Support forum for DG Tools

DmitryKz wrote: ↑

Fri Jan 10, 2020 3:37 am

Hello!
I did not find the answer in the documentation (maybe I was looking badly) - can DGIndexNV make an index file for each downloaded file, and not one common index file (.dgi) for all files in the list (i.e. make multiple *.DGIs)? I want to individually recode each file using AviSint, but I don’t understand how this can be done with DGIndexNV.
I've more than 400 *.ts files and make index files for each tooo long)))
I would be grateful for the answer.

You can use the command line client for that.
Open a command prompt, change to the directory where the files to index are and execute a commandline "for %f in (*.ts) do "path\to\your\dgindex.exe" -i "%f" -o "%~nf.dgi" -e -h"

It will create an index file for each .ts file.

Dear Boulder, many many thanks. This is exactly what I need.

Thank you for helping out, Boulder.

Just thinking out about my last indexing:

- add number of progressive, TFF, BFF at the end of dgi, beside FILM;
- scan images while indexing, giving some better parameter approximation for DGHDRtoSDR and other HDR functions (sliding window range?). At this point it could be incorporated into DGSource as it would be reading same DGI, having parameters for different ranges of video.

Your second suggestion is like an earlier one that asked to allow timeline navigation while the Crop dialog is active. I experimented with it but ran into technical difficulties that I did not have the time nor motivation to solve at the time. I keep it as an active request but it's a bit low on the priority list.

Same for your request for additional statistics, low priority I'm afraid. I'm not a spring chicken anymore and I zealously guard the time remaining on my progress bar of life.

Rocky wrote: ↑

Sun Mar 29, 2020 8:10 am

Your second suggestion is like an earlier one that asked to allow timeline navigation while the Crop dialog is active.

Sorry, I was not clear enough. My idea was, while indexing to dgi, mark the brightest and lowest of video (on range or frame base) and then feed HDR to SDR conversion with that results to have better parameters, dinamically.

Rocky wrote: ↑

Sun Mar 29, 2020 8:10 am

Given average male life expectation of 80, are you 67?

67.314... as you can see at the bottom left.

Sure, I understand your request. Again, it's a reasonable thing to ask for, but it's low priority.

Your (sad) progress bar made me realise that I've already "known" you for 18 years Where did the years go? Well, they took the colour of my beard with them but I look good in grey or white anyway.

To celebrate these years, I have a simple feature request:
Would it be possible to have the HDR-specific colorimetry and mastering information written in the template in x265 style with a macro? I don't know if you already determine the chroma location but that would be useful too. All these would then be easy to drop in the x265 commandline.

Time flies when you're having fun! Thank you for your enduring friendship.

I can do what you ask. Just give me the exact specifications as I am not familiar with x265 HDR syntax, etc.

Rocky wrote: ↑

Fri Apr 03, 2020 4:32 pm

Time flies when you're having fun! Thank you for your enduring friendship.

I can do what you ask. Just give me the exact specifications as I am not familiar with x265 HDR syntax, etc.

Thank you as well

Let's see..

COLORIMETRY 9 16 9 is transcoded directly as --colorprim 9 --transfer 16 --colormatrix 9.
There are the tables and respective values here: https://x265.readthedocs.io/en/default/ ... -colorprim but I think that they are the same what you already use.

MASTERING 13250 34500 7500 3000 34000 16000 15635 16450 40000000 50
would be
--master-display "G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(40000000,50)"

If the CLL info is there, for example LIGHT 552 190, it would be --max-cll "552,190" in x265. If the info is not there, it can be left out.

Chroma location is something I'm not sure of. If MediaInfo shows 4:2:0 (Type 2) for Chroma subsampling, you should use --chromaloc 2. All the UHD sources I've seen, had this set like that. Non-UHDs don't seem to have it so it can be left out.

Great. Thanks Boulder! May be a while but we'll get it done.

Boulder wrote: ↑

Fri Apr 03, 2020 1:30 pm

All these would then be easy to drop in the x265 commandline.

I don't understand that. How would that work, i.e., how would script contents get into a command line? You want to put it just as a comment and then you could cut and paste from that? If so, it may be easier to put another line in the DGI with the existing HDR lines.

Rocky wrote: ↑

Sun Apr 12, 2020 6:50 am

Boulder wrote: ↑

Fri Apr 03, 2020 1:30 pm

All these would then be easy to drop in the x265 commandline.

I don't understand that. How would that work, i.e., how would script contents get into a command line? You want to put it just as a comment and then you could cut and paste from that?

Exactly that. It's so much easier and error proof to copy-paste a string of text to my basic commandline skeleton than opening the dgi file (or using MediaInfo) and copying values from there one by one.

OK, how about adding a formatted command line to the DGI file right there with the existing HDR lines? You could copy and paste from that and it would be easier to implement. Or I could just replace the existing lines with the formatted version.

Can you please add command line flag -V or -version?
That would be great, thank you!

You can already right click on DGIndexNV.exe, select Properties/Details and get that information. Is that good enough?

Rocky wrote: ↑

Sun Apr 12, 2020 7:00 am

OK, how about adding a formatted command line to the DGI file right there with the existing HDR lines? You could copy and paste from that and it would be easier to implement. Or I could just replace the existing lines with the formatted version.

That would definitely work fine. While you're at it, would you mind adding the --frames xxxxx parameter as well? It's something I always add to the command line as it then gives the ETA when encoding.

Please let me know if this is working for you. The line is labeled X265_CL and it is at the bottom of the DGI file.

http://rationalqm.us/misc/DGIndexNV_Boulder.exe

Rocky wrote: ↑

Sun Apr 12, 2020 11:11 am

Please let me know if this is working for you. The line is labeled X265_CL and it is at the bottom of the DGI file.

http://rationalqm.us/misc/DGIndexNV_Boulder.exe

Thank you, works and looks good I'd remove all the extra whitespaces though, the input values are strings and I don't know if they are stripped by x265 or not. As such, better make it exactly the same format they show in their docs.

OK, will do. Thank you Boulder for this great feature request. Always looking to improve the DG user experience.

kebulek wrote: ↑

Sun Apr 12, 2020 7:11 am

Can you please add command line flag -V or -version?

Code: Select all

DGIndexNV.exe -version
->
DGIndexNV 2053.0.0.206 (64 bit) built on Apr 10 2020

That would be great, thank you!

Rocky wrote: ↑

Sun Apr 12, 2020 7:39 am

You can already right click on DGIndexNV.exe, select Properties/Details and get that information. Is that good enough?

I would like to display it in command line, so that is sadly not good enough for me.

Too bad, so sad.

I suppose there is no harm in it and it is pretty easy to do, so I'll do it. Thank you for the suggestion, kebulek.

Now looking at it, I can output to the console but it is asynchronous, so you'll get output like this:

-----
D:\Don\Programming\C++\DGDecNV\DGIndexNV\x64\Debug>dgindexnv -version

D:\Don\Programming\C++\DGDecNV\DGIndexNV\x64\Debug>DGIndexNV 2053.0.0.206 (64 bit)
-----

Is that acceptable, kebulek? The alternative is to make some com/exe hack (https://code.google.com/archive/p/dualsubsystem/) but I am disinclined to do that.

Yes, that is very acceptable! Thank you very much.