DGMPGDec 1.5.6

thanks a lot... _

Just out and already in intense usage for me!...no bug to signal...not yet...;) THANX A LOT!

LOL I was checking for a new version just two days ago. Thanks alot!

Good job Neuron2! DGIndex is now handling everything I throw at it without any problems.

I'm posting this on behalf of someone else. Apparently he has some PAL video that's got pulldown, but dgindex apparently doesn't have any way of handling this kind of pulldown, and he wonders if you can add support for it. ------------------------------------------------- I have an issue with DGIndex and PAL footage. I'm positive that my source is soft telecined PAL, stored as 24fps progressive and with the 2:2:2:2:2:2:2:2:2:2:2:3 pulldown enabled. The issue is that, if I try to either honor or ignore the pulldown flag, the output will be 25fps, which isn't what I want. On the other hand, if I try to force FILM, I get a 20fps output, which I suppose is wrong (also, AFAIK, force FILM is supposed to be used on NTSC only anyway). The source's Video Type is reported as 82.94% Video and the Frame Type is Progressive. I demuxed an m2v along with audio and muxed them in a ts so that you can check for yourself and see what's to be done. Sample:

Your sample looks like normal 25 fps. I checked part from 0:31 to 0:34 and every frame was different. It looks like simple speedup from 23.976 fps -> 25 fps. I wouldn't change enything.

Zarxzarx. Huh, this is an interesting sample with soft-telecined PAL. If it's consistent, you can use "Ignore Pulldown Flags" and then do an AssumeFPS(24) later. Otherwise, process it with "Honor Pulldown Flags" and then use TIVTC with a decimation cycle of 25. Edit: I also think you set the delay wrong because it says it's -600000000000ms. Edit2: I'm also interested in what they did with the 60i/VFR segments in ep 15. Probably some blend garbage. Edit3: FFMS2 says that the framerate is 23.976, although simple PAL ivtc would return 24 fps. FFMS2 is probably (?) right.

It doesn't make much difference. You can have a look at Appendix B in the DGDecode user manual for more discussion about it.

Then basicly I should use 32-SSE2 MMX Algorithm it is optimized for my Cpu?

You can do some testing and then decide what you prefer to use. But as I said, you'll probably not discover any more than is already documented in the Appendix I mentioned. If you do, please report it here.