Progressive source has interlacing lines in the video?

[killerteengohan]

I thought all/most Blu-Rays were Progressive but for some reason this one during playback looks as if its interlaced.

I personally don't think its interlacing if that's true their all progressive, and I assume its a blend perhaps?

Anyone know what this is or the cause of it? It does not seem to go away with IVTC or QTGMC deinterlacers.

[Dougster]

It's 29.97 interlaced. Not a progressive source. MediaInfo says MBAFF (which is interlaced).

[killerteengohan]

So why isnt TIVTC getting it all?

[Dougster]

Good question. I'm checking it now.

[johnmeyer]

I just used a standard IVTC script, and it seemed to work. However, I always drop the video into my NLE (Sony Vegas) and frameserve out of that into the AVS script. This avoids any weirdness with the way video sometimes gets read into an AVISynth script.

Here's the script I used. It is pretty much right out of the cookbook:

AVISource("e:\fs.avi")
AssumeTFF()
converttoYV12(interlaced=false)
tfm(display=false)
tdecimate()

AssumeFPS(23.976, true)

[Dougster]

Looks like it's telecined from on odd framerate at first glance. QTGMC on my end works much better than TIVTC. I've noticed that the
backgrounds seem to run at 23.97 (filmrate) while the characters are animated much slower. Have you tried sRestore with QTGMC?

[killerteengohan]

Looks like it's telecined from on odd framerate at first glance. QTGMC on my end works much better than TIVTC. I've noticed that the
backgrounds seem to run at 23.97 (filmrate) while the characters are animated much slower. Have you tried sRestore with QTGMC?

Ive used QTGMC by itself and it works okay but didnt fully get everything if you examine it frame by frame, but I didnt use it along with srestore.

[jagabo]

Slightly irregular pulldown pattern:

ffVideoSource("00016.m2ts", fpsnum=30000, fpsden=1001)
AssumeTFF()
Crop(240,0,-240,-0)
TFM()
TDecimate(mode=1, cycle=10, cycleR=2)

[killerteengohan]

I never seen cycle or cycleR parameters for tdecimate and I been using it for almost 4 years with just mode and hybrid parameters. did those change the pattern somehow I take it, or was it the assumetff?

The end result looks perfect to me. Thanks I will give that a try.

[manono]

I never seen cycle or cycleR parameters for tdecimate...

Then you should read the manual sometime. I use that mode with some frequency.

did those change the pattern somehow I take it, or was it the assumetff?

The sample is down but that mode is often used when the frame to be decimated isn't one in five but, in this case, two in ten. That is, rather than there being one duplicate frame every five frames, sometimes they might be six frames apart and sometimes four (or 3 and 7). So it averages two duplicates every ten frames. If you just use the normal one in five you might wind up with a remaining duplicate frame sometimes and a missing unique frame sometimes.