DG NV tools

[LigH]

It is probably again the usual misunderstanding.

It requires an Nvidia card which supports CUDA, because (simply said, despite possible exceptions?) only cards which support CUDA also have the PureVideo decoder chip in version VP2 (or better).

But DGDecNV does not execute CUDA programs to decode. It only uses the PureVideo VP2(+) decoder chip features on these cards.

[mastrboy]

Actually DGDecNV has 2 two different modes for decoding, from the manual:

Decode_Modes=0/1,0/1,0/1: The order of the parameters corresponds to AVC video, MPEG2 video, and VC1 video. 
A value of 0 selects CUVID decoding; a value of 1 selects CUDA decoding. For example, "Decode_Modes=0,1,0" causes 
CUDA to be used for MPEG2 video and CUVID for AVC and VC1 video. By default, CUVID is used for all video types.

[Pat357]

Originally Posted by mastrboy

Actually DGDecNV has 2 two different modes for decoding, from the manual:

Decode_Modes=0/1,0/1,0/1: The order of the parameters corresponds to AVC video, MPEG2 video, and VC1 video. 
A value of 0 selects CUVID decoding; a value of 1 selects CUDA decoding. For example, "Decode_Modes=0,1,0" causes 
CUDA to be used for MPEG2 video and CUVID for AVC and VC1 video. By default, CUVID is used for all video types.

If what you say is valid, I'm wondering where the CUDA code is hidden to decode MPEG, VC1 and H264
Even with CUDA, it would be a lot of code for the 3 main formats.
And more over, why would anyone use CUDA for decoding streams when you can access the the Video Processor (VP2..VP4..VP5)
using CUVID which can decode these streams already and this all without even writing a single line of code to do the actual decoding ?

[Guest]

When CUDA is used, it is not done 100% in CUDA. There is acceleration of some things but mostly it is done in the video driver software. The reason to need it is the rare occasion when the VP engine is broken for a particular stream's syntax. It's very rare.

[alzamer2]

when i use the driver that which come with my laptop (geforce g 105m -with cuda-) DGIndexNV work
but after i upgrade the driver (lastest one cuda 5.0.1 and tried cuda 4.2.1) i get error ERROR: cuInit failed (100) why?

[Guest]

I don't understand what you mean by cuda drivers. You should install a video driver, not a cuda driver. Why do you talk about cuda drivers?

I do know that some older notebook graphics chipset drivers are not being updated to be compatible with the latest CUDA SDK. You simply cannot upgrade those video drivers without losing support. I cannot do anything if nVidia doesn't release compatible drivers. You can fall back to an earlier DGDecNV version build with CUDA 3, however. Sadly you can't have the latest versions of both the video driver and DGDecNV.

[alzamer2]

Originally Posted by neuron2

I don't understand what you mean by cuda drivers. You should install a video driver, not a cuda driver. Why do you talk about cuda drivers?

I do know that some older notebook graphics chipset drivers are not being updated to be compatible with the latest CUDA SDK. You simply cannot upgrade those video drivers without losing support. I cannot do anything if nVidia doesn't release compatible drivers. You can fall back to an earlier DGDecNV version build with CUDA 3, however. Sadly you can't have the latest versions of both the video driver and DGDecNV.

i mean that i have the last video card drive version 306.23 with nvcuda.dll version 5.0.1
but get error ERROR: cuInit failed (100)

[Guest]

Only the last Verde driver will work on those notebook adapters in my experience.

[alzamer2]

Originally Posted by neuron2

Only the last Verde driver will work on those notebook adapters in my experience.

what do you mean by "the last Verde driver"

[Guest]

http://www.geforce.com/drivers/results/26388

[alzamer2]

Originally Posted by neuron2

http://www.geforce.com/drivers/results/26388

will this work ??
http://www.geforce.com/drivers/results/47420

[Guest]

I don't know offhand. You can always try it and revert back if needed. If it works please let me know. Thanks!

[Guest]

Originally Posted by crasus

I very much appreciate your quick reply.

It always occured from streams demuxed straight from the Bluray.

In this case, here's the BluRay we're talking about : http://www.amazon.fr/aventures-rabbi...3945127&sr=8-2

Some changes went in to address this between the version you had back in 2010 and the current version. I've just tested 2043rc1 with Avatar and in fact EAC3TO lost one frame at the end compared to DGDecNV. So I consider this one resolved. Better late than never, eh. Of course, let me know if you run into this with the latest DGDecNV.

[Pat357]

Originally Posted by neuron2

I've just tested 2043rc1 with Avatar and in fact EAC3TO lost one frame at the end compared to DGDecNV.

Neuron2, are there any binaries from this v2043rc1 available for testing the new DXVA HQ de-interlacer ?
I would be happy to test it :-)

[Zathor]

Here you go:
http://forum.doom9.org/showthread.php?t=165970

[Guest]

Originally Posted by Pat357

Neuron2, are there any binaries from this v2043rc1 available for testing the new DXVA HQ de-interlacer ?
I would be happy to test it :-)

Zathor's and my testing didn't show any noticable improvement, which surprised me given what I read in one of the LAV threads. I'm investigating that.

[RedDwarf1]

I think that I might of found an obscure bug in 2042.

I don't usually use the cropping feature and usually click no when I get prompted. However I did by mistake click yes and then quickly wanted to remove that by Entering the cropping selection dialogue and unticking the cropping and then clicking the X. I thought everything would be okay and I could then setup the cropping manually as usual.

However, that didn't work. The dgi file shows the video dimensions as 1920 x1096! Which with my usual cropping setup of 8 left me with a green bar at the bottom and the resolution showing as 1920x1088, after cropping!

I have repeated the steps with the same result. This was with a .h264 raw file.

H.264 video 1920x1088. That is reported by DGIndexNV and is how it should be but MediaInfo reports 1920x1080.

[RedDwarf1]

Ouch! I tested again but this time changed the cropping of the bottom to 16, from it's original 8 and now the resolution is shown as 1920x1104 in the dgi file. The cropping needs to be deselected for this to occur.

It's the same in the latest 2043rc1.

[Guest]

Yup, I've reproduced it. I'll correct it for 2043. Thank you for pointing it out.

[RedDwarf1]

Thank you neuron2, another bug squashed.