DG NV tools [Archive] - Page 43

meatwad

17th July 2010, 01:30

I just upgraded to a gtx 470 and I was amazed at the improvement it had with DG NV Tools. The same clip with the same settings was done on the same machine with different video cards.

9600 GSO 512 MB:

encoded 16046 frames, 45.07 fps, 2053.91 kb/s

------------------------------------------------------------
x264 Statistics
------------------------------------------------------------

Start: 3:24:02 PM
End: 3:29:58 PM
Duration: 00:05:56

GTX 470 1280 MB:

encoded 16046 frames, 48.92 fps, 2082.12 kb/s

------------------------------------------------------------
x264 Statistics
------------------------------------------------------------

Start: 6:51:56 PM
End: 6:57:25 PM
Duration: 00:05:28

The X264 profile used was Divx Plus. Anyway, that's a good improvement over the 9600 GSO I had and the 210 I tried was even lower. I haven't tested the 470 with DXVA decoders yet. I'm only posting this because I didn't think I'd see that much improvement. If you're doing a long encode, those 3-4 fps will come in handy. Also, this is the 32 bit version. I'll test the 64 bit when I get a chance. Also, all the info you gave me in a previous post proved quite helpful neuron2--Thanks.

hydra3333

17th July 2010, 01:31

OK. searching for dgsplit now ...

Guest

17th July 2010, 01:33

http://neuron2.net/dgsplit/dgsplit11.zip

hydra3333

17th July 2010, 01:52

Thanks. Well, that's frustrating. DG split stuff works with the first few of chunk sizes up to 50Mb so far. So I tried the full file again and just waited (v2018 was running in the background) - after a while it finished just this and a 24kb .ac3 file - obviously incorrect.
DGMPGIndexFileNV8
E:\SOFTWARE-2\MULTIMEDIA\DGIndex-DGAVCDec\NV-purchased\X-2020\

G:\HDTV\AFL\TEST\test.mpg 3456743424

STREAM 3
LUMFILT 0 0
CLIP 0 0 0 0
RANGE 0 0 3456743423 0
AUDIO 80

SEQ 2084
SEQEXT 0
GOP 1
FRM I 3 1 0 0
FRM P 3 1 0 0
FRM P 3 1 0 0
FRM P 3 1 0 0
FRM P 3 1 0 0
FRM P 3 1 0 0
FRM P 3 1 0 0
FRM P 3 1 0 0
FRM P 3 1 0 0
FRM P 3 1 0 0
FRM P 3 1 0 0
FRM P 3 1 0 0
FRM P 3 1 0 0
SEQ 464929
SEQEXT 0
GOP 0
FRM I 3 1 0 0
SIZ 1440 x 1088
FPS 25000 / 1000
CODED 14
PLAYBACK 14
0.00% FILM
I'll try to use DGsplit with larger sizes and see how I go.

Guest

17th July 2010, 01:58

I tried on some of my files and found a bug in the program stream parser. I'll work on that but if you can give me a stream that fails it will be helpful.

hydra3333

17th July 2010, 02:06

OK, sure thing. still narrowing a chunk down for you from one of 500Mb that fails :)

Guest

17th July 2010, 02:17

Try this version (32-bit):

http://neuron2.net/guest/pavel.zip

If it works I'll make a release of 2021 right away as there are some other things to be fixed as well.

hydra3333

17th July 2010, 02:24

OK, here's the first 20Mb chunk from the front of the file. http://mfi.re/?r94n4f3f6cck4lz The dgi it yields looks similar to the "full" one above
DGMPGIndexFileNV8
E:\SOFTWARE-2\MULTIMEDIA\DGIndex-DGAVCDec\NV-purchased\X-2020\

G:\HDTV\AFL\TEST\this-fails-20mb_0.mpg 20971520

STREAM 3
LUMFILT 0 0
CLIP 0 0 0 0
RANGE 0 0 20971519 0
AUDIO 80

SEQ 2084
SEQEXT 0
GOP 1
FRM I 3 1 0 0
FRM P 3 1 0 0
FRM P 3 1 0 0
FRM P 3 1 0 0
FRM P 3 1 0 0
FRM P 3 1 0 0
FRM P 3 1 0 0
FRM P 3 1 0 0
FRM P 3 1 0 0
FRM P 3 1 0 0
FRM P 3 1 0 0
FRM P 3 1 0 0
FRM P 3 1 0 0
SEQ 464929
SEQEXT 0
GOP 0
FRM I 3 1 0 0
SIZ 1440 x 1088
FPS 25000 / 1000
CODED 14
PLAYBACK 14
0.00% FILM

edit: that was a strange URL. Maybe it's this ? http://www.mediafire.com/?r94n4f3f6cck4lz

hydra3333

17th July 2010, 02:33

Try this version (32-bit):

http://neuron2.net/guest/pavel.zip

If it works I'll make a release of 2021 right away as there are some other things to be fixed as well.

Yes, that seems to have done the trick. Although,very few of the fields in the "video" box in the grey window get filled in - only
video type
coded #
playback #
frame rpts
field rpts
film %

Is it supposed to be like that ?

Guest

17th July 2010, 02:44

Is it supposed to be like that ? Yes. I do it to speed up the indexing operation. Use Play/Preview if you are interested in that data.

Guest

17th July 2010, 03:18

* Save BMP and Copy Frame to Clipboard now save the original frame size (with cropping and luma filtering honored).
Previously, if the frame was reduced by half for display, the reduced frame size was saved/copied.
Now the saved frame will accurately represent what will be served via your script.

* Corrected NV12 to RGB conversion based on the matrix coefficients (for the 32-bit version only).

* Fixed the following bug: Enter single-step mode, minimize the window, and then restore the window;
DGIndexNV hangs.

* The Help menu is now not disabled during play/preview/indexing.

* Reduced GDI load from updating the trackbar.

* Fixed a bug in the program stream parser that could cause play/preview/indexing to fail.

* DGSource() and DGMultiSource() are now synonyms. The Avisynth source filter is named DGDecodeNV.dll.

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

hydra3333

17th July 2010, 04:07

Yes. I do it to speed up the indexing operation. Use Play/Preview if you are interested in that data.

OK thanks ! I noticed the log file was missing the info as well.

A brilliant tool getting even better.

Lyle_JP

17th July 2010, 05:16

2021 seems to be a major step backwards. Indexing may be faster (although in x64 it seems negligible), but I haven't been able to get so much as one encode off the ground! It's like being back on 2018. Actually, it's worse, as I could eventually get 2018 to play ball with me. Here's the latest crash:

Problem Event Name: APPCRASH
Application Name: MeGUI.exe
Application Version: 0.3.5.5
Application Timestamp: 4c3e0a57
Fault Module Name: nvcuda.dll
Fault Module Version: 8.17.12.5721
Fault Module Timestamp: 4c0d6ea4
Exception Code: c0000005
Exception Offset: 0000000000001bf9
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033
Additional Information 1: b7f6
Additional Information 2: b7f643e3a3298f138e243807a424f49d
Additional Information 3: 2877
Additional Information 4: 2877193e441150ee23c7d37ca3b4f154

Win7 64-bit, all x64 tools, 257.21 forceware.

The crashes happen the minute I try to process a queue, or open an avs script one too any times, or even once sometimes.

hydra3333

17th July 2010, 06:51

Works here. 32bit xp-sp3.

Groucho2004

17th July 2010, 08:23

Works fine for me as well.
OS: WinXP SP3 32bit
Driver: 197.45

Also working:
OS: Win2003 Server SP2 32bit
Driver: 197.45

I should probably mention that this is without any "GUI" involved. For the people who have a problem and unfortunately depend on these frontends I suggest to try it without a "GUI" to isolate the problem.

sumawo13

17th July 2010, 10:51

Read the release notes.

I generated my new license and now I'm using 2021 but it still just doesn't do anything when I open any files.

Guest

17th July 2010, 13:25

The crashes happen the minute I try to process a queue, or open an avs script one too any times, or even once sometimes. Does it happen when you simply open your script in VirtualDub? I've just tried it on my 64-bit environment and see no issues. Perhaps something went haywire in the MEGUI update.

There are no changes in 2021 that would account for something like this.

Guest

17th July 2010, 13:27

I generated my new license and now I'm using 2021 but it still just doesn't do anything when I open any files. Make sure your license file is named "license.txt". That is an 's' in there NOT a 'c'. Then put it in the same directory as DGIndexNV.exe. Open DGIndexNV and make sure Options/License Switcher is set to License 1. Then open your source file.

Another way people mess this up is by including an extra space after the machine ID when generating the license.

Lyle_JP

17th July 2010, 13:28

Does it happen when you simply open your script in VirtualDub? I've just tried it on my 64-bit environment and see no issues. Perhaps something went haywire in the MEGUI update.

There are no changes in 2021 that would account for something like this.

I didn't do a MeGUI update. I updated 2021 directly. And yes, I did finally get some encodes started after a lot of crashing. The behaviors I'm seeing are precisely the way things were before the memory leak was fixed. I will test some with VeeDub and see what happens.

Guest

17th July 2010, 13:31

The behaviors I'm seeing are precisely the way things were before the memory leak was fixed. Then maybe you are somehow invoking the wrong DLL, maybe from your Avisynth plugins directory. The memory leak did not get "unfixed" in 2021.

Lyle_JP

17th July 2010, 13:44

Then maybe you are somehow invoking the wrong DLL, maybe from your Avisynth plugins directory. The memory leak did not get "unfixed" in 2021.

Not sure how that's possible. I deleted both old .dlls, and made a copy of the new DGDecodeNV.dll and called it DGMultiDecodeNV.dll to fool MeGUI. Both .dlls in my DGIndexNV folder are the new one, and they're the only .dlls in the folder. Is there something wrong with that methodology? Seemed pretty sound to me.

To clarify, there has never been (and still isn't) any DGDecodeNV dlls in my avisynth plugins directory. They're always explicitly invoked from the dgindexnv folder in my avisynth scripts.

Guest

17th July 2010, 13:50

It's OK to fool MEGUI like that. Just make sure there's nothing in your Avisynth plugins directory.

Give the results with VirtualDub alone. Ensure the script explicitly loads the correct DLL with LoadPlugin().

Lyle_JP

17th July 2010, 13:58

Okay, I reinstalled Forceware and now things appear stable (knock on wood). I remembered that earlier in the day Media Player Classic using DXVA gave me the only BSOD I've ever seen on Windows 7. I guess it done broke my Nvidia drivers!

Guest

17th July 2010, 14:06

I noticed the log file was missing the info as well. That's not ideal and I need to revisit this. Right now, it's that way to workaround a mysterious slowdown in Win7. I'll look into it.

Sharktooth

17th July 2010, 17:16

@Lyle_JP: ensure your AVS script loads DGDecodeNV.dll and uses DGSource otherwise, edit it accordingly
im going to push a megui update along with dgindexnv update. that should address the issue but the AVS script should be re-created or edited as described here: http://forum.doom9.org/showthread.php?t=155702

sumawo13

17th July 2010, 18:16

Make sure your license file is named "license.txt". That is an 's' in there NOT a 'c'. Then put it in the same directory as DGIndexNV.exe. Open DGIndexNV and make sure Options/License Switcher is set to License 1. Then open your source file.

Another way people mess this up is by including an extra space after the machine ID when generating the license.

I made sure of all of that, and it still doesn't work. I even tried generating a new license making sure I had no spaces this time but it generated the exact same license.

Guest

17th July 2010, 19:09

Email me your license file, DGIndexNV INI file and machine ID. Tell me here what is the path where DGIndexNV.exe is and where license.txt is. Be sure to use 2021 if you are opening VOB or MPG.

You must be goofing up because you are the only person of thousands that can't make it work.

sumawo13

17th July 2010, 19:23

senseiam

18th July 2010, 00:20

I made sure of all of that, and it still doesn't work. I even tried generating a new license making sure I had no spaces this time but it generated the exact same license.

I had the same issue you were having, make sure when you save the license .txt file DONT save it as UTF-8 or UNICODE, save it as ANSI

When I saved it as ANSI, it worked right away. :)

sumawo13

18th July 2010, 01:24

I had the same issue you were having, make sure when you save the license .txt file DONT save it as UTF-8 or UNICODE, save it as ANSI

When I saved it as ANSI, it worked right away. :)

Unfortunately that didn't work either, but thanks for the idea.

This is very frustrating. :(

Guest

18th July 2010, 01:24

Correct. And if you have display of file extensions turned off you may inadvertently make a file named license.txt.txt.

I just returned from the pool and will look at the files you sent me, sumawo13. One thing to do is start DGIndexNV and look again at the machine ID. Make sure it matches what you put in the license generator. Sometimes you switch on or off a network card and it changes your machine ID.

Guest

18th July 2010, 02:04

Unfortunately that didn't work either, but thanks for the idea.

This is very frustrating. :( OK, I patched DGIndexNV to return your machine ID. I replaced my license file with yours. Started DGIndexNV and everything worked fine.

Please check the reported machine ID in DGIndexNV Help dialog and make sure it matches the one you sent me. If it is correct I'll work with you by email using debug builds.

sumawo13

18th July 2010, 03:01

OK, I patched DGIndexNV to return your machine ID. I replaced my license file with yours. Started DGIndexNV and everything worked fine.

Please check the reported machine ID in DGIndexNV Help dialog and make sure it matches the one you sent me. If it is correct I'll work with you by email using debug builds.

It is indeed a match with the one I sent you, my machine ID has always been the same as far as I know, as I have onboard LAN and I've never put in a NIC.

Guest

18th July 2010, 03:04

Can your mail account accept a ZIP file? I ask because I get very irritated when I send a debug build and the receiver rejects it.

Guest

18th July 2010, 03:30

@sumawo13

Make sure your license file has a carriage return after the line of numbers.

Groucho2004

18th July 2010, 09:02

@sumawo13

Make sure your license file has a carriage return after the line of numbers.

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

sumawo13

18th July 2010, 10:05

@sumawo13

Make sure your license file has a carriage return after the line of numbers.

That did it! :D Thanks for your help, I can't believe it was something so simple.

stax76

18th July 2010, 10:19

I had also problems after I got new hardware, I forgot all steps required to get things working and needed some minutes to find out things. It seems if it fails to detect a license when trying to load a source file it just does nothing. A warning and instruction would be very helpful here, something like:

Failed to detect valid license, please do... take care of... white spaces like carriage return... ANSII encoding...

Maybe even validate text encoding and trim white spaces.

Groucho2004

18th July 2010, 10:35

A warning and instruction would be very helpful here

That's exactly what would make it very easy for crackers to find the entry point for the license check.

Edit: I suppose the license check could be done in a separate module/program which wouldn't expose the main application. However, when I load a file in DGIndexNV and I see the first frame I know that the license is working. Good enough for me.

stax76

18th July 2010, 11:08

I have some application to manage passwords and important things, I simple wrote a note there with all information needed like I do with other applications and tasks so I'm probably not gonna have problems again but when it just does nothing some might not expect a license issue, first I thought it might be a bad stream or something, later I found out I needed to regenerate my license for some reason.

Guest

18th July 2010, 12:56

I don't have a CRLF in my license file and it works... This is one of those mysteries of life. For me also that is true. But now two users have had this problem and fixed it this way. So I added that to the instructions sent upon activation.

I wonder if there are different behaviors of various runtimes in regards to fgets().

Sharktooth

18th July 2010, 14:32

mysteries of microsoft... probably different behavior with different OS versions or maybe even for different OS languages...

JoeH

19th July 2010, 09:26

For those of you waiting for 64-bit support, be advised that I placed my order today for the new rig. I went for the i7-980 Extreme together with the ASUS Rampage III Extreme mobo.

Thank you for your donations.

THanks for all the continued development and x64 version.

Curiosity question - how many FPS are you getting now when you play back a Blu-ray movie (1080@24p) at highest possible speed in DGIndex?

On my Core i7-920 with Nvidia 9500 GT I get about 40fps max.

Guest

19th July 2010, 11:31

It's all very system and stream dependent. Highest speed in DGIndexNV means settings Disable Display. For Avatar on my i7-980X x64 system I get 80fps with a GT 220 card. One recent report was 100 fps on a similar system with a 240 card.

jpsdr

19th July 2010, 18:46

I'm having trouble...
I've updated from 2020 to 2021, and i can't open files anymore, it seems license file is not recognised.
I thought serial has changed again, so i regenerate but number is the same.
I've save file in ANSI (it was already that, but just in case), tested with 1, 2 and no CRLF, but nothing work.
Going back to 2020, without any change on the license file, and everything works fine again...:(
Windows XP64 SP2 and Windows XP32 SP3 same behavior. Under XP64, both x64 and x86 version don't work.
Note : I've activated an ethernet controler, so i'm having now a MAC address and so a stable machine ID, there is no problem from this side, in theory.

^*^

19th July 2010, 19:25

Just bought new computer (i7-860, GT 240), installed Win7 x64 and purchased license 2 days ago. Everything works fine. I am getting 75-80 fps in DGIndexNV! But...I have spent (lost) 2 days to research how to preview (play back) AVS files. There was no problem with x264 - it coded from AVS+DGI without problem. But when I tried to preview AVS in Media Player (and AVSedit) I was getting error messages about YV12 problem and advice to install ffdshow. No word about how to configure it. And then I uninstalled ffdshow and installed codec pack from Shark007 with advice to enable ffdshow postprocessing. This helped me.
Dear Author! It would be very useful for new users to include in "DGDecNV Quick Start Guide" these few words about needed applications (and codecs) beside yours and Avisynth. It could save me 2 days. However, researching is much better way to learn something than just reading.

Sharktooth

19th July 2010, 20:28

Note : I've activated an ethernet controler, so i'm having now a MAC address and so a stable machine ID, there is no problem from this side, in theory.
Check if your hardware id has changed after the installation of the network controller.

Sharktooth

19th July 2010, 20:30

Guest

19th July 2010, 21:00

I'm having trouble...
Please contact me by email as I don't want to clutter the thread with everybody's individual travails. If necessary I'll send you debug builds etc. to try to find out the cause.

SomeJoe

20th July 2010, 05:12

Hi neuron2,

Just updated from 2009 to 2021. Got everything licensed, tool is running fine with one exception:

I have my own front-end that calls DGIndexNV.exe, and uses the -e and -h options to hide the interface and automatically exit. This was working properly in v2009. In v2021, the interface is not hidden and does not automatically exit.

The following command line is in use:

DGIndexNV.exe -i "T:\Temp BD Convert A\origVideo.h264" -o "T:\Temp BD Convert A\origVideo.dgi" -y 1 -e -h

This is on Windows 7 64 bit, on two different machines. Note that I am running the 32-bit version of DGIndexNV because I am still using 32-bit AVISynth.