DGMPGDec 1.5.8

Guest · 6th March 2010, 18:05

Full source code release with only a minor fix for a DGIndex crashing problem with some pathological streams.

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

Groucho2004 · 6th March 2010, 23:23

Hi Donald, thanks for this release!

I did a little experiment creating a VC6 project from the source code for DGDecode you provided and compiling dgdecode.dll.

I created a simple d2v and avs from a mpeg2 clip and ran the script through a simple AVISynth benchmark tool I wrote some time ago.

With the DLL you released I get about 125 fps, with the VC6 DLL I compiled I get about 190 fps! These tests were run on a Core 2 E7400 @3.4 GHz.

I also tried VC7.1 with all kinds of switch combinations but the VC6 compile is simply much faster.

You can try it yourself:
My benchmark tool: AVSInfo
The VC6 (SP6) DLL: DGDecode

I guess when one uses heavy filtering this won't matter that much but for a simple script it makes quite a difference.

Guest · 7th March 2010, 01:32

My DGDecode.dll is built with VC6. Maybe you are running into differences due to caching.

Groucho2004 · 7th March 2010, 01:41

Quote:

Originally Posted by neuron2

My DGDecode.dll is built with VC6. Maybe you are running into differences due to caching.

What kind of caching? Have you tried the DLL I uploaded?

Just for reference, here are the tools I use:
VC6, SP6 with processor pack
MASM 6.15.8803
NASM 2.07

Groucho2004 · 7th March 2010, 01:56

I figured out where the difference comes from. I changed the processor type in "Code generation" from "Blend" to "Pentium Pro".

Guest · 7th March 2010, 02:01

What processor do you have?

Groucho2004 · 7th March 2010, 02:06

Core 2, E7400 @3.4 GHz. It may not make such a difference on an AMD chip.

lansing · 7th March 2010, 07:21

found a bug, when I'm previewing the video with either F5 or F6, when I scroll up in my mouse scroll, the information window disappear while the preview process was still running

Guest · 7th March 2010, 15:53

Fixed for next release. Thanks for the report.

~Revolution~ · 8th March 2010, 23:03

This might not be the place to ask this but I don't quite understand why DGIndex reports some PAL sources as Interlaced (Field/Frame) when I can clearly see individual, progressive frames after selecting the "Ignore Pulldown Flags" option.

Guest · 9th March 2010, 00:11

Because as the user manual states (and as has been discussed here many times) that field reports how the stream was encoded, not what the actual content is.

~Revolution~ · 9th March 2010, 01:25

I just read a lot of material of soft vs hard telecine and mpeg-2 flags and such. I'm sorry for the stupid question. It all seems to make sense now. I have another question however. I have been searching all over and cannot find a precise and clear way of how mpeg-2 flags exactly work. So basically in a soft telecine video the actual content is 23.976 progressive (slowed down from 24) and then with flags this can be converted on-the-fly by the decoder to show 29.976 fps or 59.94 fields/s? So the actual video on the dvd is not divided up into fields but are "artificially" created by the instructions from the flags? Also if this is true then why do dvd studios still use hard telecining vs soft telecining for material originating from 24 fps film?

Guest · 9th March 2010, 01:44

Quote:

Originally Posted by ~Revolution~

I have been searching all over and cannot find a precise and clear way of how mpeg-2 flags exactly work.

See here:

http://neuron2.net/library/mpeg2/iso13818-2.pdf

Quote:

Also if this is true then why do dvd studios still use hard telecining vs soft telecining for material originating from 24 fps film?

Because they receive material already hard-pulled-down, or they are incompetents, or both.

Please start new threads in the appropriate forums for these general questions.

~Revolution~ · 9th March 2010, 02:03

You're awesome

Wilbert · 9th March 2010, 21:40

Quote:

Full source code release with only a minor fix for a DGIndex crashing problem with some pathological streams.

Thanks neuron2!

BuHHunyx · 10th March 2010, 12:17

---------------------------
DGIndex.exe - Entry Point Not Found
---------------------------
The procedure entry point AttachConsole could not be located in the dynamic link library KERNEL32.dll.
---------------------------
OK
---------------------------

Groucho2004 · 10th March 2010, 13:55

Quote:

Originally Posted by BuHHunyx

---------------------------
DGIndex.exe - Entry Point Not Found
---------------------------
The procedure entry point AttachConsole could not be located in the dynamic link library KERNEL32.dll.
---------------------------
OK
---------------------------

You could try the DGIndex I built with VC6, here.

jpsdr · 11th March 2010, 10:02

Quote:

Originally Posted by Groucho2004

Just for reference, here are the tools I use:
VC6, SP6 with processor pack
MASM 6.15.8803
NASM 2.07

With VC6, i was staying at the time at SP5, beacause SP6 doesn't have the processor pack, only the SP5.
Do you know where i can get SP6 + processor pack for SP6 ?
Thanks.

Groucho2004 · 11th March 2010, 15:43

Quote:

Originally Posted by jpsdr

With VC6, i was staying at the time at SP5, beacause SP6 doesn't have the processor pack, only the SP5.
Do you know where i can get SP6 + processor pack for SP6 ?
Thanks.

Here is one solution.

You can also unpack the processor pack files, copy them to the appropriate folders in your VC6 installation and then import the reg file.

jpsdr · 11th March 2010, 15:47

Ok, thanks, i'll try just by curiousity...
Thanks.

6th March 2010, 18:05	#1 \| Link
Guest Guest Join Date: Jan 2002 Posts: 21,901	DGMPGDec 1.5.8 Full source code release with only a minor fix for a DGIndex crashing problem with some pathological streams. http://neuron2.net/dgmpgdec/dgmpgdec.html

6th March 2010, 23:23	#2 \| Link
Groucho2004 Join Date: Mar 2006 Location: Barcelona Posts: 5,034	Hi Donald, thanks for this release! I did a little experiment creating a VC6 project from the source code for DGDecode you provided and compiling dgdecode.dll. I created a simple d2v and avs from a mpeg2 clip and ran the script through a simple AVISynth benchmark tool I wrote some time ago. With the DLL you released I get about 125 fps, with the VC6 DLL I compiled I get about 190 fps! These tests were run on a Core 2 E7400 @3.4 GHz. I also tried VC7.1 with all kinds of switch combinations but the VC6 compile is simply much faster. You can try it yourself: My benchmark tool: AVSInfo The VC6 (SP6) DLL: DGDecode I guess when one uses heavy filtering this won't matter that much but for a simple script it makes quite a difference. Last edited by Groucho2004; 7th March 2010 at 01:24.

10th March 2010, 12:17	#16 \| Link
BuHHunyx Registered User Join Date: Dec 2009 Posts: 7	w2k still doesn't work --------------------------- DGIndex.exe - Entry Point Not Found --------------------------- The procedure entry point AttachConsole could not be located in the dynamic link library KERNEL32.dll. --------------------------- OK ---------------------------

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

7th March 2010, 01:32	#3 \| Link
Guest Guest Join Date: Jan 2002 Posts: 21,901	My DGDecode.dll is built with VC6. Maybe you are running into differences due to caching.

7th March 2010, 01:56	#5 \| Link
Groucho2004 Join Date: Mar 2006 Location: Barcelona Posts: 5,034	I figured out where the difference comes from. I changed the processor type in "Code generation" from "Blend" to "Pentium Pro".

7th March 2010, 02:01	#6 \| Link
Guest Guest Join Date: Jan 2002 Posts: 21,901	What processor do you have?

7th March 2010, 02:06	#7 \| Link
Groucho2004 Join Date: Mar 2006 Location: Barcelona Posts: 5,034	Core 2, E7400 @3.4 GHz. It may not make such a difference on an AMD chip.

7th March 2010, 07:21	#8 \| Link
lansing Registered User Join Date: Sep 2006 Posts: 1,678	found a bug, when I'm previewing the video with either F5 or F6, when I scroll up in my mouse scroll, the information window disappear while the preview process was still running

7th March 2010, 15:53	#9 \| Link
Guest Guest Join Date: Jan 2002 Posts: 21,901	Fixed for next release. Thanks for the report.

8th March 2010, 23:03	#10 \| Link
~Revolution~ Registered User Join Date: Sep 2009 Posts: 89	This might not be the place to ask this but I don't quite understand why DGIndex reports some PAL sources as Interlaced (Field/Frame) when I can clearly see individual, progressive frames after selecting the "Ignore Pulldown Flags" option.

9th March 2010, 00:11	#11 \| Link
Guest Guest Join Date: Jan 2002 Posts: 21,901	Because as the user manual states (and as has been discussed here many times) that field reports how the stream was encoded, not what the actual content is.

9th March 2010, 01:25	#12 \| Link
~Revolution~ Registered User Join Date: Sep 2009 Posts: 89	I just read a lot of material of soft vs hard telecine and mpeg-2 flags and such. I'm sorry for the stupid question. It all seems to make sense now. I have another question however. I have been searching all over and cannot find a precise and clear way of how mpeg-2 flags exactly work. So basically in a soft telecine video the actual content is 23.976 progressive (slowed down from 24) and then with flags this can be converted on-the-fly by the decoder to show 29.976 fps or 59.94 fields/s? So the actual video on the dvd is not divided up into fields but are "artificially" created by the instructions from the flags? Also if this is true then why do dvd studios still use hard telecining vs soft telecining for material originating from 24 fps film?

9th March 2010, 02:03	#14 \| Link
~Revolution~ Registered User Join Date: Sep 2009 Posts: 89	You're awesome

11th March 2010, 15:47	#20 \| Link
jpsdr Registered User Join Date: Oct 2002 Location: France Posts: 2,635	Ok, thanks, i'll try just by curiousity... Thanks.