I succesfully (?) converted a PAL (25 fps) VCD to NTSC KVCD @ 23.976 fps. I say "successfully" with a question mark, because although the resulting CD works great on my PC, the audio skips and stutters on my standalone.

I want to try again, but this time converting the PAL (25 fps) VCD to NTSC KVCD @ 29.97 fps.

The steps I used before were taken from this guide:

http://www.dvdrhelp.com/forum/userguides/166237.php

What do I need to do differently to convert to 29.97 instead of 23.97? I assume I can still use BeSweet to convert the audio (I see a PAL -> 29.97 option), but what about the video?

Using TMPgenc do I need to do anything other than set the frame rate to 29.97?

Do I need to include a "telecide" line in my avisynth script? Do I need to use 3:2 pulldown or anything else like that?

Can someone please post the appropriate extra lines I need to include in my script, and any "special" settings I need to use in TMPGenc.

The script I used previously was:

Like I said, I am very happy with the results using the above, but the audio skips and stutters on my standalone!

FYI - My standalone is a Pioneer DV-440. In TMPGenc I set the min bitrate to 300, and the max to 2500.

Many thanks,
Icarus

I,
video- just load it to tmpgengc and set the rate to 29.97 if there were jumps at 23.97. If you want to adjust the framerate in your avs , u can, if not, set it after loading your video into tmpgenc.
If BeSweet converts your audio fine, no skips when played back on your tv, then use the pal to 29 option. If not, either stretch your audio in another app like, CoolEdit, SoundForge or Goldwave. Or just load your audio into tmpengc and let IT, convert it to at the same time {instead of using besweet or other , as an external encoder}.


ztr

Please especially in case of OneCD encodings, ... do not encode your mpegs at 29,97FPS and full hight (480). In my opinion this means trashed quality ...

Read my posting:
http://www.kvcd.net/forum/viewtopic.php?t=5729

Theres explained why in case of NTSC we should convert at 23,97 FPS.
By doing this you have to add a puldownflag to your MPEG2! stream.
We know that mpeg1 gives us more compression and so better Quality, but its in no relation to a 23,97 FPS amount of videoinformation we have to encode as if encoding at 23,97 using mpeg2.

Well in my opinion I don't understand the usage of mpg1 when encoding using full hight (480px) NTSC streams and muxing them in BBmepg as SVCD VBR.

Progressive NTSC Streams = encoding at 23,97 incl. pulldown (mpeg2 needed)
Interlaced NTSC streams = encoding at 29,97 (mpeg2 needed to maintain interlacing).
So I changed my opinion in case of NTSC to keep interlacing when encoding just to avoid "blending"-blur in case of deinterlacing.
There exist a lot of adaptive deinterlacing plugIns to receive a very good deinterlacing quality.

Well, ... I think this "thought" is correct. ........ hmmmm

Ok VCD 352x240 @ mpeg1 does not allow 23,97 pulldown and no interlaced streams ... so I refer to 1/2 DV Sizes like 352x480 and so on