XviD to DVD - Aspect Ratio...

[ZiGGY909]

Hi there,
I have a AVI file which is 640 x 272, im using avisynth and cce to encode it to mpeg2.

My question is... how do i fiquire out what numbers to put in the addborders command... (without using apps like fitcd)

This is FitCD's numbers:
LanczosResize(688,320,0,0,640,272)
AddBorders(16,128,16,128)

How can i determine these numbers myself>?... is there any guide here i can go through?

Thanks

[manono]

Hi-

That kind of begs the question, doesn't it? If FitCD works (and it does), why learn the math behind it? It'll take you much longer to figure, and unless you're careful, it's easy to screw up.

Anyway, I'm sure someone else can teach you how. I never bothered to learn, since FitCD is so easy and good.

I assume you set the blocks overscan on purpose and plan on encoding for 4:3 widescreen. Also, since you're not doing any cropping, you can write it this way:

LanczosResize(688,320)
AddBorders(16,128,16,128)

Might save a couple of minutes during the encode.

[ZiGGY909]

Hi, well thats just it you see, i dont know if FitCD is accurate.

I used that script above and it came out too small on my tv (like letterbox size, basically more black than picture!!)

I just want to know how to work out this, anyone please?

[fritzi93]

Oh, FitCD is accurate, except in two situations I can think of:

1) You farked the settings. (And why so much overscan?)
2) In source, ITU-R BT.601-4 comes up as checked. A few times I've seen that, the AR comes out buggered. So I uncheck that and edit the script, 704 (or 720) for the first number, 704 (720)/ real aspect ratio, and round off the result. The Add Borders commands are adjusted to agree.

What is FitCD telling you about the source?

Here's a couple guides that discuss resizing:

https://www.videohelp.com/forum/viewtopic.php?t=222898

https://www.videohelp.com/forum/userguides/185077.php

Good luck.

[ZiGGY909]

Dont know mate, like i said im a n00b !!!
Dont know why i choose a 2 overscan, thats the horizontal edge yeah?


thanks for the links fritz, very good read there with those links, helped alot

----------------------------------------

Ok my movie is : 640 x 272

I manged to work out the caculations myself using info from the links above... i just need someone to tell me if its right, if it is then il be overwhelmed

Does this script look right to you?

AVISource("C:\Documents and Settings\Darren\Desktop\movie\joined.avi")
LanczosResize(720,306)
AddBorders(0,135,0,135)
ConvertToYUY2()

il be encoding this soon and il let you know what happens !

I appreciate the kind advice.

[fritzi93]

It looks okay to me, although I confess there are real experts here, of which I ain't one. According to my calculations, you're good to go. I presume you're clear on how to use CCE with a script? Just drag it onto the CCE window. Double-click it and look at the CCE settings, you probably won't have to change anything unless you want to close GOPs, which some authoring apps seem to prefer. Try extracting just a short AVI clip from VirtualDub and test it. I use ffmpegGUI to do the audio separately, so I uncheck audio and the output is an mpv. MPC will play it. Might save you some time.

Good luck. It's a pleasure to help someone who will actually read the links provided. Welcome to the hobby.

[EDIT] The first pass if using VBR will be a .vaf, an information file CCE will then use to do the actual encode.

[manono]

Nah, that script's no good. Earlier you were complaining about too much black, and even after doing away with the blocks overscan (which would make the active video larger), you've actually given yourself more black, not less.

Again, use FitCD. If encoding for 4:3 widescreen:

LanczosResize(720,336,2,0,636,272)
AddBorders(0,120,0,120)

And if you want to encode for 16:9:

LanczosResize(720,446)
AddBorders(0,65,0,65)

If going for 16:9, it's usually a good idea to have even numbers in the AddBorders, so the 2 65s would become 64 and 66. It's debatable whether or not encoding for 16:9 will give you a better picture. I say no. Some people with widescreen TV sets like to do it to avoid using the TV set's Zoom. If you want to upsize and encode for 16:9, you might use Lanczos4Resize.

[guns1inger]

I was just about to say those numbers didn't look right. I don't believe FitCD is always correct, because I think it sometimes rounds to the nearest block border incorrectly. This does not happen often, but I have my own calculator and the two don't always agree.

[fritzi93]

Manono's right, shoulda double-checked instead of scribbling on scrap paper. I manually entered the size into FitCD, checking the PAL boxes. Here's the relevant part of the script, using Bicubic Precise Resize instead of Lanczos:

BicubicResize(720,336,0,0.6,2,0,636,272)
AddBorders(0,120,0,120)

Lanczos I get the same as Manono. Thanks for the reminder about even numbers. :P

[EDIT] For anamorphic output I get:

LanczosResize(720,448,2,0,636,272)
AddBorders(0,64,0,64)

[ZiGGY909]

Thanks for help
i just finished encoding and the results look ok on my monitor, the pic looks like its a good aspect, small view there's only top & bottom border - when i go into fullscreen, there is however side borders.

This was my script... AddBorders(0,135,0,135) lol why did it add side borders, i commanded it "0"? ... maybe it will be different on the tv though, will it?

Il let u know, cant burn it now, no discs until tommorrow!

[manono]

Hi-

The figures are close enough that you might not be able to tell if you have Aspect Error or not with your encode. One thing to keep in mind though, is that all software players, such as PowerDVD, play DVDs with incorrect Aspect Ratio. Watch it on your standalone. Then while watching, try and look for something round, like a sun, moon, ball, etc. Pause it and you may notice it to be a slight oval, instead of being absolutely round. You may have to get out a ruler to measure it to be sure. These are small percentages of Aspect Error.

As for having side borders being added, that must be a computer player issue, as your script doesn't add any. They won't be there when played on your standalone. In fact, the opposite will occur. You'll have less video on the sides because of your TV's overscan.

guns1inger, personally I turn on ITU resizing in FitCD. That will give slightly different figures. I don't know if that brings the FitCD figures more in line with your calc or not. I didn't do that in this case bacause ZiGGY909 didn't in his scripts, and I didn't want to complicate things unnecessarily. If you're talking about FitCD not resizing by Mod16, then you're right, it doesn't.

[guns1inger]

I don't use ITU, and it is generally closer to my calculations without it. The issue is that when you do select round to nearest 16, it sometimes rounds up when it should round down. Not always, just some combinations of settings don't add up. I still use it, but I don't accept it's figures without checking them.

[ZiGGY909]

Sorry for the wait, i just burned it off and viewed it on my standalone.

It's too small, im doing another encode now (ticked anamorphic and 16:9 in cce)

Do you think i should be selecting 4:3 in cce? ... i know my input is 16:9, but maybe u have to choose 4:3 cce when using custom scripts. Either way im gonna do it anyways, its about time i nailed this and encode it every possible method, that way il know for sure and some techniques along the way.

Tell me... I tried doing some test encodes, 5min clips.
I tried to add them all to my dvd author but it says the video inputs all have different sizes... anyway around this? ... possibly a way of tricking my dvd player just so i can compare the clips.

cheers for helping

[guns1inger]

You are definately doing something wrong. If you are sending CCE 'anamorphic' 16:9 material (i.e. stretched) then you should set CCE to 16:9. If you have letterboxed widescreen material (i.e. no stretching) then CCE should be set to 4:3.

If you are resizing correctly, then all you files with have the same resolution. 4:3 or 16:9, you should get 720 x 576 at the end of the process.

[ZiGGY909]

come to think about it, you could be right.
I have a "different" version of cce. *cough* (para-x)

[guns1inger]

nasty cough you have there. Use g-spot, or even virtualdubmod, to load up the samples and see what resolution you have after encoding.

You can also use virtualdub on the avisynth scripts to see what resolution they are producing.

[manono]

Your input isn't 16:9. If you used your script:

AVISource("C:\Documents and Settings\Darren\Desktop\movie\joined.avi")
LanczosResize(720,306)
AddBorders(0,135,0,135)
ConvertToYUY2()

It's for 4:3 encoding with a slight Aspect Error. Nothing to do with your CCE version.