DG NV tools

[Guest]

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

[SomeJoe]

I see ... field operation selection moved into the DGSource() call.

No problem, thanks. :)

[Guest]

-y is not field operation selection.

[SomeJoe]

OK, I could have sworn that -y was the field operation selector (Honor Pulldown, Ignore Pulldown, Force Film), but evidently it was the RGB scaling selector. I must have confused it with the -FO= option from DGIndex. My front end has a choice to use either DGIndex or DGIndexNV, and I still have code in there to do the field operation selection in the command line for DGIndex.

I had already altered my front end to use fieldop= in the DGSource() call when using DGIndexNV, I just forgot about it.

I will remove the -y 1 from the command line, that should take care of the problem, I never changed it from 1 anyway.

[Guest]

OK, I could have sworn that -y was the field operation selector. Why would you think that when it has always been clearly documented in the user manual?

[SomeJoe]

Why would you think that when it has always been clearly documented in the user manual?

I should not even dignify such a ridiculous question with a response, but evidently you don't read too well either.

I am a human that is not infallible. In my previous post which you glossed over, I clearly stated:

"I must have confused it with the -FO= option from DGIndex"

and

"I had already altered my front end to use fieldop= in the DGSource() call when using DGIndexNV, I just forgot about it."


Yet, after clearly owning up to my own mistake, you can't see fit to let it go.

I have indeed read every manual included with DGIndex/DGIndexNV cover-to-cover, and again because I'm not infallible, missed the fact that in Appendix D of the DGIndex 2021 manual, the -y option has disappeared whereas it was there in the last version I used and looked at, version 2009.

If you had included a change log or version history like I do when I release freeware (http://utalk.att.com/t5/High-Speed-Internet-Access/U-Verse-Realtime-v1-3-0-0/td-p/229448), it would have been easy for me (or anyone else) to notice that this option, the removal of which breaks existing software, had been removed. You also could have made the software ignore that option on the command line if present instead of ruining the command line parsing for remaining options.

To treat one of your paying customers as a fool in a public forum is a disgrace. I never do such a thing when I'm on the other end of freeware software support, and you should be ashamed.

[Guest]

You claimed that you thought -y was the field operation ("I could have sworn that -y was the field operation selector"). From day 1 it has been documented as the PC/TV scale option. I was curious how you could have made that error so I asked you, in a civil manner.

Don't try to blame your failure to read the documentation on me. If you continue to attack me personally as you are doing, I will issue a rule 4 strike.

I am a seeker after truth, that is all. If you say something that does not make sense or is inconsistent, I will call you on it, just as I would hope others call me on my miscues.

Followup to PM please.

[Guest]

Does anyone use the dinky luma filter in DGIndexNV? I'd like to get rid of it. I have implemented NV12->RGB24 on the GPU using a CUDA kernel, thereby speeding up the display and making the display code common between the x32 and x64 versions. I suppose I could add the luma processing to the kernel but it just seems silly when that filter is so little used and luma adjustment can be done better using Levels() in the script anyway.

Thoughts?

[Clumpco]

Does anyone use the dinky luma filter in DGIndexNV?
Nope, never.

[Audionut]

Does anyone use the dinky luma filter in DGIndexNV?

There's a luma filter :rolleyes:

[adiabatic]

Oh wait.. there's a luma filter?!?! I'm going to use it now!

[laserfan]

What's a "luma filter"? :p

I think you may have answered your own question, particularly since most everybody here always wants to do things "the best way"! ;)

...luma adjustment can be done better using Levels() in the script anyway.

[Guest]

OK, then, say your goodbyes to the luma filter.

BTW, I have fixed the bug in the licensing check. I know of only one person that was blocked by it (excluding those who worked around it with the newline hack), but if you cannot get your valid license to work, re-download 2021, which was slipstreamed with the fix.

[dgeise]

Hey Don,

First, kudos on continued frequent updates to DGNV tools.

However, I have a pretty large & growing library of raw HD footage captured from my various camcorders. It's up to about 500GB and growing. I like to keep up with your updates, but sometimes I don't realize the full impact of going to a new version until after installing the update. Things like requiring re-indexing, changes to the API, etc. are OK if I expect them but not always welcome when not anticipated.

So I'd like to make a request. Could you publish some form of a change log with new releases? Just a list of bugs fixed, features added, and whether AVS and/or DGI files are effected would be really helpful. This would help me plan my updates a little better.

:thanks:

[Guest]

It's published here in this thread on every new build. I notify of changes to the DGI format version.

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

[rack04]

OK, then, say your goodbyes to the luma filter.

BTW, I have fixed the bug in the licensing check. I know of only one person that was blocked by it (excluding those who worked around it with the newline hack), but if you cannot get your valid license to work, re-download 2021, which was slipstreamed with the fix.

My license file was working with "old" 2021 but not with the slipstreamed fix.

[Guest]

Do you have a line feed after your line of numbers in the license file. If not, add it.

If that does not help, then contact me by email, sending your machine ID and your license file.

[rack04]

Do you have a line feed after your line of numbers in the license file. If not, add it.

If that does not help, then contact me by email, sending your machine ID and your license file.

email sent.

[Guest]

Did you add the line feed?

[rack04]

Did you add the line feed?

No but adding the line fixes the problem.

[Groucho2004]

did you add the line feed?
no but adding the line fixes the problem.
:):):):):)

[Guest]

That Pythonesque exchange was due to editing.

The next version won't care if one is there or not. Sorry for the inconvenience. I'll get it right. :rolleyes:

[yup]

Hi Donald!

I try upgrade from 2020 to 2021 and can not (2020 work fine for me). I overwrite old files (2020) to new and now I can not show opened mts files. I could generate new license?

With kind regards yup.

[rack04]

Hi Donald!

I try upgrade from 2020 to 2021 and can not (2020 work fine for me). I overwrite old files (2020) to new and now I can not show opened mts files. I could generate new license?

With kind regards yup.

Please review the last few posts in this thread.

[Guest]

I try upgrade from 2020 to 2021 and can not (2020 work fine for me). I overwrite old files (2020) to new and now I can not show opened mts files. Open your license file and put a return after the line of letters. If you downloaded 2021 some time ago, please re-download it as a fix for licensing issues was slipstreamed.

[Guest]

I have just added a complete history of changes listing to the 2021 ZIP file.

[laserfan]

I have just added a complete history of changes listing to the 2021 ZIP file.Another great reason to re-download it. Many thanks for including this.

[dgeise]

Props for the changelog - many thanks.

Unfortunately I'm having a problem upgrading from 2020 to 2021.

Build 2020 contains a DGMultiDecodeNV.dll but no DGDecodeNV.dll.

Build 2021 contains DGDecodeNV.dll but no DGMultiDecodeNV.dll.

Just to test I copied DGDecodeNV.dll to DGMultiDecodeNV.dll in 2021 and that appears to fix the problem.

So either I'm a little confused or there's a small problem in 2021. Which DLL is the official DLL name we're supposed to use?

:helpful:

[rack04]

Props for the changelog - many thanks.

Unfortunately I'm having a problem upgrading from 2020 to 2021.

Build 2020 contains a DGMultiDecodeNV.dll but no DGDecodeNV.dll.

Build 2021 contains DGDecodeNV.dll but no DGMultiDecodeNV.dll.

Just to test I copied DGDecodeNV.dll to DGMultiDecodeNV.dll in 2021 and that appears to fix the problem.

So either I'm a little confused or there's a small problem in 2021. Which DLL is the official DLL name we're supposed to use?

:helpful:

Did you read the changelog?

[dgeise]

Did you read the changelog?

Doh! I caught the 'DGSource() and DGMultiSource() are now synonyms' but not the DLL name change.

So it's my confusion. Apologies for the brain-fade.:stupid:

*sigh* I wish AVISynth supported a CPP #include feature - that way I wouldn't have to batch change 45 AVS files or reindex & generate new files from a template. Oh well, as long as the syntax is now stable I;m happy.

[Guest]

You can rename the DLL back to the original to avoid having to change all your scripts.

[stax76]

@dgeise

You can use Windows Search to list all avs files, drop them on Notepad++ and use the 'Replace in all opened documents' feature, many text editors have such a feature.

[Farscape1]

i'm not sure if this really is a problem but i'll ask anyway.

i have just gone from 2018 to 2021. now when i save a project, only a few fields show any information (before all fields showed info and changed as the project saved).

now only these fields show info:

video type
frame structure
frame type
coded #
playback #
frame rpts (just shows 0)
field rpts (just shows 0)
film % (just shows 0.0)

the only fields that change as the project is saved are coded # and playback #. also the time is takes to save is much quicker (normally a plus but i'm wondering if it is performing as it should).

is that normal or do i have a problem? thanks. if i didn't give enough info, please let me know.

other info:

windows 7 ultimate
AMD Phenom II X4 940 (3.7 GHz)
comp1: GeForce GTS 250
comp2: GeForce 8600 GTS
comp3: GeForce 9500 GT

also, i didn't receive any performance boost (encoding) going from 8600 GTS to GTS 250. apparently number of cuda cores is rather irrelevant.

[linyx]

Welcome to the Doom9 Forums!

i'm not sure if this really is a problem but i'll ask anyway.

i have just gone from 2018 to 2021. now when i save a project, only a few fields show any information (before all fields showed info and changed as the project saved).


Taken from a few pages back:

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 ?

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

Also from the Changes.txt
* Performance improvements for indexing on many systems. The improvement is
substantial on most WinXP systems. The large pauses during playback in DGIndexNV
also now do not occur.

[Farscape1]

thank you very much for the info linyx (and thanks for the welcome).

i'll make sure to search a little more in the future.

[bebolan]

The license works in 2019, but 2021...

EDIT:

Sorry, it works now after changed license switcher to 3. But it is strange that my licence1 is as same as #3, #1 do'nt work.(win7 Ultimate)

EDIT2:

2019 works at vista Ultimate, 2021 not.

[Guest]

@bebolan

The licensing problems and their resolutions have been thoroughly discussed. If reading the material in the last few pages of this thread and the users manual does not help you then contact me by email.

[jimmydrac]

OK..I thought I was smart until today. I have a DGIndexNV license and a new gts 250 card with 191.07 drivers on win 7 x64. I have created the .txt license file, program loads but that's as far as I can get. It will not load ANY video file whatsoever. DGIndex works fine. But when I try to use DGIndexNV, the program starts up, but absolutely nothing happens when I load a file. No video shows up in the preview window. Am I nuts:stupid: or is this a common problem. I have read through every page here and the quick start guide and the manual but nothing helps.:confused:
Please Help
Thanks!!!

Edit: I still can't get it working but I just noticed that when I try to load a video file, of course nothing shows up in the preview window but when I check the audio tab, it show the correct audio stream!!! OK now I am totally confused. Updated video drivers to 258.96 but still no luck. Installed badaboom (I know I know) just wanted to see if my new video card was broke but it worked using gpu cuda....so I am stumped. Time for some coffee or jack daniels..not sure which LOL

Crap I'm stupid. 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.

[bebolan]

2021 & 2019 all do'nt work ! Why the machine ID could be changed ?

[Guest]

@bebolan

I told you to contact me by email. I'm not going to troubleshoot your license problem here.

[Guest]

* The DGI file format is bumped to NV9.

* The crappy luma filter was removed.

* NV12->RGB24 conversion for display is now executed on the GPU. This improves the
display rate in DGIndexNV and makes the code common for 32-bit and 64-bit versions.

* DGIndexNV now accepts a license file without a carriage return.

* The AlwaysCrop and AlwaysCancelOnAudioMismatch options are now exposed in the
GUI Options pulldown.

* The license file can now store multiple license numbers. The License Switcher
is therefore now unnecessary and was removed.

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

[kebulek]

Whatever I open with new version, I get these two errors. :(

http://img340.imageshack.us/img340/9991/error1qv.png
http://img412.imageshack.us/img412/7880/error2g.png

System: WinXP SP3, GF9600GT 512MB / 197.45 drivers

[jimmydrac]

Thanks again for all you hard work!!! I am getting between 9.5 - 15% speed bump on SD material. I will be trying some HD (1080 to 720) later today and can't wait to see what this can do!!






Win 7x64 q9550 2 gigs ram gts 250

[Groucho2004]

Whatever I open with new version, I get these two errors. :(

http://img340.imageshack.us/img340/9991/error1qv.png
http://img412.imageshack.us/img412/7880/error2g.png


Same here.

[laserfan]

Same here.Same nvidia driver as kebulek also?

[Groucho2004]

Same nvidia driver as kebulek also?

GT 240 with 191.07 on Win2K3 Server.

[^*^]

The same errors.
GT 240 (driver 257.21), Windows 7 x64

[Lyle_JP]

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.

[Guest]

Ouch. OK, I'll have to withdraw 2022 until I sort this out.

[Guest]

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.