View Full Version : Deinterlace 60fps video to 29.976fps
eriler
1st January 2014, 15:33
Hi,
I've got a part of a video that is interlaced, and that displays at 60 fps, and i need some help deinterlacing it to 29.976 fps.
Problem is, that it is native 29.976fps, not 23,97 fps. So just slapping on a tdecimate() does not work, the output video starts skipping 1 frame (Very obvious since it has scrolling text).
secondclip = trim(40505,43202).ChangeFPS("ntsc_video").assumefps("ntsc_film")
gets me my desired fps (After muxing it with a timecode file) without having dropped any frames it shouldn't have dropped, however i can see the interlacing.
Does anyone have a tip for a deinterlacing filter that will deinterlace to 29.976fps?
Here's a 10 seconds clip of the video in question:
https://mega.co.nz/#!6FFznYhY!SdKyk3PdEV7ySWQhASZc4TBJqap1bZf48OeJBjlfLaA
Guest
1st January 2014, 16:09
The video in the background is 3:2 pulldown while the overlayed credits are 29.97 progressive (it only appears interlaced after separatefields because the scrolling rate increment is close to the vertical field offset). This is a difficult thing to deal with and I do not know any good way to handle it. If it were mine, I would apply normal IVTC to the main movie and then apply a pure adaptive deinterlacer to the credits part.
eriler
1st January 2014, 16:17
So just tfm().tdeint().assumefps("ntsc_film") on the credits part, and then make it 60fps in the timecodes file?
Stereodude
1st January 2014, 16:24
Presumably you mean 23.976, but I think you may be out of luck depending on your goal. You have 23.976fps film based footage (with a telecine applied to it) in the background and the credits are 29.97p on top of it. You can manually control the IVTC (since any automatic search will fail) to reconstruct the background footage and then drop the duplicated background frame (again this will have to be done manually) giving you 23.976 fps footage with no interlacing, but the credit superimposed on top will not end up moving smoothly.
Guest
1st January 2014, 16:24
I forgot about the problem of the mismatched frame rates. :(
I do not know a good solution for you. Best may be just accepting that the credits will be jerky. VFR seems overkill just to make credits smooth, but it is an option. Maybe others will have an idea.
Stereodude
1st January 2014, 16:30
So just tfm().tdeint().assumefps("ntsc_film") on the credits part, and then make it 60fps in the timecodes file?That's probably not ideal. You shouldn't use tfm. I think you would want to make it 29.97 in the timecodes file (assuming you're doing VFR) since tdeint doesn't double the frame rate by default and you are not passing it any parameters.
eriler
1st January 2014, 16:30
Sorry, i had written tfm().tdeint().assumefps("ntsc_round_double") in the post above, i meant tfm().tdeint().assumefps("ntsc_film") (Otherwise it wouldn't work because the movie part gets decimated to 23.97).
Let's face it, nobody who'll download this cares about the credits (whether the video in the background nor the scrolling credits), so they don't need to be perfect, i just want them as good as i can without having to go through backbreaking work on them.
Guest
1st January 2014, 16:54
Let's face it, nobody who'll download this cares about the credits ... Closed for prima facie rule 6 violation. Explain in a PM if you have rights to redistribute this copyrighted material.
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.