DGDecode 1.1.0+ by NaN

[Carpo]

p4m - thats prob a laptop - laptop i have says its a 1.8 but its speed reported by windows and linux have both said 1.2 - so thats prob why the speed off cce on there isnt great

[SamuriHL]

Mine's a Dell Inspiron 9300, so, yes, a laptop. It's amazingly fast for a laptop. I truly love this thing. I generally do all my encoding on my two video machines...an athlon xp 2500+ and an athlon xp 2100+ both with a gig of memory...but when I do use the laptop I find it's quite fast. I just did an encode of Batman Begins in a little over 2 hours...speed was between 2.5 and 4 on most of the files. I really can't complain at all. I do tend to use my external hard drive through firewire, as well, and that helps quite a bit. I don't want to beat on the internal hard drive too much for video editing/reencoding.

[FredThompson]

On the "trouble" PAL DVD I've been testing, the latest SEE build will work with the first segment of two which build 1.1.0 hates. The second segment is a failure. DGDecode won't load it. Darn. Getting there, something's not quite right, though. DGDecoe 1.4.5 loads both segments flawlessly.

[blueboyec]

So to use DGDecode 1.1.0+ by NaN have to do the following:
Options: ---> AVS Options:---> Advance Options:---> Set Decoder idct: 32 bit SSE2/MMX

Is this correct?

Thanks for the help in advance.

[Carpo]

no just put the dll is the same dir as dvdrb.exe

[luphy]

Hmmm, that's odd. My 1.74 P4M gets higher than that on a consistant basis. What speed is the hard drive on that thing and how much mem do you have? I have a gig of ddr2 and a 5400 80 gig drive on mine. You should be seeing a bit faster than that I'd think. This new dll definitely improved things for me, as well. Probably close to 20% increase.

The Dell 9300 series laptops have a newer generation CPU compared to my 8500 Dell laptop - and the FSB speed is faster too. The newer 9300 have the Pentium M, which is probably 2 generations newer than my P4-M. A 1.7Ghz Pentium M is probably equivalent to a 2.8 or higher P4-M. And the 9300 has a bigger cache and a 533Mhz FSB versus 400Mhz for the P4-M.

[SamuriHL]

Well that would certainly explain it then. :) I wasn't aware of the differences. Technically, I'm not a huge intel fan, but, I wanted a laptop and the centrino chipset certainly gave the best performance and battery life when I bought it. That's probably still the case. I will say that I have absolutely enjoyed the 9300 since the day I got it. No complaints at all.

[Carpo]

running the encode i am now i can deff say there is an improvement in speed - this could be due to nans dll or new avisynth im using - you never know

but on a film here with 54.4% compression using UnDot().Deen() its sitting at about 2 on encoding speed where with other dll it says at about 1.4-1.5 so i would say there is deff improvement and a real case for dvdrb v1.10 to support neuron2 version (stable one when dvdrb 1.10 is done) and/or nans updated one if he updates it

although this is just my thought, jdobbs is the man who will decide (i have already asked for support int he wish list thread :) )

all in all its a great piece of kit either way and well worth the money i donated :D

EDIT: doing a film with idct 3 undot and deen and getting 1.8 (now that may not seem much) but with other dll it was 1.3 - so i would say that nans improvements to neuron2 version have had som beifits for me :)

[blueboyec]

Carpo/NAN or anyone else,

So I do not have do anything else other than put the dll in the same dir as dvdrb.exe?

Just woundering what most people set Decoder idct to, I currently have it set to 32 Bit Simple MMX(XVID)? What does the default set it to?

Thanks



no just put the dll is the same dir as dvdrb.exe

[Carpo]

yip just put nans dll in same dir as dvdrb.exe

think dvdrb defaults to idct 7 - i have mine set to 3 - would use 4 but think there is issues with ieee one

[writersblock29]

@blueboyec

All you have to do is drag and drop Nan's dll into whatever folder your usual DGDecode dll is located, and answer "yes" to the warning window that will appear (the window says something about 'are you sure you want to replace *DGDecode* with *New File*). Or -- if you'd like some insurance without finding your original dll on the internet again, just move the original dll to another folder... replace it with Nan's... and you're off. If you run into any problems with Nan's driver, then you can always replace it with your original. Of course, if you do run into trouble with Nan's driver (and I'm sure he'd agree with this), post it here so that he can check it out.

If you used the DVDRB installer, then I beleive it automatically puts the DGDecode dll into the same folder as the Rebuilder EXE. To be sure where the original DGDecode file is, open Rebuilder, run Setup, and follow the path listed.

[blueboyec]

Carpo and writersblock29,

Thanks for your response.

I was just asking the previous questions to find out if there are any extra benefits to setting Decoder idct: to 32 bit SSE2/MMX since Nans dll is using SSE2 for improving speed. I have had no problems after installing the dll, just trying to find out if we could speed up RB in other ways.

[Carpo]

l, just trying to find out if we could speed up RB in other ways.

get a fast pc ;D

normaly encodes on my pc arent that bad - if you add filters and change the idct then this will slow down your encodes - its best to leave the settings as default - unless you really know what your doing ;)

[NaN]

@ blueboyec: just stick with xvid simple (MMX), it's a very nice one (fairly high precision with high speed). The SSE & SSE2 builds are just a bit better matched to the particular cpu architecture.

Cheers, NaN

[blueboyec]

NaN,

Thanks. My CPU info indicated MMX, SSE and SSE2. Based on this info do you still recommend xvid simple (MMX)?

Thanks again.

BB

[masscamp24]

Is itm ok for me to try this decoder

[Jeffster]

Thanks. My CPU info indicated MMX, SSE and SSE2. Based on this info do you still recommend xvid simple (MMX)?
I think you're confusing two separate issues...

If you want to try this alternative decoder, the .dll you choose (SSE1 or SSE2) depends on your CPU... the iDCT algorithm is a function of the .dll and you can choose any one that is supported by your CPU.

If you want more information on choosing an iDCT algorithm there are several threads (http://forum.doom9.org/showthread.php?t=94925) on this forum about them and the pro's and con's of each, or read the DGDecode manual... but as NaN said, Simple iDCT (XviD) is a good choice.

[Rippraff]

Is itm ok for me to try this decoder
Yes !

[masscamp24]

Thanks for your quick response RIPPRAFF. However do I replace the existing decoder in the DVD-RB folder with this one? Does it affect the quality in anyway? Please bear with me, I'm new and a rookie to all of this. However DVD-RB PRO is a FANTASTIC!!!!!! program.

[blueboyec]

Jeffster and NaN,

Thanks for the info. I'll sick with Simple iDCT (XviD).


BBec

[jdobbs]

However DVD-RB PRO is a FANTASTIC!!!!!! program. Good observation. ;)

[rkr1958]

I'm using NaN's decoder which is dated 10/14/1004 and is located in
C:\Program Files\DVD-RB PRO\DGDecode.dll

The one I'm using for AviSynth 2.5 is dated 1/21/2005 and is located in
C:\Program Files\AviSynth 2.5\plugins\DGDecode.dll


I'm running a P4 Northword 2.6-GHz CPU, which does have SSE2. I did notice a speed up in CCE-basic and a decrease in run times. Thanks NaN ...

I have a question though, do I have to worry about the above two version of DGDecode.dll conflicting with each other when I run either DVD-RB Pro or an AviSynth script?

Also, if I updated AviSynth to it's latest version will that work with DVD-RB? If not, what's the highest version of AviSynth that does?

Thanks.

[jdobbs]

The two versions of dgdecode shouldn't conflict. You just have to specifically include the "load" statement in any AVS that is using the one in the "DVD-RB PRO" directory (as DVD-RB does).

[jdobbs]

AVISYNTH v2.5.5 is the latest that has been completely tested and certified (if there is such a thing) with DVD-RB. There were some problems with v2.5.6 during development -- but I don't know if they still exist.

[Carpo]

there is this

http://forum.doom9.org/showthread.php?p=729821#post729821

although i dont know what plugins are affected

[jdobbs]

???? v2.5.7 isn't even listed on the sourceforge site:

http://sourceforge.net/project/showfiles.php?group_id=57023

[Added] Never mind... it appears they are currently working on it... and it isn't even in Alpha release yet.

[feedback]

there is this

http://forum.doom9.org/showthread.php?p=729821#post729821

although i dont know what plugins are affected
@Carpo
Thanks for the heads up with the link you posted!
I have been using AviSynth 2.56, build: Jan 31, 2005 [21:37:08]
for a couple of months with no apparent problems, but I see that the potential for problems, using 2.56, does exist with plugins.

Regards,:)

[Carpo]

im guessing they have sorted it as the src and exe is back on the download page at sourceforge

@feedback

i been using for few weeks with no issues - just plugins are affected and i dont use em (much) :p