Log in

View Full Version : MPEG2Dec3dg.dll vs. DGDecode.dll


halpern
30th January 2005, 14:33
Can someone please tell me the difference between these two files? Why would you use one as the decoder and not the other? Thanks.

Guest
30th January 2005, 14:51
mpeg2dec3dg.dll is an earlier release of the decoder, which was subsequently renamed to dgdecode. You have to be careful which one you use, because they are paired with the indexing utility that generates the D2V file:

DVD2AVIdg <--> mpeg2dec3dg.dll
DGIndex <--> dgdecode.dll

So you need to know which version of the indexer that RB is using.

halpern
30th January 2005, 14:53
Are you using v .70 of dvd-rb and if so what decoder are you using? Thx

wmansir
30th January 2005, 15:45
Since DVD-RB now supports DGDecode I don't see any reason that MPEG2DEC should be used. For the most part they will both work identically, but there are rare occasions where DGDecode has been reported to work where MPEG2DEC fails.

pg55555
30th January 2005, 23:51
Apart from Wmansir comments, it is my understanding that the usage of one or other file it is transparent to a RB user: Just set the path to the decoder .dll you are using in the Setup and RB will take care of generating the right D2V files.

One point you must be carefull if decide to use mpeg2dec3dg.dll is teh version: Only the 1.0.1.0 version worked with RB. Newer ones such as 1.0.3.0 had problems. This is another reason to go with dgdecode.dll

eriksen76
31st January 2005, 01:33
I use DGDecode from DGMPDEC 1.1 final

Works like a charm

Are there any newer versions?? Or should I stick with this one

/Eriksen76

MaxT
31st January 2005, 01:39
DGDecode.dll comes from DGMPGDec (MPEG2 Decoder and Frame Server).

There's 1.2.0 beta 4 out, you can read more @
http://neuron2.net/fixd2v/decodefix.html

Personally I still use 1.1.0

Guest
31st January 2005, 05:02
1.2.0b4 DGDecode is very stable and has a fix for de-ringing in the postprocessor. We're still wringing bugs out of DGIndex 1.2.0b4.

MaxT
31st January 2005, 09:56
Sounds nice, thanx for the "report" :) I'll upgrade to 1.2.0b4.