Log in

View Full Version : FPS In Nero Recode 2


guardedthought
30th December 2004, 21:49
Has anyone found a relatively easy way to do frame rate conversions in Recode 2? I like to do my "TV Backups" at 19.98 fps (basically to get a better image at lower resolutions) and right now I do TMPGenc->VFAPI->VdubMOD->AVIsynth->Recode to get the resolutions and FPS set correctly.

I would love to be able to cut the VFAPI out altogether as it brings down my recoding FPS, but so far this is the only method I have found to get this done.

And before you ask, I havet to use TMPGenc to read the files because I do occasionaly re-encode other MP4 files, and VdubMod can't read them. I also do cropping and FPS conversion in TMPGenc just to save a step in VdubMod. Right now I only use VdubMod to frameserve to Recode. In a typical day, I can get one DVD backup and one TV backup done. If I could lose VFAPI from my setup, I could probably get two TV backups per day.

bond
30th December 2004, 22:02
you could create an .avs script that writes duplicate frames directly in a way that you get your desired framerate (eg 25fps). i dont know how this is possible, but i am pretty sure that it is possible :D

btw afaik neros asp codec is able to create n-vops if two frames are duplicate, which means that you could remux (not recode) the stream after it has been encoded with nero with the 3ivx muxer and drop the duplicate frames/n-vops out again. that way you will get a variableframerate stream having the same frameamount as your captured stream, but it will be played like a 25fps stream, helping you saving lots of bits :)

guardedthought
30th December 2004, 22:10
I had already tried writing the frame rate conversion into my avs script, but AVIsynth didn't like it on all the different source files I had. It did also slow down AVIsynth noticably.

I didn't know about the n-vops option though. That would work except that hardware limitations (on the multiple devices that playback the TV Backup encodings) really prevent me from going any higher than 19.98 fps before the lower end devices (particularly the smartphones) start dropping frames like crazy. That and the fact that most of the devices that this needs to work on can't handle VFR.

Thanks for the heads up on the n-vops though. I'm going to explore that and see if I can't put it to use on another project.

guardedthought
30th December 2004, 22:11
And I forgot to mention in my initial post that I need to use the ASP version of ND, not the AVC.