Aspect ratio as a number rather than a ratio

[hello_hello]

How did you come up with that 534, how can MeGui come up with that (getting 800)? Does it use autocrop for that (800)? Assuming it does it correctly (does it always?) and finds that 800 value. Then second, how does it it calculate those 534, what that sophisticated resize does actually , forget 1296, you say yourself you would not resize to it, so you have 1280, can you give me an equation how to get 534?

Seriously? You need an equation? 800/1920 x 1280 = 533.3333
I didn't say I wouldn't resize to 1296, I said I'd aim for 1280 first. If I couldn't resize without cropping too much picture for very low aspect error, I'd change the resizing if need be. I'd stick with 1280 for 16:9, but for widescreen encodes what do I care? It'll be upscaled to 1920 on playback anyway.

I don't see the problem. The closest mod2 resizing is 1280x534 which means there's a small aspect error, just as I said. Getting it down to zero can require a little fiddling with the cropping in the calculator. Maybe a pixel or two from the width, a couple more from the height etc, but often it's possible. The calculator didn't magically produce the other cropping/resizing combinations though. I fiddled with the cropping/resizing myself to find them.

I only use auto-cropping to roughly crop, but from there I invariably manually adjust it. Many (or most) programs let you auto-crop and resize but still only let you specify a width because the height depends on the cropping. So you specify 1280, they crop, and the height ends up the closest match for 1280 possible. The greater the mod specified, the more potential for aspect error.

AutoGK was one program smarter than the average bear. It cropped twice. It'd do the usual cropping and resizing but instead of resizing to the specified with, it'd resize to a height that gave you a width equal to or greater than the one specified. Or something along those lines. So if you specified (for example) 720 as a width, and after cropping the exact resizing would be 720x396, it'd resize to the next mod16 height instead ie 728x400 (727.27x400 rounded up) then it'd crop the width for 720x400. That way it could give you the requested width and mod16 with almost zero aspect error.
I had intended to duplicate some of it's scripts myself at one stage, even just as an exercise, but as everything's mod4 or mod2 these days and I always manually crop and resize, I haven't been motivated, but if I was only auto-cropping that's probably the way I try to do it, as it gives you the best of both worlds.

In case of cropping to 1920x800, is it 1280/(1920/800)=533.3333 ~ mode 2: 533.333 round up to 533, is it divisible by 2, no, add 1, it is, we got 534
if cropping to 1920x798, is it 1280/(1920/798)=532 ~ mode 4: 532/4=133 133x4=532
Where is that guessed aspect ratio involved? In our case 2.4:1. It would messed up those 798 calculations, is it looking ahead and checking that 798 would bring exact 532 later on? Thus shooting all outcomes around autocrop value and guessing the best? Is that what that Yoda resize does and that is what is implemented in MeGui? Or does it all at once go back to 1920x800 and offers resize to 1280x532 or crop to 1920x798 and resize 1296x532 ?

MeGUI doesn't automate anything, aside from automatically adjusting the resizing while cropping if you let it. Mostly I fiddle with the cropping and resizing myself until I find a very low aspect error combination.

2.4:1 isn't some magic resolution. Crop 2 more pixels from the height and the source is now 2.397:1, and in exactly the same way it was 16:9 before you cropped to make it 2.4:1, the resizing and aspect error calculations are based on the post-crop resolution.

Vs. Resizing value : 1280/(1920/1080) = 720 nice number you'd come up with those resizing BD, DVD to known 4:3 or 16:9 videos, you include them in Avisynth scripts, so you do not need to calculate those in the first place. This outcome is expected. 4:3 or 16:9. So no calculation is really happening. Then just mode cropping 2,4, or 8 whatever, 2 is fine I guess. Why don't you admit it, I do not understand.

It's not a case of me admitting anything, but I think it be a case of getting you to understand. There's always a calculation. 1280/(1920/1080) = 720 might be a nice number and easy to remember but it's a calculation.

You say that weird resolutions we should exclude because as we know all could be in error already so you might round up, not knowing if up or down both could be worse or better.

You'll have to show me where I said that, because I use non standard resolutions all the time.

It comes down to this. I have a 720x576 PAL DVD I want to resize to exactly 4:3 dimensions. 640x480, 768x576, it doesn't matter, so I'll pick 720x540. There's a lot of black down the sides I want to remove. I crop the crud and resize what's left to 720x540. I note the aspect error, and increase the cropping as required (width and/or height) until the aspect error is zero or almost zero. I save the script and I have a nice clean 4:3 encode at 720x540.

How would you resize first and then auto crop for a nice 4:3 resolution, and how would you ensure it's 720x540 each time? AutoGK had an option to always output the specified width and a 4:3 aspect ratio, and once again it involved some additional auto-cropping and script cleverness, but it didn't distort the picture. If you don't care about that sort of thing it's your personal choice, but I do, and I know you can't do it by simply resizing first and auto-cropping second, so your way doesn't work for me.

[_Al_]

MeGUI doesn't automate anything, aside from automatically adjusting the resizing while cropping if you let it. Mostly I fiddle with the cropping and resizing myself until I find a very low aspect error combination.

finally something, I cannot make one click encoder to work, that is why I ask, I thought it designs avisynth script. So is that right? It does not do that like Handbrake, loading BD and making cropped MP4? Seriously man, just answer the question. We could be there a couple of days ago.

If it does not, the do you understand what I am getting at? Why do you need that 2.4:1 for? I told you, you do not need that, you do not need any of those values what op asked about, you brought up that Megui needs that for this and this, and I asked why, because if not BD source or DVD they are false and software cannot guess correct value, you even said it yourself.

How would you resize first and then auto crop for a nice 4:3 resolution

You would not, that was my point, resize 720x576 to 1024x576 if 16/9 flag 768 if 4/3 flag, then crop letterbox only if there is, you find a tiny border, you leave it. I know, the whole world does it differently, I heard that, but that is why there is a number of videos seriously messed up. And you can script it as a bonus. You put DVD in your drive and find MP4 in the morning. No AR's messed up etc. etc., I know consensus is hard to beat. You said yourself that tablet, phone, whatever gives you black border anyway, I looked at it and said enough of this crop at all time nonsense and things just work much better. I do nothing. You bring up calculator, Yoga resizer, avs reader (MPCHC , virtualdub) finding cropping, calculating whatever and arguing with me that I do something wrong because you or the whole world does it differently. lol But I do not transcode DVD anymore, no need. It's just 4GB.
I am going to check now if handbrake can do it that way...

[hello_hello]

MeGUI doesn't automate anything, aside from automatically adjusting the resizing while cropping if you let it. Mostly I fiddle with the cropping and resizing myself until I find a very low aspect error combination.

finally something, I cannot make one click encoder to work, that is why I ask, I thought it designs avisynth script. So is that right? It does not do that like Handbrake, loading BD and making cropped MP4? Seriously man, just answer the question. We could be there a couple of days ago.

Seriously man. I've written essays answering your questions, trying to explain for days. What else are you still having trouble understanding?
I must have missed the numerous times you've asked about the OneClick encoder.... oh wait a minute, this is the first time.
Apparently OneClick can be used to auto-crop and/or resize and output a finished file just like Handbrake and every other GUI, and they all crop first, but I've almost never used OneClick myself.
I still don't know how you go about resizing first and auto-cropping because you haven't answered the question..... yet again. I'm ready to assume you don't actually have a method for cropping after resizing and it's just theoretical.

If it does not, the do you understand what I am getting at? Why do you need that 2.4:1 for? I told you, you do not need that, you do not need any of those values what op asked about, you brought up that Megui needs that for this and this, and I asked why, because if not BD source or DVD they are false and software cannot guess correct value, you even said it yourself.

Is English your fourth or fifth language?
I bought up MeGUI simply because we were discussing converting decimal numbers into the smallest possible fraction and not knowing an easy way to do it myself, I get MeGUI to tell me by creating a custom aspect ratio. That was it. You turned it into a different discussion by telling me I shouldn't be using aspect ratios for reasons that make no sense given every video has one.
I explained why I use custom aspect ratios for DVDs but obviously you don't get it and I don't know how else to explain it. I use 15:11 as the aspect ratio, you use 4:3, but EITHER WAY, you have to pick the aspect ratio you want to start with and there's no magic involved just because you happen to pick 4:3. It's an aspect ratio like the rest.
Once again.... for the other videos I WASN'T GUESSING AT ASPECT RATIOS. THEY WERE WRITTEN TO THE VIDEO STREAM. MEGUI WAS IGNORING THEM BECAUSE THE RESOLUTION WAS EXACTLY 720X480 AND ASSUMING 4:3 INSTEAD. I CREATED CUSTOM ASPECT RATIOS SO I'D BE USING THE ASPECT RATIOS WRITTEN TO THE VIDEO STREAMS INSTEAD OF THE 4:3 MEGUI WAS ASSUMING. And once more for luck.... THERE WAS NO GUESSING.

You can tell me I don't need 2.41 as often as you like but it just sounds like a way to justify not being able to crop and resize like everyone else. Cropping the black is so easy, encoding it seems borderline stupid to me.

How would you resize first and then auto crop for a nice 4:3 resolution

You would not, that was my point, resize 720x576 to 1024x576 if 16/9 flag 768 if 4/3 flag, then crop letterbox only if there is, you find a tiny border, you leave it. I know, the whole world does it differently, I heard that, but that is why there is a number of videos seriously messed up. And you can script it as a bonus. You put DVD in your drive and find MP4 in the morning. No AR's messed up etc. etc., I know consensus is hard to beat. You said yourself that tablet, phone, whatever gives you black border anyway, I looked at it and said enough of this crop at all time nonsense and things just work much better. I do nothing. You bring up calculator, Yoga resizer, avs reader (MPCHC , virtualdub) finding cropping, calculating whatever and arguing with me that I do something wrong because you or the whole world does it differently. lol But I do not transcode DVD anymore, no need. It's just 4GB.
I am going to check now if handbrake can do it that way...

So you can't achieve what I've told you countless times I want to achieve but you're still telling me to do it that way anyway.
I haven't told you you're doing it wrong. You're talking nonsense now. You started off telling me I should be doing it your way because aspect error calculators are snake oil, but now I'm the one who's been telling you you're doing it wrong? Unbelievable.
I've said it's personal preference. Things aren't going to work better for me if I don't crop, because they're working fine now. No aspect error, no black, and the output I want.

[_Al_]

you are an impossible man, just wasted couple of days,

You want plain English? Did not read further than that remark, you are entering ass**** territory with statements like that, it is me who is patient here. So elaborate on this and give me yes , no answer and quick proof, no stupid novels of yours good for nothing:

-Aspect ratio that mediainfo reports is bloody good for nothing if file is not BD or DVD file.

-MeGui does not need it while calculating anything, yet you bring that number up, rounded up all the time and make some decimal to fraction calculations thinking about infinity for a decimal number.

-You CAN resize and autocrop BD, DVD file afterwards automatically not having university degree how things work and you are better off.

-If talking about not BD and DVD file , like downloaded MP4, our own encoded files if cropped or whatever was done (especially after your world norm class treat crop&resize and making mistake because doing it manually one makes a mistake, just look at the web) we established source could be anything, thank you.

[hello_hello]

you are an impossible man, just wasted couple of days,

Yep. All that and you still don't understand

You want plain English? Did not read further than that remark, you are entering ass**** territory with statements like that, it is me who is patient here. So elaborate on this and give me yes , no answer and quick proof, no stupid novels of yours good for nothing:

Really? After I've asked you yet again what your method is for resizing first and cropping second and you've ignored it yet again? Yet once more you've told me to do it that way. And you want me to keep answering your questions? I'm still laughing.

And to think you actually accused me of being the one telling you how to do it. It's hard to create a new version of history in forums without being able to remove all the evidence, yet it's amazing how often people are somewhat detached from reality.

How do you convert numbers to the smallest possible fraction? I've never known.
ie How do you convert an aspect ratio of 2.76:1 to a fraction smaller than 267:100, assuming it's possible?
When creating a custom aspect ratio in MeGUI, either fractions or numbers can be entered, but when the custom aspect ratio is saved, MeGUI displays both. I wouldn't mind knowing how to convert decimal numbers to the smallest possible fraction myself.

I would not let MeGui doing stuff like that, it needs for some Avisynth calculations right? Just setting proper modes (cropping) you can Resize and autocrop at the same time even using batch scripts, if not doing it quickly in the head. Just remember resizing first (same ratio as original, for example 1980x1080 to 1280 and calculating 720), then autocroping, that is the principle, this proper sequence makes a hell of a difference. Doing it other way brings you this AR nonsense calculations, maybe Megui programmer fell for it. Try it. Talking here about non anamorphic videos.

You bring up calculator, Yoga resizer, avs reader (MPCHC , virtualdub) finding cropping, calculating whatever and arguing with me that I do something wrong because you or the whole world does it differently. lol But I do not transcode DVD anymore, no need. It's just 4GB.
I am going to check now if handbrake can do it that way...

[hello_hello]

Double post

[Keyser]

For those of you who want to know what's the AR expressed as a reduced fraction, I prepared a small program that calculates the GCD (greatest common divisor) of the video dimensions and then divides both dimensions by that amount. Just enter the dimensions and the program does the rest.

[hello_hello]

For those of you who want to know what's the AR expressed as a reduced fraction, I prepared a small program that calculates the GCD (greatest common divisor) of the video dimensions and then divides both dimensions by that amount. Just enter the dimensions and the program does the rest.

Thanks.

[hello_hello]

I was reminded of this thread while I was trying to work out how to do something else, as I discovered Avisynth has the ability to reduce fractions, so I created a little function to make it easier, and another one to convert decimal numbers to fractions. The result is displayed as a subtitle in the centre of the video.

LowDen(Num, Den, Limit) reduces fractions.

# Function for displaying the lowest common denominator of a rational pair of numbers.
# The result displays as a subtitle in the centre of the video.
# The Limit argument specifies the allowable error as 1/Limit, so Limit=100 would be 1/100 or 0.01 or 1%.
# If Limit is not specified, Num & Den are reduced by the greatest common divisor.
# http://avisynth.nl/index.php/Internal_functions#Continued_Numerator.2C_Denominator
#
# Examples:
# LowDen(1280, 720) will result in 16/9
# LowDen(1281, 721) will result in 1281/721
# LowDen(1281, 721, 100) will result in 167/94
# LowDen(1281, 721, 10) will result in 16/9

function LowDen(clip c, int "Num", int "Den", int "Limit")
{
    assert(defined(Num), """ LowDen: Both numerator and denominator must be specified """)
    assert(defined(Den), """ LowDen: Both numerator and denominator must be specified """)

    Numerator = string(ContinuedNumerator(Num, Den, limit=Limit))
    Denominator = string(ContinuedDenominator(Num, Den, limit=Limit))

    return c.subtitle(Numerator + """/""" + Denominator, size=30, align=5, text_color=color_white)
}

DecToFrac(Dec, Limit) converts decimal numbers to fractions.

# Function for converting decimal numbers to fractions.
# The result displays as a subtitle in the centre of the video.
# The Limit argument specifies the allowable error as 1/Limit, so Limit=100 would be 1/100 or 0.01 or 1%.
# Limit=50000 by default which should make it accurate to nearly 6 decimal places,
# therefore 1.777777 or 1.777778 will convert to exactly 16:9. To disable the Limit argument, set Limit=0
# http://avisynth.nl/index.php/Internal_functions#Continued_Numerator.2C_Denominator
#
# Examples:
# DecToFrac(1.78) will result in 89/50
# DecToFrac(1.777778) will result in 16/9
# DecToFrac(1.777778, 0) will result in 634601/356963

function DecToFrac(clip c, float "Dec", int "Limit")
{
    Limit = default(Limit, 50000)
    Limited = Limit == 0 ? undefined : Limit

    Numerator = string(ContinuedNumerator(Dec, limit=Limited))
    Denominator = string(ContinuedDenominator(Dec, limit=Limited))

    return c.subtitle(Numerator + """/""" + Denominator, size=30, align=5, text_color=color_white)
}