DGAVCDecNV 1.0.13: GPU decoding on Nvidia [Archive] - Page 20

xopowo

1st February 2009, 18:20

The serial number that was generated for me when I bought the license works ... on WinXP. Now that I'm using Win7 (xp is jacked up), the same serial won't work. How does one generate a new number? Or is it just a matter of asking? I'm using the same computer, so don't know why anything would be different, but who knows.

Esurnir

1st February 2009, 21:35

madshi

2nd February 2009, 08:54

@neuron2, I've just added MKV demuxing to eac3to, too. You may want to peek into the eac3to thread once in a while cause users are posting funny MKV samples there to keep me busy. Just in case you're interested in collecting more strange samples... :)

Guest

5th February 2009, 03:14

* Added support for Matroska (MKV) input streams.

http://neuron2.net/dgavcdecnv/dgavcdecnv.html

~bT~

5th February 2009, 19:35

^ thanks Don.

rica

5th February 2009, 22:36

Thanks neuron :)

meatwad

6th February 2009, 13:48

Has anyone been able to use the GPU deinterlacer with StaxRip? The problem is that I can't alter the avs file to add the line to AVCSource. Even if I try to manually edit the avs file StaxRip still won't process it. I'll ask in the StaxRip Forum as well if no one here has been successful.

Could there possibly be an alternate form of syntax I could use to get the Nvidia Deinterlacer to work? I can easily add it in the line below it like any other function, just not on the AVCSource line:

AVCSource("%source_file%")
deinterlace=true

Naturally that doesn't deinterlace, but it crashes if I try to alter it to this:

AVCSource("project.dga", deinterlace=true)

ultratoto14

6th February 2009, 14:37

it's deinterlace=1

AVCSource("project.dga", deinterlace=1)

http://neuron2.net/dgavcdecnv/DGAVCDecodeNVManual.html

meatwad

6th February 2009, 15:31

I saw that when I was going over the manual, but it totally slipped my mind. Thanks--I hope it works.

ultratoto14

6th February 2009, 18:08

@neuron

http://neuron2.net/dgavcdecnv/DGAVCDecodeNVManual.html

In the samples, there is

AVCSource("project.dga", deinterlace=true)

instead of

AVCSource("project.dga", deinterlace=1)

Guest

6th February 2009, 18:22

Fixed. Thank you for pointing it out. :thanks:

Guest

7th February 2009, 03:03

I've updated the CUVID server and client to support MPEG1 and MPEG2 video.

http://neuron2.net/dgavcdecnv/dgavcdecnv.html

You can probably guess what's coming next.

After that my plan is to combine all three variants into one. Then I will add "output trimmed TS" as well as multiple ranges.

woah!

7th February 2009, 06:47

Guest

7th February 2009, 07:02

I added the EXE so please re-download it.

rica

7th February 2009, 19:05

I've updated the CUVID server and client to support MPEG1 and MPEG2 video.
****
You can probably guess what's coming next.
***
Then I will add "output trimmed TS" as well as multiple ranges.

Congrats :)

Sagekilla

7th February 2009, 23:25

Thanks for all your work neuron2! Looking forward to become a supporter as soon as I get out of my poor-college-student situation ;)

laserfan

8th February 2009, 16:44

I've updated the CUVID server and client to support MPEG1 and MPEG2 video... You can probably guess what's coming next.

After that my plan is to combine all three variants into one.I'm surprised there hasn't been more reaction to this! Although I have (finally) learned when-and-how to invoke DGIndex.exe and DGAVCIndexNV.exe and DGVC1IndexNV.exe and CUVIDServer.exe and which .d2v or .dgv or .dga goes-with-which it will be great if any UI streamlining can be done, so THANKS DG IN ADVANCE! Sign me up for any alphas-or-betas! :)

xopowo

9th February 2009, 04:48

Guest

9th February 2009, 05:40

Is there a memory leak in CUVIDServer 1.0.4? I'm using Win 7 64-bit and encoding with x264.exe and the memory used by the server has grown from 262mb to now 690mb in 19 minutes. I only have 4gb of memory. Is 64gb recommended :)

avs is just "1.dga", deinterlace=1)

not doing anything fancy ... decimating after that, no cropping or resize

I was looking at x264.exe memory usage ... cuvidserver passed it ... now, 22 minutes into the encode, it's at 867mb! Funny you should ask. I just reported that to Nvidia today. I'll keep you informed.

Can I have your full script please?

I thought it only happens with random access. Decimation could force that.

Guest

10th February 2009, 03:34

The memory leak has been fixed. All NV tools have been updated with the fixed nvcuvid.dll, so redownload any of them to get the fixed DLL.

@xopowo

Please advise if this fixes your issue.

Deinorius

11th February 2009, 21:12

@neuron2
The Core Team just updated CoreAVC to 1.9.0.0 (http://www.coreavc.com/index.php?option=com_content&task=view&id=27&Itemid=1) with CUDA-Support. Would be interesting, if it's more efficient than VP2-Part.
I never read it but is it possible for DGAVCIndexNV to index LV 5.0/5.1 Streams?

Rectal Prolapse

11th February 2009, 22:01

I am pretty sure CoreAVC CUDA still requires a videocard with VP2 support. Someone I know has a G80 NVIDIA card (8800GTS 640) and CUDA is not selectable in CoreAVC 1.9 - so that would support that theory.

~bT~

11th February 2009, 22:04

^ i believe u are correct.. vp2 or higher is needed for cuda.

Deinorius

11th February 2009, 22:09

Damn, I hoped it could be more. So it's not really reasonable. The only sense it does for me to decode non-DXVA compatible Streams, but that's it. At least other DXVA Video decoder can use ATI UVD too.

Guest

12th February 2009, 00:49

I never read it but is it possible for DGAVCIndexNV to index LV 5.0/5.1 Streams? Yes, no problem.

Audionut

12th February 2009, 01:37

From the CoreAVC thread.

I think it would be better if DGAVCIndexNV didn't rely on nvcuvid.dll being in system32; the program location is stored in the .dga file so why can't DGAVCDecodeNV load nvcuvid.dll from there?

I do not have a copy of nvcuvid.dll anywhere on my comp other than dg***decodenv folders.
The closet I have is nvcuda.dll

edit: and everything works fine that way too.

Guest

12th February 2009, 03:42

Both DGXXXIndexNV.exe and CUVIDServer.exe must be able to find nvcuvid.dll. DGXXXDecodeNV.dll does not need it and so is irrelevant. Thus, the two EXEs must see the DLL via the Windows DLL search path:

http://msdn.microsoft.com/en-us/library/7d83bc18(VS.80).aspx

If you have those two EXE's in the same directory with nvcuvid.dll, everything will be fine.

It is reasonable to have the CUVID Server in its own directory, as well as to have the DG tool variants in their own directories. That is why I recommended to put nvcuvid.dll in system32, so that multiple copies of it are not required.

I will give some thought to a solution that doesn't require multiple copies and doesn't overwrite the version installed by the Nvidia driver install. Ideas are welcome.

~bT~

12th February 2009, 10:38

i installed this driver: 181.20_geforce_winvista_32bit_international_whql

when i moved nvcuvid.dll to system32, it never overwrote anything.. :confused:

squid_80

12th February 2009, 10:57

i installed this driver: 181.20_geforce_winvista_32bit_international_whql

when i moved nvcuvid.dll to system32, it never overwrote anything.. :confused:
All nvidia driver versions after 181.20 should include nvcuvid.dll.

~bT~

12th February 2009, 11:18

^ i'm a 100% sure it didn't coz i was waiting for the overwrite confirmation to pop up.

or is it card dependant? i have 8600gs.

squid_80

12th February 2009, 11:49

^ i'm a 100% sure it didn't coz i was waiting for the overwrite confirmation to pop up.

or is it card dependant? i have 8600gs.

All nvidia driver versions AFTER 181.20 should include nvcuvid.dll.

.....

~bT~

12th February 2009, 11:56

^ lol, gotcha. so we are both correct :p

Audionut

12th February 2009, 14:08

All nvidia driver versions after 181.20 should include nvcuvid.dll.

They don't. I've installed 181.21, 181.22 and an old 185.xx beta.

None have included it.

I will give some thought to a solution that doesn't require multiple copies and doesn't overwrite the version installed by the Nvidia driver install. Ideas are welcome.

My l33t programing skills are showing here.
Can you include the dll into the exe's?

Aren't you combing all 3 decodeNV's into the same exe? Then you would only have the 1 exe and 1 dll.

Can you run a check on the version of the dll in system32 folder and overwrite with your copy if newer?

Create installers. Overwrite dll in install folder if its older than the new decodenv being installed.

I really don't see the problem though. Download zip, Extract, run exe.

.

menlvd

12th February 2009, 14:21

what can be wrong
last dgavcdecnv
sys win7 x64
drv 181.22
using 2 pass encoding
1 pass processed fine, but 2 even start (w/o manual close and starting again CUVIDServer.exe)
in sys wxp-sp3 32 everything is fine

Guest

12th February 2009, 14:40

What encoder and encoding GUI do you use?

menlvd

12th February 2009, 14:57

What encoder and encoding GUI do you use?

latest x264 1109 x64
not using gui
simple run from scrip or run from cmd
sample "D:\minep\me_gui\tools\x264\avs2yuv.exe" -raw "D:\temp\bd-taken\taken.dga.avs" - | "D:\minep\me_gui\tools\x264\x264.1109.kMod.core2.x64.exe" --pass 1 --bitrate 11000 --vbv-maxrate 40000 --vbv-bufsize 62500 --keyint 240 --min-keyint 1 --ref 5 --bframes 3 --deblock -3,-3 --partitions all --8x8dct --me umh --trellis 2 --subme 9 --weightb --mixed-refs --no-fast-pskip --threads 6 --no-psnr --no-ssim --level 4.1 --progress --aq-mode 1 --aq-strength 1.7 --psy-rd 1.1:0.1 --b-adapt 2 --output "d:\123.mkv" --sar 1:1 --direct auto --no-dct-decimate --b-pyramid --qpmax 35 --qcomp 1 --qpmin 5 --ratetol 3 --merange 24 --pbratio 1.2 --ipratio 1.3 --stats "d:\stats.stats" - 1920x816
and then try to start second pass but no progress w/o restart cuvidsrv
will try install latest forceware 182.05, but i'll don't think thats solve problem

Guest

13th February 2009, 02:36

1. When serving video, replace copies of leading orphaned B frames with copies of the first decodable frame.

2. Fixed blocking on seeks with deinterlace=1.

3. Fixed false sync lock for M2TS files.

4. Fixed problem where stepping by GOP backward could wrap from the start of the file to the end of the file.

5. Closing the window while a play/preview is running caused a CUVID popup error. Fixed.

6. Enable "Disable Display" option only after a file is loaded. This prevents a crash scenario.

7. Fixed nvcuvid.dll memory leak.

8. Update CUVID Server to version 1.0.4.

http://neuron2.net/dgavcdecnv/dgavcdecnv.html

Guest

13th February 2009, 02:40

@menlvd

I don't have win7 x64 so I'm not sure how to help you.

What happens without the avs2yuv.exe silliness? In other words, just open the script directly with x264.

squid_80

13th February 2009, 03:15

They don't. I've installed 181.21, 181.22 and an old 185.xx beta.

None have included it.
Hmm seems I missed noticing 181.22 had jumped from beta to offical. So any official drivers after 181.22 should include nvcuvid.dll.
I don't know where you've got the 185.xx beta from, sounds wrong to me since the beta driver released earlier this week is 182.05.

menlvd

13th February 2009, 06:06

@menlvd

I don't have win7 x64 so I'm not sure how to help you.

What happens without the avs2yuv.exe silliness? In other words, just open the script directly with x264.
w/o avs2yuv.exe run only x86 x264.exe - but no problem
seems to be a avsyuv produce bug that can cause broblem with cuvidsvr

xopowo

13th February 2009, 08:21

Unfortunately, I just replaced everything with the new version(s) and the memory leak is still incredibly bad :(

Here is the AVS script I'm using ...

LoadPlugin("C:\encode\Dlls\DGAVCDecodeNV.dll")
AVCSource("1.dga")
selecteven()

That's it. Nothing more when doing a 720p source to bring it back to 29.97fps from 59.97

OS - Windows 7 (64-bit) Build 7000
CPU - Intel Xeon x3360
Memory - 4GB DDR2 800
Video - nVidia GeForce 9600 GSO (768mb)
Avisynth - 2.57
VirtualDubMod 1.5.10.2 (virtualdub doesn't work for me)

7 minutes into the encode, and CUVIDServer.exe went from 23772k (at launch) to 644040k.

Longer encodes, the server crashes (when it eats about 1.7gb of memory). There is a dialogue box that pops up that just says "server" and an 'OK' button (nothing legible).

I don't know what to tell you other than even with the new version, it still leaks badly.

nvcuvid.dll has to be located in \Windows\System\ in order for it to work for me (as opposed to \system32\)

Let me know if you need more information.

I just tested the same exact avs file with VirtualDub version 1.8.8 (32-bit version) and the same exact results. CUVIDServer.exe crashed on that one 18:47 into the encode with memory at 1,688,596K ... yikes!

meatwad

13th February 2009, 10:36

xopowo, I believe it's a Windows 7 problem. I experienced the same thing with the 32 bit version. The same jobs in XP went through without a hitch.

Guest

13th February 2009, 14:27

xopowo, I believe it's a Windows 7 problem. Me too. I'll mention it to Nvidia to see what they think.

laserfan

13th February 2009, 17:00

I just had an unexpected result in an encoding: I had used eac3to to make an .mkv file, indexed it with v1.0.11 and re-encoded with x264, and my encode is "off" by 3 frames from the original, messing-up the I-frames I'd specified and thus my chapter marks. Puzzling over this I noticed my XP Pro x64 setup has your updated nvcuvid.dll in my SysWOW64 directory, but an older version from 16-Dec-08 in my system32 folder. Brand-new to 64-bit OS, I'd read that (counterintuitively) 32-bit dlls were to go into SysWOW64 and 64-bit into system32 (so the older nvcuvid.dll must likely be from my Nvidia 9600display card driver installation).

Should I have placed the 08-Feb-09 (new) nvcuvid.dll into system32 instead, replacing the one that's there? Trying to sort this before I re-run my encoding (8 hours) with the newer 1.0.12... :o

UPDATE: Well I put DG's nvcuvid.dll into system32 and rebooted and it didn't crash. Realized also that I run CUVID Server from its own directory so tried using procexp to ID which dll it was using. Can't tell--neither the Dec version nor DG's identifies itself in any way that I can tell. Guess if no one has advice for me I'll try 1.0.12 and do it again (hell I dunno if this has anything to do with frames being "off" anyway)...

UPDATE2: And in fact it doesn't seem to be the problem--I still am "off" by 3 frames. Going to start-over from scratch, extracting as .h264 not .mkv.

Still, would appreciate if someone knows if replacing nvcuvid.dll everywhere (sysWOW64, system32, every tool location) is the right thing to have done. That's where I'm at now.

Guest

14th February 2009, 01:00

Everybody please re-download 1.0.12. It had a bad bug in DGAVCDecodeNV.dll.

Guest

14th February 2009, 01:27

@laserfan

Put my nvcuvid.dll into the same directory as DGAVCIndexNV.exe. Also, put it in the same directory as CUVIDserver.exe, if that differs from the former. Then you won't have to put it in a system directory.

Regarding your three-frame discrepancy, redownload 1.0.12 and try with that. If it still occurs tell me how to duplicate it, providing a stream if necessary.

laserfan

14th February 2009, 02:08

Put my nvcuvid.dll into the same directory as DGAVCIndexNV.exe. Also, put it in the same directory as CUVIDserver.exe, if that differs from the former. Then you won't have to put it in a system directory.Thanks--I suspected maybe the .exes would take the "path of least resistance" to find the .dll but wasn't sure.

Re: 3 frames off, I have a couple other things to try (along w/your fixed version) and appreciate your offer of help!

jj666

14th February 2009, 08:31

They don't. I've installed 181.21, 181.22 and an old 185.xx beta.

None have included it.

The 185.20 driver was alpha quality and not officially released, there's a comment from a mod here that says it is not recommended for use by Nvidia due to broken functionality:

http://www.nvnews.net/vbulletin/showpost.php?p=1890381&postcount=28

Cheers,

-jj-