Support forum for DG Tools

Hallo !

i just tried to use DGDecNV for the first time and it does not work.
I tried several different h264 clips in a m2ts or mkv container but i just get the same message:

GPU Decoder:failed to create video decoder (100)

The Card here is a GT430 based card.

LAV with Cuvid and madVR work fine, so they definitely have no proplem to access the GPU.

OS is Windows7 64Bit.

DGDecNV is also listing the GT430 as a GPU device.

Any hints for what i should check ?


Thanks for reading

Which version of DGDecNV are you using? Are you trying to run the 32-bit or 64-bit DGIndexNV? Finally, please email me your user ID you received at activation, as I cannot find your name in my database. Thank you.

I am using the latest DGDecNV version (2041).

I tried to use both versions (32 and 64 Bit), same result.

But i just used the 64 Bit in order to check it out , despite the fact that it, according to the instructions, would require a 64 Bit AviSynth Version, which is not the case here anyway.

My installed AviSynth Version is 2.6 Alpha 3 32Bit (taken from here: http://sourceforge.net/projects/avisynt ... 110525%5D/)

, altered to 2.6 MT by using Set`s build ( http://forum.doom9.org/showthread.php?t=148782).

Nvidia Driver Version is 295.73


Thanks for reading

I just checked out one more thing:

It looks like i can create valid dgi-files with DGDecNV via Save Project or Save Project & demux Video,

but any attempt to open them with virtualdub produces a virtualdub error like this:

"File "C:\test.avs" does not have a video stream"

Opening the same original file simply via DirectShowSource works fine.


Thanks for reading

Hi Arthur.

Do you see video in the 64-bit version of DGIndexNV?

Please post your Avisynth script. Thanks.

Also, we can test your Avisynth installation. Make a simple script called version.avs with just this in it:

Version()

Then open that in VirtualDub using File/Open video file. What happens?

Sorry for your trouble with my tools. I hope we can figure it out.

Hi,

No, the 64-bit version of DGIndexNV behaves just like the 32-bit version.
Same error :GPU Decoder:failed to create video decoder (100)

The Avisynth script i used goes like this:

LoadPlugin("Z:\Software\Video\dgdecnv2041\DGDecodeNV.dll")
dgsource("C:\2011-12-04--16-26-58.dgi")

When i open up a simple script called version.avs with just this in it:

Version()

VirtualDub shows , as it should, this:

AviSynth 2.60, build:Sep 13 2011 (03:56:35)


In case it helps tracking down the problem :

your DGDecNV-predecessor DGAVCIndex does show a video.


Thanks for reading & support

You can try an earlier driver such as 280.26.

How much memory is on your card? Use GPU-Z to find out how much memory is available at the time you start DGIndexNV.

I tested driver version 280.26.
Unfortunately it didn`t change anything.

There are 1024 MB on the card, and more than 950 MB are available when i start up DGIndexNV.

Thanks for reading

Sorry, I don't know where to go from here. I'll issue you a refund if you email me the paypal transaction #.

Did you try with Avisynt 2.5.8?

Thanks, Nick, but DGIndexNV doesn't use Avisynth. DGIndexNV can't open CUVID on that system (assuming no PEBKAC), so
Avisynth hasn't entered the picture.

Stupid question most likely but... you aren't running DGIndexNV remotely over RDP (Remote Desktop Protocol), are you?

@kypec

No, there is no RDP involved here.

@admin

Thanks for the refund-offer but i am not used to giving up so quickly
Especially if , like in this case, it somehow should work, since the problem is that
DGIndexNV can't open CUVID on my system But LAV can.

So the question is what is LAV doing differently in comparison to DGIndexNV ?
Are there several possible ways for a program to access the GPU (opening CUVID) ?
Is there a way to get something like a detailed logfile from DGIndexNV besides the error message ?

Who knows, maybe my problem will finally produce dgdecnv 2042 as a result....

He said he gets the CUVID error in DGIndexNV. Sure, you can still create an index, but if you can't open CUVID, you won't get anywhere with it. Remember, indexing is just parsing the source stream and writing some data. It doesn't use CUVID.

Is this only occurring when using VirtualDub?

Have you tried opening the avisynth script using media player classic? Does that show any video?

DGIndexNV itself fails to open CUVID and show video, according to Arthur. That doesn't use VirtualDub or Avisynth! CUVID cannot be opened on Arthur's system for some reason.

You only need CUVID to decode and draw the pretty video pictures.

Maybe a stupid question, but you haven't got mismatched nvcu*.dll files in your DGIndexNV and windows\system32 folders by any chance?

Well, there are plenty of nvcu*.dll files in my windows/system32 and windows/syswow64 folders ,
but how shall i tell wether or not they are mismatched ?

Keep in mind, there is another piece of software on my machine here which is succesfully using CUVID, and this is LAV.
So i am pretty sure that previous suggestions about posting dgi files, sample videos and so on will not solve the problem.
And so: yes, i can open h264 content with MPC-HC with LAV and madVR.
Also opening my files via DirectShowSource (which uses LAV since i configured it this way) in VirtualDub works.

There must be a difference in how LAV and DGIndexNV are calling CUVID, or not ?

I guess the next thing i try is putting the graphics card into another computer to test it there.

Marking resolved as OP has apparently abandoned the thread.