23.976 to 29.976 - do I want to do that?

[Intuit]

I originally put this post in advanced conversion but I'm not sure if it really belongs there!

Hello everyone. I have a Xvid video with a source that is 23.97 FPS. In Canopus, I have the option of choosing 2 different frame rates. One of these is 29.976. Will it do anygood for me to choose 29.976 or will that screw up my playback? I know this is probably an easy question to answer! Please excuse my noobidity!

[guns1inger]

No, you do not want to do that. You want to encode it as 23.976 with 2:3 pulldown. This will be a seperate encoding option. This will keep the video smooth and the audo in sync.

[Intuit]

Great! Thanks!

[Intuit]

Well I was unable to encode with 23.976. TMPGEnc wouldn't encode it (it gave me an error) and Canopus crashed. However when I left it at 29.976 (default for Canopus), it was able to encode it, but the picture doesn't look good as you said it would. Any ideas on the best way to encode this?

I know this probably belongs in another forum now...

BTW, i have already demuxed the audio...


GSpot screenshot:

[jagabo]

TMPGEnc (Plus?) shouldn't have crashed. Use the settings marked in red:

[Intuit]

I can't find a setting for TMPGEnc where it says 23.976(internally 29.976)... I can only pick one or the other. I have tried both TMPGEnc Plus and regular TMPG...

[Intuit]

nevermind, I got it. Thanks again Jagobo.

[Intuit]

Grr....TMPGEnc Plus gave me the error again:

"Read Error occured at address 00012F40 of module 'TMPGEnc.exe' with 646165E."


Anyone know what this means????

[Intuit]

See screenshot of file above...

[Intuit]

Does anyone have any idea why I can't encode this file at 23.976?

[jagabo]

Grr....TMPGEnc Plus gave me the error again:

"Read Error occured at address 00012F40 of module 'TMPGEnc.exe' with 646165E."

Anyone know what this means????

It either means the source file is corrupt or TMPGEnc has a bug. You could try using AVISynth or VirtualDub to frameserve the video to TMPGEnc. That may or may not help.

[Intuit]

Thanks Jagobo. Dare I ask how to frameserve? Is there a good guide for this type of file on here that you know of?

I have know idea how to even start to frameserve....

[jagabo]

Open the video in VirtualDub (or VirtualDubMPEG2, or VirtualDUbMod). Select File -> Start Frame Server. It will ask for two names, a pipe name (use whatever you want) and a filename. This creates a dummy file used to pass information between VirtualDub and whatever program it is frameserving to. In TMPGEnc, open the filename you used there.

[Intuit]

Do I setup TPMGEnc like I normally would to encode then?

[Intuit]

No, you do not want to do that. You want to encode it as 23.976 with 2:3 pulldown. This will be a seperate encoding option. This will keep the video smooth and the audo in sync.

Hey I see no 2:3 pulldown...only 3:2

Is there another option out there that is 2:3?

[manono]

Use 3:2 Pulldown, if that's the only choice. 6 of one and half a dozen of the other.

[Intuit]

Well I can't frameserve, I tried that and was unable to. I can't convert with 3:2 as TMPGEnc gives me an error message and Canopus crashes. I'm going to try 29.976 and just hope it looks ok.

Grr, is anything ever easy?????????????????????????????

Thanks for eveyone's help and info though!

[guns1inger]

I would try using FitCD and avisynth, as this will frameserve nicely to ProCoder, whereas Virtualdub takes a bit of finsessing

[jagabo]

Well I can't frameserve, I tried that and was unable to.

Did you ever run AuxSetup.exe in the main VirtualDub folder? You have to run that once for frame serving to work.

[Intuit]

No, I didn't do that. However, I did encode at 29.976 and the video seems to be alright. I will see what happens after I burn to dvd...

IF its jerky, I will definitely try to frameserve. Thanks for your help!

[jagabo]

You can encode a 23.976 fps progressive source as 29.97 fps interlaced, or you can encode as 23.976 fps progressive with 3:2 pulldown. The latter gives better results and requires less bitrate.

[Intuit]

Right on. Well it worked at 29.976, so I'm happy for now. I will keep your efficiency type ideas in mind for future dvds though. Thanks again for your help.