Support forum for DG Tools

Sherman updated the manual to rc9, also fixed some older stuff that was out of date. Please check it out and advise any changes needed. Thank you!

http://rationalqm.us/misc/DGIndexNVManual_rc9.html

Thank you, Sherman.

For your reference, following are the functional changes versus build 221 (only the last one is not in rc9). Not all of them affect the user manual.

* Built with VS 2019 and latest tools. WinXP is no longer supported.
* Major performance improvement for indexing and demux.
* Removed the process priority option. Everything is now high priority, including the indexing thread. It is retained in the
INI file for backward compatibility but the value is ignored.
* Fixed several potential crashes exposed by static code analysis.
* Don't drop the last chapter for MPLS.
* Fixed lost demux settings after Save Project with MPLS open.
* Fixed bug in report progress for CLI.
* Fixed bug in detection of CLI invocation.
* Fixed extra byte at the end of demuxed video.
* The BUFFER_SIZE is reduced to optimize IO.
* Removed the obsolete decode modes option. The line is retained in the INI file and ignored.
* Fixed bugs in default save project path handling.
* No longer clear the Info dialog after a play/preview/indexing ends.
* Added MPLS browser (File/Open Disk).
* Removed the Full_Info option. It is always now enabled. It is retained in the
INI file for backward compatibility but the value is ignored. The Settings dialog
was compacted to make it smaller.
* Fixed erroneous values in the DGI file header section when the project
is saved without a prior play/preview, or when Full_Info was set to 0.
* Fixed wrong DELAY value from MKV when the first frame in the file is not a video frame.
* Implemented free resizing of the DGIndexNV window. It pretty much operates as expected. Note that:
a) The proportions of the stream are maintained.
b) Resizing is not enabled until a stream is loaded.
c) The Force Zoom and Video/Zoom stuff still works, but if you resize then the selected Zoom in the
Video/Zoom menu gets unchecked. You can then use the Video/Zoom menu to re-select a fixed
1, 1/2, 1/4, or 1/8 Zoom.
d) If you try to resize such that the buttons are obscured, then the resize will be limited.
e) If you have a Force Zoom in the INI file that would make the buttons obscured (given the
loaded stream), then a Zoom = 1 will be forced.
* Redesigned cropping. Note that cropped areas are now shown in gray and the main window is not resized.
* Base the granularity of the cropping trackbars on the size of the input clip, so that you can always adjust by 2 if needed.
* Replace the old template folder browse with IFileDialog as used by Open Disk.

Here is rc10:

http://rationalqm.us/misc/DGIndexNV_rc10.rar

* Replace the old template folder browse with IFileDialog as used by Open Disk.
* Fix broken W64 demuxing (LPCM tracks in transport streams).

Here is rc11:

http://rationalqm.us/misc/DGIndexNV_rc11.rar

* Made the cropping fill pattern a little more exciting. Britney
* Fixed regression that made the INI file incompatible between rc and 221 stable. They can share the INI file again. Rocky
* Fixed some info missing from the log file versus 221 stable. Rocky
* Fixed resizing window bigger than the video. It was not zoomed properly. Rocky

Oy, just noticed that resizing bigger than the stream resolution fails. I'll fix it and update.

Fixed. Please re-download rc11.

Standing proud on the rise, surveying all that lies before me. They call me vigilant, watchful. And I never stop watching!

Moving the main window around is like psychedelics...all that flashing! Get that right or dance the Moose Shuffle.

Picky picky, wicked and wee
Everything for me
and nothing for thee.

Nice poem, Curl. You are quite the creative one.

The flashing happens only when cropping is in effect. That should be fixable. I'll have a look.

I fixed the flashing when moving the main window. It now occurs only when moving the sliders in the Cropping Dialog and that is inevitable. The fix was slipped into rc11 so re-download to get it.

Now let's fix the flashing of the navigation bar when resizing.

Time to start thinking about releasing this sucka. Speak now or forever hold your peace.

Rocky wrote: ↑

Thu Dec 10, 2020 3:43 pm

Time to start thinking about releasing this sucka. Speak now or forever hold your peace.

Release the SUCKA!!!
(with apologies to "Release the KRAKEN" line from the movie Clash of the Titans))

I thought that was from our current election imbroglio. Thank you for the reference. I'll release tomorrow.

BTW, I started working on quantum physics again. Think I may have found something important. If true, it busts all the 2015 "loophole-free" experiments.

BTW, I started working on quantum physics again. Think I may have found something important. If true, it busts all the 2015 "loophole-free" experiments.

If anyone found a bug, it would be you. :belly-laugh:

I released it. A day late but not a dollar short.

Marking RESOLVED but feel free to follow up if needed.

Not bad for a little code optimization and clean up.
Just restructure everything, clean up bugs, publish a paper on quantum mechanics and go have dinner and a drink
Well done

Drinking red wine right now! I'm in Illannoy so can't go out for dinner. Have to do my own cooking. Discovered pan sauces for my steaks and lamb chops. Cognac, fresh thyme, and heavy cream. Use red wine for lamb and beef, white for fish, chicken, and pork. Shallots and mushrooms. Yummy!

We need to port DGDecodeNV to VS 2019 and then do an optimization. It's probably CUVID limited so there may not be much of a gain.

Found an antidote for my chlorine sensitivity that developed recently. Vitamin C cream. It neutralizes chlorine. Thank the Lord above, I can keep swimming.

Ported DGDecodeNV to VS 2019 and did some profiling. There is no opportunity for making any significant optimization. It is limited by CUVID and Avisynth+, not DGSource() code.

Rocky wrote: ↑

Thu Dec 10, 2020 5:53 pm

BTW, I started working on quantum physics again. Think I may have found something important. If true, it busts all the 2015 "loophole-free" experiments.

Goodness me, that sounds really exciting.
I look forward to hearing the for-dummies version of it, perhaps on the for-dummies yo*t*be or something
Cheers !

We'll see if it pans out. Never count your acorns before they sprout. But I'm excited about it too.

So now DGIndexNV is faster at demuxing than DGDemux! Sherman won't like that!

So now DGIndexNV is faster at demuxing than DGDemux! Sherman won't like that!

How much faster?

For one test:

DGIndexNV: 2:36
DGDemux: 3:03

That is significant

Yah. Thing is that Sherman was focused on CPU, and while he did a great job on that, the packet-based approach doesn't optimally use the file system caching. Let's see if they can be brought into line.

The information window no longer shows the word "Finished" in the info section

EDIT
Please stand by and let me check something

EDIT 2
When demuxing a BD the word "Finished" does show
When demuxing a 4K the word "Finished" does not show

That's very surprising. I'll check it out today.