DG NV tools [Archive] - Page 45

cweb

25th July 2010, 22:11

Same errors. GT 220 1GB, 257.21 Windows 7 x64. Also, to clarify, this is not an issue of trying to open an older .dgi file. These errors occur when I try to run DGIndexNV to create a new .dgi.

Same errors. GTX 285, 196.21 driver. Win7 x32.

Guest

25th July 2010, 22:12

Please see my last post. Thank you.

cweb

25th July 2010, 22:15

I've updated the 32-bit executable to add additional error reporting. I need someone for which it failed to re-download 2022 and try again with this and post the error popups that occur. Thank you.

Ok. Now it gave me this error as soon as dgindexnv was loaded.

http://a.imageshack.us/img709/8479/delme1.jpg

kebulek

25th July 2010, 22:16

Ok. Now it gave me this error as soon as dgindexnv was loaded.

http://a.imageshack.us/img709/8479/delme1.jpg
Same here.

Guest

25th July 2010, 22:17

Oops, I know what's wrong. Thanks for your test result.

Stand by for fixed version...

cweb

25th July 2010, 22:18

Oops, I know what's wrong. Thanks for your test result.

Stand by for fixed version...

thanks :)

Guest

25th July 2010, 22:24

Re-download 2022 and get the cubin file into the same directory as DGIndexNV.exe.

Report your success. :)

cweb

25th July 2010, 22:29

Re-download 2022 and get the cubin file into the same directory as DGIndexNV.exe.

Report your success. :)

I redownloaded it but the result was the same. I didn't find a cubin file. Could the file have been cached somehow? I cleared my cache and redownloaded just to be sure.

kebulek

25th July 2010, 22:29

Re-download 2022 and get the cubin file into the same directory as DGIndexNV.exe.

Report your success. :)
I don't see any "cubin file" in current 2022 zip archive. :confused:

Guest

25th July 2010, 22:35

Oops.

Try again.

Thank you for your patience. :)

kebulek

25th July 2010, 22:38

Re-download 2022 and get the cubin file into the same directory as DGIndexNV.exe.

Report your success. :)
Now it works for me. Looks like you did it after all... ;)

Guest

25th July 2010, 22:43

I was hurrying to get you guys squared away and accidentally re-uploaded version 2002. :eek:

Also, I kinda forgot that the cubin executables are dynamically loaded, and that kinda means you need to have the binaries. :stupid:

Groucho2004

25th July 2010, 23:20

Still getting this:

http://www.iol.ie/~schubert/Image1.png

Guest

26th July 2010, 00:02

Your path refers to build 2021. What's up with that?

Verify that the correct cubin file (32 or 64 bit) is in the same directory as version 2022 DGIndexNV.

Groucho2004

26th July 2010, 00:15

Don't mind the path, I just didn't create a new directory.

I just tried again in a new directory with just the license file carried over from 2021. Same error message.

Edit: I'll try with XP now.

Edit1: Same thing on XP SP3.

Guest

26th July 2010, 00:40

State your Nvidia card type, memory size, and driver version.

Groucho2004

26th July 2010, 00:44

State your Nvidia card type, memory size, and driver version.

Asus GT 240 GDDR5, 512 MB, driver is 191.07.

Guest

26th July 2010, 00:47

SubJunk

26th July 2010, 05:00

Hi, I just registered 2 days ago and wanted to say thanks, it's really great. I was using 2021 and it worked perfectly, and 2022 works too.
It seems to be faster than before as well, though I haven't run tests.

MrVideo

26th July 2010, 05:38

Self reminder to delete old dll's from plugin dir when Don renames.

Good point. Otherwise people's scripts will continue to use the old DLL and not know it.

MrVideo

26th July 2010, 05:46

Everything is renamed now for 2021 and DGMultiSource is retained as a synonym for DGSource.

Damn, didn't know you did that already. There is nothing in the 2021 Readme file about the renaming. Even though I installed the latest version, I didn't notice the change. I just grabbed the files and copied them to the installed location. I'm just now getting around to catching up with the forum.

Suggest that the renaming info be placed in a future Readme file for those who are upgrading from a version earlier than 2021.

MrVideo

26th July 2010, 06:03

I don't have a CRLF in my license file and it works...

I don't either. The license files (two of them) are edited on my Solaris 10 X86 server. EOL for unix is LF only. No issues

MrVideo

26th July 2010, 06:20

Remove the -y 1. That option no longer exists.

Time for a WAG. If the -e and -h were placed in front of the -y, I'm guessing the -e and -h would have been honored and the use of the old option would never have been detected. The reason is that when the -y option was parsed, all further parsing of the command line stopped.

Normally (I'm speaking Unix world programming), when an illegal, or unknown, option is entered, the program bails with an error indicating that option such-and-such doesn't exist.

In this case, couldn't a GUI be poped up with the error message about the bad option, or spit it out to stderr? That would be a little more user friendly. It is easy to hit the wrong character and not know it. If that creates an error, let the user know.

MrVideo

26th July 2010, 06:25

I will include a full history in the ZIP from now on.

Thanks, that is helpful.

MrVideo

26th July 2010, 06:35

I was in the process of sending the license file to Donald so he could tell me what I was doing wrong when I noticed I had named the file license.txt intead of a text file named license. DUH. Works great now....I feel so dumb.

But license,txt is the correct filename. As mentioned in a previous post, you probably have extension display turned off and you ended up naming your file license.txt.txt. You can thank Windblows for knowing exactly what you want and doing it for you.

lych_necross

26th July 2010, 07:13

cweb

26th July 2010, 07:47

thanks, 2022 works for me now..

MrVideo

26th July 2010, 09:00

After reading these posts and updating to the reposted 2022, I get this error:

Does that file exist in the path shown in the error?

Why are you running the 32 bit version on a 64 bit system?

Groucho2004

26th July 2010, 09:18

Version 191.07 is very old and this error is known to occur with older driver versions. Please upgrade drivers to latest version and report results. FYI, I am running 257.21.

http://www.nvidia.com/object/winxp-258.96-whql-driver.html

I tried the latest drivers (258.96) and DGIndexNV works with those. However, I'm getting all sorts of weird behaviour (for example, Aniti-aliasing doesn't work with older games) and even blue screens with these drivers. When I got the new card I tried a number of drivers (19x and 25x) and I settled on 191.07 because it worked best for me.
I think I'll stick with DGIndexNV 2021 for the time being until the NVidia drivers work for me.

Edit: I'll try 257.21.

lych_necross

26th July 2010, 10:02

Does that file exist in the path shown in the error?

Why are you running the 32 bit version on a 64 bit system?
Yep, the file exists in the shown path. I'm running the 32bit version because I use avisynth plugins and scripts that are not supported yet on the x86_86 build of avisynth (that and there is no official 64bit build of avisynth yet).

Groucho2004

26th July 2010, 10:53

Using driver version 196.21 now. Works fine with 2022 (it seems).

tormento

26th July 2010, 11:34

@neuron2

Can't get the multiple license file work. Tried to put every license on different line, like in old versions but nicht.

Any new syntax is required?

Guest

26th July 2010, 12:38

After reading these posts and updating to the reposted 2022, I get this error:

http://img713.imageshack.us/img713/5352/errorlu.jpg
Win 7x64, Geforce 460, 1GB video mem, driver version 258.96.

I'm using the 32bit version of dgindexnv OK, that's a Fermi that has CUDA compute capability 2.0. I have to include a version of the cubin file that is compiled with -arch sm_20, and if possible, load the correct one dynamically. I'll work on that and report back later today.

Guest

26th July 2010, 13:03

@neuron2

Can't get the multiple license file work. Tried to put every license on different line, like in old versions but nicht.

Any new syntax is required? Nope, I just goofed it up. I slipstreamed the fix. Get the corrected DGIndexNV from a re-download of 2022. Thank you for pointing it out.

Guest

26th July 2010, 13:09

Using driver version 196.21 now. Works fine with 2022 (it seems). Thank you for the test result. I have changed the driver version requirement in the Readme to version 196.21 or higher.

Sharktooth

26th July 2010, 14:05

you should change it to "the latest driver available for your videocard"

Guest

26th July 2010, 14:07

you should change it to "the latest driver available for your videocard" Nah, because the very latest drivers are apparently hosed right now.

Guest

26th July 2010, 14:09

OK, that's a Fermi that has CUDA compute capability 2.0. I have to include a version of the cubin file that is compiled with -arch sm_20, and if possible, load the correct one dynamically. I'll work on that and report back later today. Please try this test version on your Fermi (32-bit binaries):

http://neuron2.net/dgdecnv/fermi.zip

Put all three files together.

aegisofrime

26th July 2010, 18:23

Nah, because the very latest drivers are apparently hosed right now.

Hosed? How so?

It's interesting that you should post this, because I'm getting random BSOD errors when using DGSource() for H.264 content. I have been wondering what's the cause of the BSODs...

Using a Palit GTX 460 Sonic here...

tormento

26th July 2010, 18:28

Nah, because the very latest drivers are apparently hosed right now.
Nah, the latest are whql (whatever it counts) and very stable when encoding or gaming or ht'ing. At least on my rig.

tormento

26th July 2010, 18:29

I have to include a version of the cubin file that is compiled with -arch sm_20
Noticed that the latest CUDA sdk is out?

MrVideo

27th July 2010, 00:10

Yep, the file exists in the shown path. I'm running the 32bit version because I use avisynth plugins and scripts that are not supported yet on the x86_86 build of avisynth (that and there is no official 64bit build of avisynth yet).

Ah OK. Guess that means I won't be going to 64 bit anytime soon, since I too use AVISynth.

Guest

27th July 2010, 00:17

Noticed that the latest CUDA sdk is out? Do you seriously think I am not keeping myself informed on CUDA developments? :devil:

MrScientist

27th July 2010, 02:00

Guest

27th July 2010, 03:12

hi, after a system rebuild, i can't get dgindexnv to save the dgi index file for me. i can load/add a file (mkv or m2ts), but i can't do a "save project." this is for any file i try. and i can play all of the files on my system. what am i missing? thanks. You're missing a proper trouble report. All system details, DG version number, video driver version number, exactly what happens when you open a file.

Is this a licensing issue, i.e., does the file show video? If you have rebuilt your system, you'll have to regenerate your license, because your machine ID will have changed. Did you do that?

If video shows then exactly what happens when you do Save Project?

MrVideo

27th July 2010, 03:19

but i can't do a "save project."

Did you configure your Windblows system correctly. You might not have permission to save the project where it is attempting to put it.

What happens when you try and create the DGI file via the commandline?

MrVideo

27th July 2010, 03:21

Do you seriously think I am not keeping myself informed on CUDA developments? :devil:

Don't ya know that you have your blinders on and your head stuck in the sand, both at the same time? :D

Guest

27th July 2010, 03:25

aegisofrime

27th July 2010, 03:48

Hey, don't forget rule 11, all posts must have useful content. Mine didn't but I can't seem to strike myself. So you get to slide too.

I wish lych_necross would come back. I don't want to have to buy a Fermi card. :p

I have a GTX 460, and I can do the usual stuff just fine. Creating an index file, encoding using x264 using DGSource with Deinterlace=2...

That said, with all the hype nVidia has piled on Fermi, is there anything special that Fermi cards can do that others can't?