Dealing with 3:2 Pulldown

[poisondeathray]

I don't think so. My frame #49 for yadifmod/nnedi3.srestore is a different time .It's almost 1/2 a second off

Add info() to that script in post #28

How many frames does it report ?

[ROBO731]

That's strange. There's 558 frames.

[manono]

This is what I get on frame 49.

Frame 49? What's your framerate, 19.98fps? This is what I get with both frames 61 and 62:

[poisondeathray]

Something is messed up . With yadifmod/nnedi3.srestore I get 693 frames @ 23.976.

Do me a favour and download "sample.vob" that I uploaded in post #15, so we're on the same page and try again

[ROBO731]

This is what I get on frame 49.

Frame 49? What's your framerate, 19.98fps? This is what I get with both frames 61 and 62:

Hmm, that's weird, should I upload my d2v?

[manono]

No, but did you make it using 'Honor Pulldown Flags' as you should have? My guess is that you used 'Forced Film'.

And I would be wrong about getting a 19.98fps video. I was thinking of what you'd get if you IVTC'd something on which you had Forced Film. Using SRestore as we're doing you'll get 23.976fps, but speeded up (and missing a whole lotta frames). And the unblender won't work correctly.

Go back and make the D2V again.

[poisondeathray]

No, but did you make it using 'Honor Pulldown Flags' as you should have? My guess is that you used 'Force Film'.

bingo! that would do it!

[ROBO731]

Wow, I can't believe I overlooked that. That fixed it. Thanks guys.

[jagabo]

Try this:

Mpeg2Source("sample.d2v", CPU=6, Info=3) 
Interleave(TFM(field=1), TFM(field=0))
SRestore(omode=4, speed=3)
SelectEven()
TDecimate()

[ROBO731]

Thanks it looks great with this script.

[poisondeathray]

jagabo's is the best one . No deinterlacing, better quality, and faster to boot

You see , someone comes along with a better suggestion. You never would have got that if you took the video off so soon and kept it off

[jagabo]

Yes, when I went to download from the original link I got the message the file had been deleted. I almost didn't continue reading the thread.

[ROBO731]

Yeah, I realize that. I'll use a different site in the future that I don't use for my own private storage. For now, I changed my mega links of my previous posts to the one that pdr attached so that it will work as long as it's on this site and so I could take it off my storage. Anyway, thanks guys, I really appreciate all the help.

[manono]

Using that script, during the 12fps parts (with each number representing a unique frame) I get:

1222344456667888

That is, it's animation and the dupe frames aren't in the right places. But if using TDecimate(Mode=1), I get what I should:

1122334455667788

That script sure got rid of all the blending, though, and I'll be able to use it sometime, I'm sure. So, thanks.

Or am I the only one getting dupes in the wrong places?

[jagabo]

Using that script, during the 12fps parts (with each number representing a unique frame) I get:

1222344456667888

That is, it's animation and the dupe frames aren't in the right places. But if using TDecimate(Mode=1), I get what I should:

1122334455667788

You're right. I didn't notice that. I was just looking for blending artifacts.

[ROBO731]

DGIndex detects a field order transition. Is there any point in correcting it with the script I'm using? If so, is there a way to find the exact frame number?

[manono]

It's usually, but not always, correct to have DGIndex fix it. And If I remember correctly, TFM won't use one that hasn't been fixed. In the additional file DGIndex creates you can find where in the D2V it happens. But I don't know how to take the D2V information and find the exact frame number. After fixing the D2V there aren't usually any problems IVTCing. It's just a case of a '0' being used instead of a '2', or vice versa.

[ROBO731]

Okay thanks, I'll correct it then.