VirtualDub question for Virtualis

[eronnero]

Hey man I tried chopping the video (to compensate for overscan) with VirtualDub like you said and it worked great. My question is though, did you take the 16 from the sources original width x length or from the w x l of the output default, eg PAL from 352x288 to 336x272 etc. Hope that made some kind of sense to ya!
Anyway look forward to hearing from ya soon.
Cheerz.

[vitualis]

I think it was some other guy that recommended that (and I don't necessarily agree that it needs to be done). If your video is sourced for something that was designed to be played on a TV (e.g., DVD), then the original author will have taken TV overscan into account.

In any case, you can adjust for overscan with VirtualDub using the following method:
Let us assume that you want to eventually create video for PAL VCD (i.e., 352x288) and your source video is already 352x288.

Then, with VirtualDub, Video --> Filters --> Add --> Resize

width = 316
height = 259

Check expand frame and letterbox image
frame width = 352
frame height = 288

You can't just go resizing 16 pixels from each side as you'll end up with your video aspect ratio off.

16 pixels off both sides off the width is about 5% overscan adjustment, and you can calculate the correct ratio to use for the height. The closest integer pixel is 259 pixels.

If you use the settings above, everything should be "okay"... This is assuming that your source video is in a 4:3 display aspect ratio, however.

Best of luck.

Regards.

[eronnero]

Sorry dude, my mistake. Thanks for your advice anyway, it was very helpful!
Cheerz.

[eronnero]

Hey there, me again....
Your post raised a few questions. Is there any failsafe method of overscan compensation (I use movies primarily downloaded from the net, and all so far have suffered from overscan when burnt)? And how did you come to that VirtualDub ratio you gave me? Also if I use this VirtualDub method of reduction,what ratio setting should I use in TMPEGEnc, eg. full aspect ratio, centre etc?
Thanks again.

[vitualis]

352 x 288 is the final framesize.

5% overscan on each side means width of content = 352 *0.9

That is, width of content = 352 * 0.9 = 316.8 --> round to 316 pixels

New height of content = (316 / 352) * 288 = 258.5 --> round to 259 pixels.

BTW, if you use TMPGEnc, you can play around with its settings and it will automatically make a border for you if you so wish... (that is, the above isn't necessary).

Regards.

[sterno]

FitCD can also calculate resizing for overscan correction.

[vitualis]

There you go!

I don't normally do this so I only know how to do it manually... Seems logical for there to be an automated tool.

Regards.

[eronnero]

Cool thanks guys. Just on more question (I promise!) Where do I put these newly aquired measurements, and in which program?
Thankya vera much.

[eronnero]

Err...umm ok. I have no farching idea what I was looking at in FitCD or what I was to do with it! I loaded a file into it, it gave me a whole bunch of figures etc. and that was it. Is there a help guide to using it (with TMPEGEnc or VirtualDub)? Hmm.. Im beginning to think overscan can have its way........

[eronnero]

....oh I'm tryin' to burn to VCD.
L8R.