Feature Requests

Support forum for DGDecNV
Boulder
Moose Approved
Posts: 46
Joined: Fri Jul 29, 2011 7:22 am

Re: Feature Requests

Post by Boulder » Fri Jan 10, 2020 5:53 am

DmitryKz wrote:
Fri Jan 10, 2020 4: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.

DmitryKz
Posts: 10
Joined: Tue Nov 05, 2013 1:52 pm

Re: Feature Requests

Post by DmitryKz » Fri Jan 10, 2020 6:49 am

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

User avatar
Rocky
Moose Approved
Posts: 711
Joined: Fri Sep 06, 2019 12:57 pm

Re: Feature Requests

Post by Rocky » Fri Jan 10, 2020 8:16 am

Thank you for helping out, Boulder.

User avatar
tormento
Moose Approved
Posts: 310
Joined: Mon Sep 20, 2010 2:18 pm

Re: Feature Requests

Post by tormento » Sun Mar 29, 2020 4:18 am

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.

User avatar
Rocky
Moose Approved
Posts: 711
Joined: Fri Sep 06, 2019 12:57 pm

Re: Feature Requests

Post by Rocky » 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. 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.

Image

User avatar
tormento
Moose Approved
Posts: 310
Joined: Mon Sep 20, 2010 2:18 pm

Re: Feature Requests

Post by tormento » Sun Mar 29, 2020 8:28 am

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
Image
Given average male life expectation of 80, are you 67? :lol:

User avatar
Rocky
Moose Approved
Posts: 711
Joined: Fri Sep 06, 2019 12:57 pm

Re: Feature Requests

Post by Rocky » Sun Mar 29, 2020 8:33 am

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.

Boulder
Moose Approved
Posts: 46
Joined: Fri Jul 29, 2011 7:22 am

Re: Feature Requests

Post by Boulder » Fri Apr 03, 2020 1:30 pm

Your (sad) progress bar made me realise that I've already "known" you for 18 years :salute: 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.

User avatar
Rocky
Moose Approved
Posts: 711
Joined: Fri Sep 06, 2019 12:57 pm

Re: Feature Requests

Post by Rocky » 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.

Boulder
Moose Approved
Posts: 46
Joined: Fri Jul 29, 2011 7:22 am

Re: Feature Requests

Post by Boulder » Sat Apr 04, 2020 7:44 am

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.

Post Reply