DG NV tools - Page 90

Guest · 27th June 2010, 01:15

I don't want to discuss it in a public forum.

meatwad · 27th June 2010, 05:38

Has anyone recently compared the speed of DG NV tools against CoreAVC (2.0.0) using an ATI video card? I'm not sure what's going on, but when encoding a 720p mkv down to 624x352 in iPod format DGNVIndex lost by about 40 fps on average. I even tried Core with CUDA enabled as the decoder and it was about 10 fps slower than DGNVIndex. I've been using DG NV tools since 2008 and this is just bizarre? I didn't uninstall Catalyst Control Center or the ATI drivers and that might be where the issue is (even though I disabled CCC from loading on startup). I'm using 2015 with Windows 7 x64 and a 1090t x6 processor (890gx chipset integrated Radeon 4290HD and 8GB of ram). The Nvidia pcie card I used was geforce 210.

I really don't think leaving the ATI drivers installed is the issue because DG NV tools ran just fine. I guess I should have ran the same encode using CoreAVC without CUDA acceleration being on when I had the geforce 210 installed. Guess I'll experiment a little more tomorrow.

meatwad · 27th June 2010, 06:21

I decided to go all the way and completely uninstall ati catalyst and the ati drivers. The results were pretty much the same. Using the geforce 210 the winner was CoreAVC without CUDA acceleration on, but only by about 3-7 fps over DGNVIndex. The worst performer was CoreAVC with CUDA acceleration on. It was about 20 fps slower than with it off. I guess I need to try another Nvidia graphics card, but I was under the assumption that only the amount of memory on the card would have any real impact when it came to CUDA. Anyway, CoreAVC seems to work better with ATI (or so it would seem). Hopefully someone more qualified will be able to sort this out. I really like DG NV tools so please don't take this the wrong way, plus speed isn't the only reason for using them.

lych_necross · 27th June 2010, 06:56

Well Neuron, I guess you could always go with a hardware key

tormento · 27th June 2010, 08:18

Has the dgi structure changed again?

Guest · 27th June 2010, 13:33

Quote:

Originally Posted by tormento

Has the dgi structure changed again?

Changes in the DGI structure are indicated by the version number at the top of the file.

Guest · 27th June 2010, 14:15

My latest anti-cracking strategy: a new release every day.

* Fixed a bug in VC1 pulldown detection. For example, streams on the bluray "Life" were being erroneously marked with frame pulldown in the DGI file, causing extra frames when serving.

* Bumped the DGI version number to 8 to complete the removal of the ill-advised protection. (Yes, tormento, I know you hate me.)

http://neuron2.net/dgdecnv/dgdecnv.html

tormento · 27th June 2010, 17:03

Quote:

Originally Posted by neuron2

(Yes, tormento, I know you hate me.)

But I love your work

meatwad · 28th June 2010, 04:31

Neuron2, is there a major difference in DG NV Tools performance with different Nvidia GPUs? I remember reading somewhere that the low end cards should perform as well as the high end cards and that the amount and type of memory were the only real game changers.

Guest · 28th June 2010, 14:18

Quote:

Originally Posted by meatwad

Neuron2, is there a major difference in DG NV Tools performance with different Nvidia GPUs? I remember reading somewhere that the low end cards should perform as well as the high end cards and that the amount and type of memory were the only real game changers.

The key factors are memory bandwidth and VP core clock rate.

Regarding your performance observation, I can address that only with full details on your machine, your script, and your encoder setup (x264 command line if applicable). A 40 fps deficit *for transcoding* sounds fishy to me but I'm willing to conduct some experiments if you give me the information I need to try to reproduce your scenario.

Generally, for simple decoding only a fast CPU will beat the GPU. For transcoding, however, offloading decoding to the GPU can modestly improve performance as long as the decoding does not become the bottleneck. For example, if you decode HD and encode SD then the GPU decoder may struggle to keep up with the encoder. On the other hand, if your script is complex and you can offload it to the GPU (deinterlacing and resizing), then the balance swings the other way. So it is a complex situation. And of course performance is not the only factor to be considered, as I have described many times.

cweb · 28th June 2010, 18:55

Right now I am using version 2013 (will update soon but I wanted to ask this first)..

You had said back in January 2010 that "The options in DGIndexNV are just there to allow you to see the effect of the deinterlacing."

So if I set Enable PureVideo Deinterlacer | Single rate etc in dgindexnv, I HAVE to use the corresponding deinterlace parameter in dgmultisource() ?
If I do not use the parameter, does it use the setting in dgindexnv or does it just not deinterlace at all?

I'm asking as I created 2 dgi files with dgindexnv (of the same dvd), with the deinterlace on and off respectively, and the files are identical.

jpsdr · 28th June 2010, 19:06

I've jumped from 2014 to 2016, now each time i try to open an .m2ts file, i've the error message : GPU Decoder : Fail to create video decoder (1). Tested on several files, always same error message.
Replaced file with 2013 version (haven't keep 2014) : Everything work fine again.

rack04 · 28th June 2010, 19:08

Quote:

Originally Posted by jpsdr

I've jumped from 2014 to 2016, now each time i try to open an .m2ts file, i've the error message : GPU Decoder : Fail to create video decoder (1). Tested on several files, always same error message.
Replaced file with 2013 version (haven't keep 2014) : Everything work fine again.

Have you updated your license file?

n0an · 28th June 2010, 19:13

I want to index a VC1 file, but DGIndexNV pops the following error: "The procedure entry point cuCtxDestroy could not be located in the dynamic link library nvcuda.dll. I have the nvcuda and nvcuvid dlls in my system32 dir. Same error for CUVIDserver.exe as well. I have sloved this problem for DGAVCInde, but I am unable to recall the solution. Any help with be greatly appreciated

.

Guest · 28th June 2010, 19:25

Quote:

Originally Posted by cweb

So if I set Enable PureVideo Deinterlacer | Single rate etc in dgindexnv, I HAVE to use the corresponding deinterlace parameter in dgmultisource() ?
If I do not use the parameter, does it use the setting in dgindexnv or does it just not deinterlace at all?

If you do not enable it with the source filter, then it is not enabled.

Quote:

I'm asking as I created 2 dgi files with dgindexnv (of the same dvd), with the deinterlace on and off respectively, and the files are identical.

That is correct. There is no connection between what you do in the indexer and what you do in your source filters.

Guest · 28th June 2010, 19:26

Quote:

Originally Posted by jpsdr

I've jumped from 2014 to 2016, now each time i try to open an .m2ts file, i've the error message : GPU Decoder : Fail to create video decoder (1). Tested on several files, always same error message.
Replaced file with 2013 version (haven't keep 2014) : Everything work fine again.

Regenerate your license.

Guest · 28th June 2010, 19:27

Quote:

Originally Posted by n0an

I want to index a VC1 file, but DGIndexNV pops the following error: "The procedure entry point cuCtxDestroy could not be located in the dynamic link library nvcuda.dll. I have the nvcuda and nvcuvid dlls in my system32 dir. Same error for CUVIDserver.exe as well. I have sloved this problem for DGAVCInde, but I am unable to recall the solution. Any help with be greatly appreciated

.

Remove the DLLs from the DGDecNV directories. Install the latest Nvidia drivers. That is all.

cweb · 28th June 2010, 19:39

Quote:

Originally Posted by neuron2

If you do not enable it with the source filter, then it is not enabled.

That is correct. There is no connection between what you do in the indexer and what you do in your source filters.

Thanks....

stax76 · 28th June 2010, 22:11

I have a sample causing a problem when loading from command line, it loads using -i without -o but with -i and -o together it fails to load, somehow weird, I hope you can reproduce it, another sample I just tried did not cause any problem.

http://www.filedropper.com/mp4aaclc

tormento · 28th June 2010, 23:23

Quote:

Originally Posted by neuron2

* Here's a cookie to make up for the first item above. Added audio language detection for opened MPLS files. After opening the MPLS file, Audio/Audio Demux will tell you the languages of the (nonhidden) streams.

Not fully working here.

With the retail italian Cars BD, on movie playlist (00072.mpls, 0…2 angles), the audio demux recognizes only 1100…1105 languages. The following 1106…110b, which are not hidden, are not recognized.

BDInfo fully recognizes the audio streams.

Please tell me which parts you need to debug the error.

27th June 2010, 08:18	#1785 \| Link
tormento Acid fr0g Join Date: May 2002 Location: Italy Posts: 3,075	Has the dgi structure changed again? __________________ @turment on Telegram

27th June 2010, 14:15	#1787 \| Link
Guest Guest Join Date: Jan 2002 Posts: 21,901	Build 2016 My latest anti-cracking strategy: a new release every day. * Fixed a bug in VC1 pulldown detection. For example, streams on the bluray "Life" were being erroneously marked with frame pulldown in the DGI file, causing extra frames when serving. * Bumped the DGI version number to 8 to complete the removal of the ill-advised protection. (Yes, tormento, I know you hate me.) http://neuron2.net/dgdecnv/dgdecnv.html

28th June 2010, 18:55	#1791 \| Link
cweb Registered User Join Date: Oct 2002 Location: The Pandorica Posts: 528	Right now I am using version 2013 (will update soon but I wanted to ask this first).. You had said back in January 2010 that "The options in DGIndexNV are just there to allow you to see the effect of the deinterlacing." So if I set Enable PureVideo Deinterlacer \| Single rate etc in dgindexnv, I HAVE to use the corresponding deinterlace parameter in dgmultisource() ? If I do not use the parameter, does it use the setting in dgindexnv or does it just not deinterlace at all? I'm asking as I created 2 dgi files with dgindexnv (of the same dvd), with the deinterlace on and off respectively, and the files are identical. __________________ PC specs for bug reports: Intel Core i7-4790K @4Ghz Win10(Linux VM) PCI express NVIDIA RTX 2060 SUPER graphics card http://twitter.com/cwebdesign

28th June 2010, 22:11	#1799 \| Link
stax76 Registered User Join Date: Jun 2002 Location: On thin ice Posts: 6,857	I have a sample causing a problem when loading from command line, it loads using -i without -o but with -i and -o together it fails to load, somehow weird, I hope you can reproduce it, another sample I just tried did not cause any problem. http://www.filedropper.com/mp4aaclc __________________ https://github.com/stax76/software-list https://www.youtube.com/@stax76/playlists

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

27th June 2010, 01:15	#1781 \| Link
Guest Guest Join Date: Jan 2002 Posts: 21,901	I don't want to discuss it in a public forum.

27th June 2010, 05:38	#1782 \| Link
meatwad Registered User Join Date: Jun 2007 Posts: 106	Has anyone recently compared the speed of DG NV tools against CoreAVC (2.0.0) using an ATI video card? I'm not sure what's going on, but when encoding a 720p mkv down to 624x352 in iPod format DGNVIndex lost by about 40 fps on average. I even tried Core with CUDA enabled as the decoder and it was about 10 fps slower than DGNVIndex. I've been using DG NV tools since 2008 and this is just bizarre? I didn't uninstall Catalyst Control Center or the ATI drivers and that might be where the issue is (even though I disabled CCC from loading on startup). I'm using 2015 with Windows 7 x64 and a 1090t x6 processor (890gx chipset integrated Radeon 4290HD and 8GB of ram). The Nvidia pcie card I used was geforce 210. I really don't think leaving the ATI drivers installed is the issue because DG NV tools ran just fine. I guess I should have ran the same encode using CoreAVC without CUDA acceleration being on when I had the geforce 210 installed. Guess I'll experiment a little more tomorrow.

27th June 2010, 06:21	#1783 \| Link
meatwad Registered User Join Date: Jun 2007 Posts: 106	I decided to go all the way and completely uninstall ati catalyst and the ati drivers. The results were pretty much the same. Using the geforce 210 the winner was CoreAVC without CUDA acceleration on, but only by about 3-7 fps over DGNVIndex. The worst performer was CoreAVC with CUDA acceleration on. It was about 20 fps slower than with it off. I guess I need to try another Nvidia graphics card, but I was under the assumption that only the amount of memory on the card would have any real impact when it came to CUDA. Anyway, CoreAVC seems to work better with ATI (or so it would seem). Hopefully someone more qualified will be able to sort this out. I really like DG NV tools so please don't take this the wrong way, plus speed isn't the only reason for using them.

27th June 2010, 06:56	#1784 \| Link
lych_necross ZZZzzzz... Join Date: Jan 2007 Location: USA Posts: 303	Well Neuron, I guess you could always go with a hardware key

28th June 2010, 04:31	#1789 \| Link
meatwad Registered User Join Date: Jun 2007 Posts: 106	Neuron2, is there a major difference in DG NV Tools performance with different Nvidia GPUs? I remember reading somewhere that the low end cards should perform as well as the high end cards and that the amount and type of memory were the only real game changers.

28th June 2010, 19:06	#1792 \| Link
jpsdr Registered User Join Date: Oct 2002 Location: France Posts: 2,637	I've jumped from 2014 to 2016, now each time i try to open an .m2ts file, i've the error message : GPU Decoder : Fail to create video decoder (1). Tested on several files, always same error message. Replaced file with 2013 version (haven't keep 2014) : Everything work fine again.

28th June 2010, 19:13	#1794 \| Link
n0an Britain's Finest! Join Date: Jun 2009 Posts: 143	I want to index a VC1 file, but DGIndexNV pops the following error: "The procedure entry point cuCtxDestroy could not be located in the dynamic link library nvcuda.dll. I have the nvcuda and nvcuvid dlls in my system32 dir. Same error for CUVIDserver.exe as well. I have sloved this problem for DGAVCInde, but I am unable to recall the solution. Any help with be greatly appreciated .