View Full Version : DG NV tools
colinhunt
29th February 2012, 09:29
Just fire up DGIndexNV and try to load a file.
Tested with a few m2ts files. All opened without problems... but last night's BD-RB run had stopped at the beginning (0.20%) of the 2nd pass of the main movie file. No error messages on screen. Laptop was all fine otherwise, had not crashed or frozen; BD-RB was simply stuck waiting for input and reacted immediately to clicking of the Abort button. Previous DGDecNV related errors had all occurred at the start of an encoding run so I'm assuming this was one of them as well.
Guest
29th February 2012, 14:01
You'll need to ask jdobbs about this.
colinhunt
29th February 2012, 16:14
You'll need to ask jdobbs about this.
One possibility sprang to mind. The laptop has a specific button for turning the display off and I use it often as I've turned all display related power saving features (dimming etc.) off. Could turning off the display also affect how the graphics adapter is available to DGDecNV?
Shevek
29th February 2012, 17:10
One possibility sprang to mind. The laptop has a specific button for turning the display off and I use it often as I've turned all display related power saving features (dimming etc.) off. Could turning off the display also affect how the graphics adapter is available to DGDecNV?
quite possibly. DGDecNV certainly doesn't work when I connect to my desktop via RDP (which uses a different video driver)
Test it by playing the video in DGDecNV then switching the screen off. See if there are any errors when you switch it back on.
colinhunt
29th February 2012, 17:36
quite possibly. DGDecNV certainly doesn't work when I connect to my desktop via RDP (which uses a different video driver)
Test it by playing the video in DGDecNV then switching the screen off. See if there are any errors when you switch it back on.
I ran another backup job with BD-RB with DGDecNV enabled, but never turned the display off. The job finished without problems.
Next I loaded an m2ts from a Blu-ray into DGDecNV, played it and turned the display off. After 10 seconds I switched the display on again: no error messages and playback was running normally. Hmmh.
linkRed
5th March 2012, 14:09
Is it possible that DGDecNV would show the frame info, while working under with AvsP, like ffvideosource?
http://i038.radikal.ru/0908/69/95fd4a89b06e.png
Which script should I be putting into AvsP for that?
Guest
5th March 2012, 15:14
You can use that same method. There is also a debug option to DGSource(). For AvsP specific questions you should ask in an AvsP thread.
linkRed
5th March 2012, 20:11
Yes, but what does the script should say in that case?
AvsP won't recognize command DGDecodeNV(***)
rack04
5th March 2012, 20:20
Yes, but what does the script should say in that case?
AvsP won't recognize command DGDecodeNV(***)
DGSource("C:\My Files\project.dgi")
linkRed
5th March 2012, 21:19
No-no, how do I do that without indexing?
Asmodian
5th March 2012, 21:25
No-no, how do I do that without indexing?
Do what without indexing? Use DG NV tools? You don't.
linkRed
5th March 2012, 22:17
Well, bummer. But at least now I know it is impossible. Informed = armed! Thanks.
Guest
5th March 2012, 23:26
It's very simple to make an index. Why do you shy away from it?
hajj_3
10th March 2012, 23:23
out of curiosity, has there been any development on an AMD accelerated version of this application, i remember you were waiting for a newer SDK a while back to possibly add support?
Guest
11th March 2012, 00:10
Sorry, no progress on AMD support.
Guest
13th April 2012, 14:07
I would be grateful for testing of this 2042 release candidate:
http://neuron2.net/dgdecnv/dgdecnv2042rc1.zip
I especially need it to be tested on GTX 680. Thank you.
LigH
13th April 2012, 16:06
I may have to recreate my license but lost the link to the license generator page at neuron2.net; could someone please remind me (via PM, if not publicly)?
__
OK, found it (http://forum.doom9.org/showthread.php?p=1412937#post1412937).
Asmodian
13th April 2012, 18:14
Version 2042rc1 works here. I tested the indexing of rat.h264 with both the 32 and 64 bit versions. I also checked that the index of rat.h264 opened with DGSource() (DGDecodeNV.dll) in 32bit Avisynth 2.6 alpha 3 and looked correct in Virtualdub 1.9.11 32842.
neuron2, Thanks for the quick support of the GTX 680. :)
This computer:
Windows 7 x64
Intel i7 980
Nvidia GTX 680
24GB RAM
Guest
13th April 2012, 19:18
You're welcome and thank you for your testing. This version changed the way the correct CUBIN file is determined, so I was unsure if it still worked with GTX 680. Looks like we are good to go.
:thanks:
Guest
14th April 2012, 00:48
neuron2, Thanks for the quick support of the GTX 680. I just wanted to add that it would not have been possible without the always excellent support I receive from nVidia. There were issues with the 64-bit support in CUDA 4.2 versus 3.1, and nVidia very promptly responded to my queries and showed me the way. Over the years, I have been unable to find sufficient superlatives for the support they give me.
InsulinJunkie
14th April 2012, 23:45
There were issues with the 64-bit support in CUDA 4.2 versus 3.1
FWIW, this RC does solve the long-standing problem I had where I needed to stay w/285.62 drivers (64-bit Win7 and 64-bit DGIndexNV, with a GT 240). Otherwise, any newer drivers would crash with BluRay files when I attempted to open them.
Now I'm able to open BluRay files with more recent drivers, so thanks!
CruNcher
15th April 2012, 01:19
I just wanted to add that it would not have been possible without the always excellent support I receive from nVidia. There were issues with the 64-bit support in CUDA 4.2 versus 3.1, and nVidia very promptly responded to my queries and showed me the way. Over the years, I have been unable to find sufficient superlatives for the support they give me.
The Goal was a superlative Ecosystem and they build that up at a massive scale and speed and it's good that they understood 1 Key is to support anyone in that Ecosysten and not to put to much under NDA as well and make it as easy as possible with very good designed APIs, the direct engineering support for DGDecNV from day 1 shows this very well bug reports where taken serious and this way nvcuvid.dll improved @ a massive speed as well by all the 3rd parties involved being today very stable :)
With this strategy they build up a Dev community and overall Apllication Support ATI/AMD can still dream off, Intel also seems to understand these needs and chance correct their MediaSDK is as of the same Quality as how Nvidia started with ;)
http://forum.doom9.org/showthread.php?t=164555
cweb
23rd April 2012, 09:41
In case anyone had the error "Failed to create video decoder (100)" like I had when switching to SET's latest Avisynth 2.6 build (when using dgsource() ), the potential solution is to delete any old nvcuvid.dll you have lying around (in my case in the avisynth plugins directory).
Details are here (http://forum.doom9.org/showthread.php?p=1571381#post1571381).
BTW I would like to thank neuron2 for the latest RC.
VideoFanatic
22nd August 2012, 19:49
Neuron2, could you please explain to me as simply as possible what DGDecodeNV does? I get that it supports file formats not supported by the free version of DGMPGDec but other than that I don't see what the benefit is compared to DGMPGDec.
I was using Avisynth 32-bit with MT and DGMPGDec (free) and I used Simple x264 Launcher to encode my MPEG2 videos. I am using McTemporalDenoise to denoise my videos. I have an 8 core PC and I'm getting around 11 FPS encoding speed. The CPU usage is near 100%.
I was told that your program uses my graphics card instead of my CPU to encode the videos. So I bought a cheap £30 CUDA VP5 card (I was told that I didn't need to buy an expensive card as long as it had CUDA VP5) and I bought your program. I did everything the same as before but replaced DGMPGDec with DGDecodeNV. I tried without MT mode and got 2 FPS and it was still using a little bit of the CPU. I tried with MT mode and I got around 9 FPS which was slower than if I used DGMPGDec (free) and again it was nearly using all the CPU.
Am I using the program incorrectly? Why is the program using the CPU when I thought it was supposed to use my graphics card?
I have several things in my script but the only thing I changed when I used DGDecodeNV was the bolded line.
setmtmode(5,12)
DGSource("J:\File.dgi")
setmtmode(2,0)
Is DGDecodeNV frame acurate?
Why doesn't it have a similar function to CPU=6 as DGMPGDec does?
Guest
22nd August 2012, 20:22
I was told that your program uses my graphics card instead of my CPU to encode the videos. You have been misled. One thing you might try doing is reading the DGDecNV documentation to determine its functionality.
Am I using the program incorrectly? Why is the program using the CPU when I thought it was supposed to use my graphics card? I will assume you did not misspeak in saying you expect DGDecNV to use the GPU to *encode* your videos. How is a decoder going to use the graphics card for encoding? Did you see the "Dec" in DGDecNV? It stands for Decoder. The title of the web page says "AVC/MPG/VC1 Decoder and Frame Server". How could you possibly think it would have anything to do with encoding? If you did misspeak, please try again, being as precise as possible.
Is DGDecodeNV frame accurate? Of course.
Why doesn't it have a similar function to CPU=6 as DGMPGDec does? I couldn't use the code due to GPL, I never use that postprocessing myself anyway, it's arguably not very good and it can be done better with external filters, and finally there is not equivalent functionality for AVC and VC1 while I prefer to have a unified experience for all video formats.
If all you ever deal with is MPEG2, you may find DGMPGDec adequate, but even with MPEG2 there is a lot of additional functionality in DGDecNV that many find useful: MKV support, Output Trimmed TS, MPLS support, GPU deinterlacing/resizing, autocrop, better GUI, etc., etc.
DGDecNV was really made for BluRays, so AVC and VC1 support are crucial. As I said, if all you work with is DVD then you may find DGMPGDec perfectly adequate. I'll be happy to refund your donation if you'd like to send me an email.
VideoFanatic
22nd August 2012, 21:28
Thanks but I will use the program in future with h.264 files so I don't need a refund. So from what I understand your program supports different file formats and it uses the Graphics card's GPU when making a project file instead of the CPU? And basically a CUDA card is needed just so your program will function. Is that correct?
Just wondering though, why does my MPEG2 video encode to h264 a couple of FPS slower than when using DGMPGDec?
From what I understand CPU=6 has the same stength of deblocking as CPU=4 but it adds deringing? Is that correct? You said you don't like CPU=6 as there are better filters to use. Could you please recommend the best one in your opinion?
Guest
22nd August 2012, 21:51
Thanks but I will use the program in future with h.264 files so I don't need a refund. So from what I understand your program ... uses the Graphics card's GPU when making a project file instead of the CPU? No, decoding of video frames occurs on the GPU. Saving a project does only parsing and no decoding. When you either play video in DGIndexNV or execute your Avisynth script then the GPU will be used for decoding, and also optionally for deinterlacing and resizing/cropping. The GPU is also used for NV12->RGB24 conversion for display of the frames in the GUI. That does not occur for frame serving via your script.
And basically a CUDA card is needed just so your program will function. Is that correct? You really don't like to read existing materials and documentation, do you? The first paragraph of the page where you donated is too complex for you to understand?
Just wondering though, why does my MPEG2 video encode to h264 a couple of FPS slower than when using DGMPGDec? The GPU cannot be MT'ed. There's only one of them. I assume all other factors are equal. Generally, you will not experience a speedup for MPEG2 if you have a fast processor and/or are processing SD video. In any case, speedup of transcoding is not the raison d'etre of DGDecNV, though in some scenarios a speedup can be realized. And of course MT'ing DGMPGDec will have a significant impact.
From what I understand CPU=6 has the same stength of deblocking as CPU=4 but it adds deringing? Is that correct? You said you don't like CPU=6 as there are better filters to use. Could you please recommend the best one in your opinion? No I said I don't use postprocessing at all! I was told all this by other guys, there's a thread about it at my forum, and it links another thread about it here. Maybe you can find them if you look. Do a search for "deblocking" at my forum. It's on my to-do list to add support for postprocessing. You can find lots of threads about such filters here. Sorry, I have no recommendations for you. As I mentioned, DGDecNV is targeted at BluRays, not torrent downloads. :)
VideoFanatic
22nd August 2012, 23:01
I said this: "And basically a CUDA card is needed just so your program will function. Is that correct?"
You really don't like to read existing materials and documentation, do you? The first paragraph of the page where you donated is too complex for you to understand?
Your donate page says this:
"DGDecNV is a decoder/frameserver for AVC, MPEG2, and VC1 streams that runs on the GPU of Nvidia graphics cards that support CUDA video decoding. That means the card must have a VP2 or greater engine. VP1 is not supported!"
I'm sorry but to me that says that a CUDA card is required for your program to function.
Groucho2004
22nd August 2012, 23:24
I'm sorry but to me that says that a CUDA card is required for your program to function.
Let's just assume that English is not your native language and that you're misunderstanding.
The first paragraph on the product page is very clear about what the program does and what's required to run it.
In short - Yes, you need a Nvidia graphics card that supports CUDA video decoding with at least a VP2 engine.
Guest
23rd August 2012, 00:36
I feel like Alice in Wonderland. Words don't mean what they mean!?
LigH
23rd August 2012, 07:15
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
24th August 2012, 00:03
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
11th September 2012, 21:28
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 :p
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
11th September 2012, 22:06
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
15th September 2012, 17:17
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
16th September 2012, 00:36
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
16th September 2012, 21:59
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
16th September 2012, 23:41
Only the last Verde driver will work on those notebook adapters in my experience.
alzamer2
17th September 2012, 11:56
Only the last Verde driver will work on those notebook adapters in my experience.
what do you mean by "the last Verde driver"
Guest
17th September 2012, 13:27
http://www.geforce.com/drivers/results/26388
alzamer2
17th September 2012, 20:50
http://www.geforce.com/drivers/results/26388
will this work ??
http://www.geforce.com/drivers/results/47420
Guest
17th September 2012, 22:45
I don't know offhand. You can always try it and revert back if needed. If it works please let me know. Thanks!
Guest
22nd September 2012, 01:42
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-jacob-Blu-ray/dp/B001GMY9NK/ref=sr_1_2?ie=UTF8&s=dvd&qid=1283945127&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
24th September 2012, 13:08
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
24th September 2012, 13:15
Here you go:
http://forum.doom9.org/showthread.php?t=165970
Guest
24th September 2012, 13:41
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
24th September 2012, 18:24
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
24th September 2012, 18:29
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
24th September 2012, 18:36
Yup, I've reproduced it. I'll correct it for 2043. Thank you for pointing it out.
RedDwarf1
25th September 2012, 00:15
Thank you neuron2, another bug squashed. :)
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.