Log in

View Full Version : DG NV tools


Pages : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 [62] 63

Guest
25th June 2014, 18:36
Did you figure out why it works with 2046?

2046 32-bit was built with VS 2005 Pro on WinXP 32, while 2047 was built with VS 2012 Express on Win8.1 64. Is it relevant? I don't know. I can't try VS 2013 until nVidia supports it in the CUDA toolkit. VS 2005 won't run on Win 8.1.

There is no reliable information about this symptom. I have seen references to VS being involved, but I don't know how much credence to give them.

We could try the 2005 compile again but it would be a big hassle as I decommissioned that machine. :( But I can try building it on a Win 7 32 with VS 2005. I'll install VS 2005 and provide a test build. May take a while...

Guest
25th June 2014, 18:37
The folder option should be functional on all folders, including desktop. Not necessarily. You have to select to apply it to all folders. Did you do that?

Does your active user account have Admin privileges?

Morku
25th June 2014, 19:31
I changed the settings in system control and folder option, so it should affect the whole PC. If I am doing wrong, tell me how I do correctly.
I am administrator of the PC, but with enabled User Account Control (default since Vista).
Hopefully it will work with VS2012, too. 2005 is really old.

Anyway, when you have the same OS, why it doesn't happen to you, too?

Groucho2004
25th June 2014, 21:27
2047 was built with VS 2012 Express on Win8.1 64. Is it relevant?
Do you link the binary statically to the VS and SDK libraries? If so, you might want to try linking dynamically.
There may be a incompatibility with the SDK version you use with VS2012 and Windows 8.1.

Edit: One more thought - try setting "lpstrInitialDir" in the OPENFILENAME structure to something that's not protected by UAC, like "c:\" (unless you have done so already).

Guest
26th June 2014, 14:30
Do you link the binary statically to the VS and SDK libraries? If so, you might want to try linking dynamically.
There may be a incompatibility with the SDK version you use with VS2012 and Windows 8.1. Statically, of course. Dynamic is a bridge too far for me, to prevent a boat load of user issues with runtimes not installed, etc.

Edit: One more thought - try setting "lpstrInitialDir" in the OPENFILENAME structure to something that's not protected by UAC, like "c:\" (unless you have done so already). It gets set to the location of the source stream so that the DGI file gets created there.

Guest
26th June 2014, 14:31
Morku, please re-download DGIndexNV_Morku.exe and give it a whirl. I changed the way the ofn struct is initialized. Probably it won't help but you never know.

Also, following up on Groucho's idea, can you try with UAC disabled?

Groucho2004
26th June 2014, 14:45
Statically, of course. Dynamic is a bridge too far for me, to prevent a boat load of user issues with runtimes not installed, etc.
I still think you should give it a try to narrow down the problem. Installing the 2012 runtimes should not be an issue.

Morku
26th June 2014, 17:11
Still crashs at the same two described points.

Since Windows 8, UAC is more integrated. Turning off UAC in system settings don't turn off this feature completly, you have to go in regestry in set EnableLUA to 0. Without UAC, Metro Apps wont work anymore.

So I turned off UAC, set EnableLUA to 0, as recommended, I rebooted my PC and started DGIndexNV with administrator privilegs. More rights are not possible ^^ But it still crash on desktop and D:\Sonstiges
I think the typical DGIndexNV user is able to install runtimes and know why :)

Guest
26th June 2014, 17:36
I think the typical DGIndexNV user is able to install runtimes and know why :) Possibly, but at this point attributing the problem to the runtime version is just a wild guess.

Nevertheless, re-download and try the dynamic build I made.

Morku
26th June 2014, 17:42
Sadly doesn't work neither at the same two points.

Guest
26th June 2014, 17:45
Here is something else to try:

"We found another thread on ServerFault reporting a similar problem ("Typically it crashes when you click File/Open or File/Save, but not every time"). Another user (PG) was able to resolve the problem by excluding the application from Data Execution Prevention, on Microsoft's recommendation.

We checked the Data Execution Prevention setting and found that it was set to "Turn on DEP for all programs and services except those I select." After changing it to "Turn on DEP for essential Windows programs and services only", the problem no longer occurs."

http://www.softwareok.com/?seite=faq-Windows-8&faq=145

Guest
26th June 2014, 17:54
Also try temporarily disabling shell extensions with, e.g.. ShellExView.

Morku
26th June 2014, 17:57
When I want to add DGIndexNV_Morku.exe in that Data Execution Prevention list, it says "this program have to execute with active Data Execution Prevention. You can't disable it for that program". But I will try without having it into list.

I don't know if I have additional shell extensions. How I can disable it, without breaking my user experience (so to be able to turn on back again). Maybe I should try in windows safe mode?

EDIT: Nope, didn't work, but I was unable to add anyway... In safe mode, there was some random error messages, like "Failed to create video decoder" after loading a file what is normal I think, BUT... it didn't crash on desktop and my folder anymore.

Guest
26th June 2014, 18:11
Don't try to add an exception, just click the "Turn on DEP for essential Windows programs and services only".

We disable extensions just for debugging. i don't suggest to leave it that way.

Morku
26th June 2014, 18:17
There is no "Turn on DEP for essential Windows programs and services only". Only 2 options and the second says: "Turn on DEP for all programs and services except those select:". Am I wrong place?
I tried this option, rebooted and... didn't work.

EDIT: Wait, it seems the secure start of UEFI doesn't allow me to disable DEP. I will sisable secure start now.

Guest
26th June 2014, 18:23
I don't know why you don't have it. I do.

Anyway, I think a shell extension is more likely.

Also, try turning off thumbnails for your Desktop directory.

Morku
26th June 2014, 18:37
Okay,
I disabled secure start in UEFI. After that i was able to disable DEP completly with that tutorial: http://www.thewindowsclub.com/disable-data-execution-prevention
I completly disabled UAC
in folder options, I disabled thumbnails and this popup thing for all folders (including desktop).
I disabled all shell extensions of third party software (the pink entrys in ShellExView). Or do you think about of any other shell extension?

After all, I rebooted again and tried again. No difference. It crash on desktop and D:\Sonstiges. It only works in safe mode.

Guest
26th June 2014, 18:38
I've really reached the end of my rope here. All I can suggest is that you don't try to save a project to your Desktop directory. Is that so horrible?

Morku
26th June 2014, 18:44
No, it's not, because I want save it to a subfolder of D:\Sonstiges ^^
After all, it's not a solution for public. Is there so much difference between 2046 and 2047 not to use 2046 anymore?
I can try to disable all shell extensions, if it wont break my pc.

Guest
26th June 2014, 19:09
There's nothing more I can do. Contact Microsoft for further support.

Guest
27th June 2014, 17:49
I made one last attempt and slip-streamed all the changes into the release 2047 version. I can't think of anything else to do about this problem. A last resort for the few users (currently only two) that have experienced this is to not locate your DGI file on the desktop.

RedDwarf1
27th June 2014, 20:36
I made one last attempt and slip-streamed all the changes into the release 2047 version. I can't think of anything else to do about this problem. A last resort for the few users (currently only two) that have experienced this is to not locate your DGI file on the desktop.

I find it unbelievable that people would have any need to do such a thing in the first place. It seems totally illogical to put stuff on the desktop. Icons maybe but anything else no.

Do people actually move large video files to their desktop or am I misunderstanding things? I cannot see any other reason why a dgi file would need to be on the desktop.

I don't think that it will bother too many people.

Guest
28th June 2014, 00:24
Well, the user has redirected the desktop directory to a folder on another drive and while we may not consider that scenario desirable that's what he wants to do. I would fix it if I could but the only thing left to try is to convert to Vista+ common file dialog support (via COM). It would be a big job for minimal gain, IMHO.

Shevek
28th June 2014, 11:47
I totally agree

1 or 2 edge cases (who are in fact not even following the Windows standard) with a usable workaround should not require a global change to code

I work in software and we have been fighting this for years and finally have a lead who agrees with us and fights our corner.

I think you've been generous in the time you have spent on it so far.

Groucho2004
3rd July 2014, 10:23
:p No problem. Always looking forward to testing out things.
I noticed in your signature that you have a GTX750. Could you please run the test in this thread (http://forum.doom9.org/showthread.php?t=170567)?

qupfer
8th July 2014, 17:32
Hi, I have the same Problem.

If I press F4 (or click on save) DGIndexNV 2047 will crash immediately. Licence-File seems to be okay, because video is shown correct.

It will also Crash with other "export" functions like "F1"

Edit: after some tests: It crashs allway on the second "file select dialog".
I mean, for example.
Load Project --> Cancel --> Load Project --> crash
Load File --> Cancel --> Load File Crash
Load File --> OK --> Save --> Crash
and so on

And I will post my problem in the offical board as soon as my account is activated

Groucho2004
8th July 2014, 17:40
Hi, I have the same Problem.
You're not going to get support here. Try the official support forum (http://rationalqm.us/board/index.php).

Doom9
8th July 2014, 17:45
You're not going to get support hereWell.. that depends. People helping people is a big part of this forum. It doesn't always take the author (and he has hinted that he's still lurking around).

Groucho2004
8th July 2014, 17:56
Well.. that depends. People helping people is a big part of this forum. It doesn't always take the author (and he has hinted that he's still lurking around).
I was referring to his particular problem for which I doubt he's getting support any other place than Don's forum.

videoh
8th July 2014, 18:39
make sure you get the latest build of 2047 from DG's website

look at the main DGDecNV page to see the way to get the latest binaries

he's been trying to fix this and testing is still going on

Video Dude
12th July 2014, 21:03
Build 2048 is now available. Also, build 2047 got a new slipstream release with a couple of bugs fixed.

hydra3333
13th July 2014, 11:59
is this new location official ?
http://rationalqm.us/board/index.php

Sharc
13th July 2014, 12:04
-- Yes --

hydra3333
13th July 2014, 12:07
Hang on. Just rebooted my PC and it went to http://neuron2.net/board/index.php

edit: and now it's swapping between them :( doesn't look kosher.

Video Dude
13th July 2014, 13:56
edit: and now it's swapping between them :( doesn't look kosher.

It's ok and to be expected during the transition. neuron2.net is still active for some time so links can redirect. There is a thread dedicated to this in Don's forum if you want more info.

hydra3333
13th July 2014, 14:48
Thank you. I'll visit there.

I like/use his software and was/am happy to donate for it since it's so useful for my purposes (filtering home videos captured by a DVD recorder ... yeah, don't comment on that ... and some TV caps for timeshifted viewing)

videoh
3rd June 2017, 17:19
DGDecNV 2053 slipstream 102 now supports full bit depth delivery for HEVC 10-bit and 12-bit streams.

Thank you to nVidia for CUVID evolution.

stax76
3rd June 2017, 17:31
Great news. Was there a change regarding license in 2053? I couldn't get 2053 working some weeks ago, I tried to regenerate the code with the license web page but it didn't help, 2052 works.

videoh
3rd June 2017, 17:44
Greetings, stax76. Thank you for your interest.

Item 2 in the Readme.txt (changed in 2053):

2. If you place DGIndexNV.exe and DGDecodeNV.dll in different directories, you must put a copy of your license file in both directories.

If that does not resolve the matter for you, please post again. Sorry for the curve ball.

stax76
3rd June 2017, 18:04
Thanks videoh, problem solved.

videoh
3rd June 2017, 18:27
Great to hear. Thank you for the update.

Morku
28th July 2019, 10:44
Short question: On which relevant hardware is DGIndexNV generate the machine ID for the license?
Yesterday I had to generate a new one to make it work again, but no hardwarechanges were made at all. Thanks in advance.

Sharc
28th July 2019, 10:53
Short question: On which relevant hardware is DGIndexNV generate the machine ID for the license?
Yesterday I had to generate a new one to make it work again, but no hardwarechanges were made at all. Thanks in advance.
As far as I remember there has been a general request for renewing the licenses (few months ago or so).

Morku
28th July 2019, 11:53
I know, but this change came with a new binary release... years ago(?)

I use DGIndexNV frequently with current builds. Yesterday I had to renew the license. And the truth is: this came with a crash of my PC before when I had an encode with x265+DGIndexNV and my PC did a Secure Backup BIOS B to A itself.
So my BIOS was back to stock. I upgraded back to latest BIOS and set everything to same settings, but... I also had to renew my license.

So "something" has been changed on my PC, for example a checksume on BIOS?
So the information could help where I could start to check my PC.

gonca
28th July 2019, 12:18
I know, but this change came with a new binary release... years ago(?)

I use DGIndexNV frequently with current builds. Yesterday I had to renew the license. And the truth is: this came with a crash of my PC before when I had an encode with x265+DGIndexNV and my PC did a Secure Backup BIOS B to A itself.
So my BIOS was back to stock. I upgraded back to latest BIOS and set everything to same settings, but... I also had to renew my license.

So "something" has been changed on my PC, for example a checksume on BIOS?
So the information could help where I could start to check my PC.

http://rationalqm.us/board/viewtopic.php?f=5&t=463&p=9131&hilit=license+generation#p9131

Look at slipstream 161

videoh
28th July 2019, 15:27
Which HW is checked depends on which version of DGDecNV you use.

The latest version uses your motherboard serial ID if a valid one is present. If not, then the HW serial number of your system disk is used as fallback. Previously the volume ID was used but that could change when the OS is updated, etc.

Morku
28th July 2019, 16:06
Thank you.
Before I had to renew, it was the exact same version. Nothing was changed.
HDD and OS is also exakt the same.

So the BIOS Security Backup must have changed my motherboard serial... :confused: Interesting :D
Who knows.

videoh
28th July 2019, 16:40
If your system was using the fallback, then it could have been the HDD serial that was changed. But as you say, who knows? The important thing is you are running again and such crashes are rare. Not worth investigating further, IMHO.

Morku
28th July 2019, 18:21
I think the security BIOS backup wiped my motherboard serial. When I go for: wmic bios get serialnumber
I get:
SerialNumber
To Be Filled By O.E.M.

I will ask the board manufactory.

Didée
12th August 2019, 21:37
Seems I'm facing a very similar problem with DG NV Tools.

Just to note, I'm in "video retiree" and hardly do any video tasks at all anymore. The last time I've created & processed a video project with DGDecNVTools was in autumn of 2017. And also one project in 2016. Yes really. Now these days, trying to open any video in DGDecNV throws me an "invalid license" ... mostly. Sometimes it's also "application doesn't response".

I'm not here to complain. Once I asked Donald how to proceed with donating if I don't have a PayPal account, and Donald was so generous to give me a free license. I'm still very thankful for this. But after many years of so relaxing problem-less serving of video files (ffmpeg is a PITA to me, and from experience oftentimes unreliable and/or unpredictable), I feel bit lost about getting back into the swing of things when I can't use the good old & approved tools ...
My hardware has not changed in any way over the years. Only change is with USB devices ... one more USB HDD, and a change of the USB WiFi adapter. That's all. And of course a good bunch of Windows (still 7) Updates. USB devices shouldn't be part of the hardware ID generation, or should they?
*exe, *dll and *license are all in the proper locations. All that stuff last used in 2017, all good & working. New call in 2019 ... "invalid license".

Some hint for an old man who just tries to make things working like they did in the past?