Pal 25fps to NTSC 29/23fps NEED HELP!

[Kevin Henry]

Got a number of DivX files down that are 25fps. My DVD player wont play them properly if I do a straight convert to mpg (mega stuttering) so I'm thinking cos I have to use NTSC standard -

- HOW do I change 25fps to NTSC? I've tried a few tricks, but I dont like stretching the audio as it ruins the sound.

Using CCE 2.64, frameserving from TMPGEnc & VFAPIConv.

[bugster]

Its not as if you are the 1st person who has ever wanted to do this!

http://www.vcdhelp.com/pal2ntsc/pal2ntsc.htm

or for something a bit different

http://www.vcdhelp.com/mpeg2tovcd.htm

[DJRumpy]

I would think dropping it to 23.976 fps would be virtually unnoticable.

[Kevin Henry]

ah thanks. I've searched the forums, and I found lotsa ntsc to pal so I sorta reversed the procedure. But the stretched audio ended up with funny 'wobbles' in it occasionally, so I was getting rather annoyed.

Posting a thread is usually a last resort for me, when I cant find the solution myself ...

I dont know how noticable the difference is, cos the stutter with 25fps is terrible. 23 fps is a little noticeable, and pulldown seems to make it worse I'll check the link, thanks.

Ok this is wierd. I put a 29fps movie into CCE and it came out at 23fps. what up with that?

[DJRumpy]

I'm guessing that depends on how you 'reversed' the process. Did you convert your film down to 23.976 frames per second?

[Kevin Henry]

Yeah, I used Vdub to convert the film, then stretched the audio to fit. Sync was perfect, but there were 'wobbles' in the sound.

Now, encoding 23fps files gives me wicked stuttering! GRR!

Also, the CCE homepage says that the output frame rate is selectable with CCE - how the HELL do you do that??? I cant see anyway to do it!

[DJRumpy]

Convert your audio seperately using BeSweet. BeSweet will convert audio from one format to another seemlessly. Just select 'PAL to NTSC (23.976)'. I've used it a time or two, and gotten good results. Encode your AVI, and then multiplex your audio back in.

[pijetro]

Here it goes
.1)I frameserve to CCE with Vdub at 23.976fps.(I use ver2.5).
2)Run "pulldown.exe" on that .mpv file.
3)Rip the audio to PCM 16bit 44100khz into Cool Edit, and if you're audio source is good in the first place, then Cool Edit does a great job of stretching it out by 104.27%.(the difference 25fps/23.976fps). I personally type in the total amont of seconds of the new audio, by seeing what the new video length is when after loading it into WinDVD. You shouldn't get any quality problems.
3)Use toolame to convert the new .wav to .mp2.
4)Multiplex with either bbmpeg or Tmpgenc.

You seem to frameserve a .tpr, via Vfapi, but it should be the same thing. I'm assuming you're making SVCD's.

BTW, can you lead me to a link that properly shows step by step .tpr frameserving via VFAPI? I want to compare the speeds.

[Kevin Henry]

pijerto - save the .tpr, open in vfapi conv, convert, then open the .avi in CCE and encode. It's that simple.

Thanks for the tip, I'll try the frameserving from vdub but i'm not having much joy with that method...

yeah, making CVDs.

[pijetro]

Maybe I should start another post , but when you load your Tmpgenc settings (bitrates 'n' stuff), doesn't that conflict with what you want CCE to encode?

I understand about the resizing and aspect ratio via .TPR, but where does CCE take over when it comes to bitrate control?

When I've got some time, maybe i'll shut up and get on with it myself!!!

[Kevin Henry]

nah, i think the only thing that gets sent to cce is the frame rate & the resizing info ... i'll check tho.

open the .ecl file that cce creates, it has all the info in there ...

[Eldritch]

Take a look at the following link:

http://forum.doom9.org/showthread.php?s=92cb578df2a3fe27311eab1b20287ae3&threadid=35387

It contains an avisynth script together with a new filter called SmoothDeinterlace. It can do standards conversion in both directions. From the documentation:

This script works by first converting the input video from interlaced fields to progressive frames using an adaptive deinterlacer. Then the progressive frame rate is converted. Finally the progressive frames re-interlaced for output. Scaling is also performed where appropriate.

It may seem to be quite complicated but the users' reactions in the above thread are really positive.

Good luck!
Eldritch