DGMPGDec 1.5.6

[neuron2]

1. Added Unix-style CLI parsing. The legacy parsing is also supported. The new parsing allows for commas and spaces within file names.

2. Revised the audio header emulation check to prevent it from rejecting some valid audio.

3. Increased the timeout for finding transport packets from 3 to 5 seconds.

4. Properly ignore some program stream filler packets that do not specify the correct packet length.

5. When a new transport stream is loaded without exiting DGIndex, the PIDs are now re-determined (without requiring the user to reset them as was previously the case).

6. Fixed a bug in which normalization was being used erroneously when demuxing audio (could happen if you were decoding AC3 to WAV with normalization enabled and then you set the mode to demux audio without unchecking the normalization option).

7. Fixed a bug in the Cropping dialog such that the height field was not properly set after changes were made.

8. Improved reliability of stream type detection upon file open.

http://neuron2.net/dgmpgdec/dgmpgdec.html

[b66pak]

thanks a lot...
_

[MatLz]

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

THANX A LOT!

[Egh]

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

Thanks alot!

[Nomolu]

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

[Zarxrax]

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: http://www.sendspace.com/file/jpzzjo

[Atak_Snajpera]

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.

[thewebchat]

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.

[SilaSurfer]

hey Neuron2 great tool thanks. I wanted to ask you which iDCT Algorithm do you suggest, i have a Pentium IV dual core processor and is there a quality
difference between them. I'm backing up my DVDs

[neuron2]

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

[SilaSurfer]

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

[neuron2]

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.

[SilaSurfer]

Ive read somewhere I'cant really remember where somebody had problems with macroblocks with IEEE-1180 Reference algorithm . It was with Dgindex 1.50 version on DVD source input. Is this true?

[neuron2]

There was an early bug but it was fixed long ago. Anyway there's no need to use that one as it is slower.

[SilaSurfer]

Slow for quality I don't mind as its written in the manual:
Qualitywise: IEEE-1180 Reference > 64-bit Floating Point > Simple MMX (XviD)
Speedwise: SSE2/MMX and SSE/MMX (Skal)

[SilaSurfer]

Hey Neuron, could you please close this thread that I created, I asked the same question here and in thread, I'm sorry about it it won't happen again. Thanks
http://forum.doom9.org/showthread.php?t=150756