View Full Version : 29.97, 23.976 hybrid MPEG2 problem
LogicDeLuxe
24th October 2006, 19:26
I need to convert this into PAL 50i with speedup.
I tried open it with MPEGSource, MPEG2Source and Directshowsource. Either way, I got the wrong running time, with either the 23.976 parts running too fast or the 29.97 parts running too slow.
How can I open it properly in AVIsynth?
And it's getting even worse, some of the 29.97 scenes (not all of them) actually are 23.976 fps and have double blended frames. (I used that double blend removal script before with great success, though that was on a pure 29.97 fps source, and not mixed with 23.976 like this.)
foxyshadis
24th October 2006, 21:49
You should use dgdecode's mpeg2source, and create the d2v in dgindex by using "honor pulldown flags". Your situation sounds like flags were ignored.
As for fixblendivtc, you should be able to work with it after tfm, before requestlinear (important fox fixblend!) and tdec. What are you aiming for? 24 all the way, or 30? Or hybrid? The tfm/tdec arguments depend on that.
LogicDeLuxe
25th October 2006, 11:44
You should use dgdecode's mpeg2source, and create the d2v in dgindex by using "honor pulldown flags". Your situation sounds like flags were ignored.Thanks. It works so far.As for fixblendivtc, you should be able to work with it after tfm, before requestlinear (important fox fixblend!) and tdec. What are you aiming for? 24 all the way, or 30? Or hybrid? The tfm/tdec arguments depend on that.As I wrote, I am doing a conversion to 50i PAL with speedup.
What is tfm/tdec?
Right now, I use telecide() and then Lanczos4resize(width,576).
And then the FixBlendIVTC_hybrid.avs, which fixes the double blends, but also messes with the double frames from telecide.
Using bob.blendfps(29.97) instead of telecide() fixes that, but it also would degrade the quality for sure. So I'm looking for a solution better than this preferably not messing with the properly telecined parts at all (except for telecide, scaling and speedup to 25 fps, of course).
Mug Funky
26th October 2006, 04:56
grab "autopal" from here:
http://forum.doom9.org/showthread.php?t=114054
you'll need the latest tdeint, masktools v2 (and probably v1), motion (by clouded/mg262 - you'll have to search), and probably some other stuff. i just quickly copypasta'd the latest there, so i'm not sure on the dependencies, but there's nothing too esoteric in there.
then run this line:
autoPAL(speedup=true)
parts detected as film will be sped up and made progressive.
parts detected as 30p or 60i will be field-blended as per usual (and if there's edits present in the Film sections, they'll be blended unfortunately)
i've been using this in production for a couple of months, and by now it's pretty reliable. but if you get artefacts, tell me - after all, 99% complete can still mean 1 frame in 100 is buggered...
[edit]
btw, encode interlaced, tff (script only outputs tff, the way it's meant to be :)). the progressive parts can take one for the team...
vBulletin® v3.8.4, Copyright ©2000-2010, Jelsoft Enterprises Ltd.