Trying to resize for overscan and it screws up video

[MDK]

Good Day,

I hope some can help with this very frustrating problem I am having. Here is the scoop:
I capture a TV show using virtualDub and Huffyuv at a resolution of 352X480. All that works fine. When I encode it to MPEG2 with CCE2.5 the resultant video looks great but I can see a serious overscan problem on my TV so I can here a looked up some stuff on overscan and found that FitCD can calculate it for you. I used it to calculate the proper resize and border addition and plugged that in my AVISynth script like this

...
BicubicResize(320,446)
AddBorders(16,17,16,17)
...

When I burn the disc and watch it on my TV there is very apparent flicker and what looks like interlacing field problems. Before I started on the overscan problem I did experiment and find the right field order for the encoder so I am about 99% positive it is not that.

I have even tried de-interlacing the clip first then resizing and it still looks funny.

I am at a loss
Any help greatly appreciated
Thanks
MDK

[gll99]

I too use Win98SE, when I used the vxd drivers with my card all my captures had visible scan lines. I used a vdub filter to mask them and then resized the image back to its original size. I haven't had to do it since switching to wdm drivers but I had to switch my capture app to wdm compatible ones. (like amcap,virtualvcr, powervcrII, wincoder.)

If you have a bt878 compatible capture card you may want to look at these wdm driver sites:


http://www.iulabs.com/eng/index.shtml

http://btwincap.sourceforge.net/index.html

[mb1]

Some points to consider:

- you have interlaced material so do proper interlaced resizing. Check the interlaced resizing box in FitCD for that.

- FitCD has a resizing bug for interlaced resizing combined with optimize for cce which leads to reverse field order. Deselect optimize for cce (or avoid odd values and play manually)

- CCE handles the field order flag its own way (always sets tff)
Normally your captured source should be tff so should be no problem (but avoid the FitCD bug with reverse field order)

I would recommend this script:
...
AssumeFrameBased.SeparateFields
BicubicResize(336,222,0,0.6,0,3,352,233).Weave
AddBorders(8,18,8,18)

Don´t resize to 320 as it gives you viewable black borders on the left and right side (even on tv).

regards
mb1

[MDK]

Thanks for the replies and for the information.

mb1:

In your script example it seemes to apply to the VCD format. What resizing format would you suggest for a CVD (352x480). I captures at 352x480 and want to keep it at that size for burning a MPG2 CVD.

Thanks for any additional help and for the info on FitCD

Cheers
MDK

[mb1]

@ MDK

Please try my script. It is for 352x480. ('weave' brings the two fields together and so doubles height 222x2=444 + 18 + 18 = 480).

As told before this is interlaced resizing.

regards
mb1

[MDK]

mb1,

Thanks for the clarification. I will be giving your script a try this evening and I will let you know how it goes.

Thanks again
MDK