converting .avi to dvd - jerky, and sometimes short results

[righton]

i am trying to convert some avi files to dvd compliant mpegs

i tried a program by cucusoft, and the resulting encode turned out well, with smooth picture and the full length of the video showing.

i have been trying to use dvd2svcd along with CCE to try and produce similar results in a shorter time. i have tried a PAL .avi and also an NTSC one. Using the D2sRoba plugin, the encodes come out with the proper video length (same as original). if I just use dvd2svcd on it's own though, my results come out as much as 1/2 the length of the original file (and d2sroba didn't work on my NTSC file).

as well, no matter how i have tried to configure settings, the encoded dvd files do not come out with smooth motion similar to the original (i have changed the field order, bitrate settings, frameserver settings -- pretty much all the settings i can find in dvd2svcd).

I know it is possible to encode the file well since the cucusoft program did it. i'd just like to be able to convert more efficiently (faster) and with the best results possible.

any suggestions on settings i could change?

(and out of curiosity, it seems there is no frame-rate setting in dvd2svcd...is it automatically set?)

is there a better set of programs to use?

is there a certain reason my encoded files are coming out with the wrong length after encoding (using dvd2svcd)?

(edit: i did search for anwers to this as well, but no luck so far)

[B4ST4RD]

Dude,
I also am having the same problem(Video Length). Are you using a joined video file? That seems to be where my problem started.
As for the jerkyness, I found that DVD2SVCD with CCe is the best app to use. It's far superior to TMPEnc 2.5 and 3.0 xpress. Useing the following guide seems to get the best results..
http://www.dvdrbase.com/showthread.php?t=25572
The file length seems to be a big issue which I can't find any answers to. It's probably something to do with a joiuned file having 2 different bitrates, I'm not quite sure how to fix this problem yet, but will keep you posted