svcd and cvd have ripples

[Farmerbright]

I finally decided to buy the tmpgenc plus so I could start making more than mpeg1 vcds but so far have been unimpressed with my results. I've tried capturing off satellite at 480x480 and made standard svcd and 352x480 cvd. I also did caps of 352x480 and made cvds. the problem is there is a ripple around everything moving on the tv. From a seated position it looks like the picture is jumping, but when you pause it you can see the lines, almost like ghosts from a oar attennae, around everything.

Should I try filtering first in vdub? If so, with what? I've tried different bitrates and also changing the field to "A" instead of "B" which was worse.

Thanks.

[Bravoxena]

I'm now sure why, but it's the way you're encoding. It's happened to me a few times when encoding videos. You don't have to filter anything. Hopefully, someone here will know what it is.

[bunyip]

It's probably interlacing - you would not have needed to bother about this in VCD but you do in SVCD - in the Advanced settings of TMPGenc turn on Deinterlacing (start with even field setting) and see if that makes a difference.

[hwoodwar]

Are you using Motion Estimate Search for the Motion Search Precision? If so, try using another setting. I have seen this create a similar affect.

SVCDs and CVDs are supposed to be "interlaced".

[bunyip]

hwoodwar - yes you are correct that the final SVCD will be interlaced but often if you don't delinterlace the source while you are encoding you will get interlacing artifacts in the final video fields.

[Farmerbright]

Thanks.

I have been using motion search precision at "normal" for these tests, although I normally encode at "slow". I have not tried deinterlacing and will do so. Under q matrix I have the "no motion search" box checked.

Is there a template to download that any of you would recommend that would have more advanced settings checked?

Farmerbright

[SatStorm]

Detect the correct field order of your material first and then set TMPGenc correct to encode....
You don't have to de-interlace anything: CVD and SVCD support interlace.

By default, TMPGenc set the field order to DV status (Bottom field first). Most of the time, it is Top field first (Field A). Swap it and you don't have problems like those anymore

[Farmerbright]

Changing field order didn't help the first time, and I tried it again with no luck. thanks anyway.

Deinterlacing made my 480x480 perfect but didn't remove the ripples from my capped 352x480 in either mpg1 or mpg2 conversions. If I convert the res down to 352x240 everything is perfect and the ripples go away. I believe that in order for me to make a cvd I will have to capture at a higher res like 480x480 and then convert. Would it matter if I was going to convert down, to capture at something nonstandard like 400x480, or 420x etc?