Page 31 of 34

Re: Feature Requests

Posted: Fri Jan 04, 2019 8:01 am
by admin
It's described in the user manuals, also discussed in threads here.

Bottom line: for determining Avisynth Crop() values, mod 2 is fine. For DGSource() cropping, currently nVidia supports mod 2 only for the right and bottom borders. If you try to select mod 2 for the top and left borders and export that to your script, you will get a warning popup. If you must have mod 2 on the top or left, then use Avisynth Crop().

Re: Feature Requests

Posted: Fri Jan 25, 2019 12:04 pm
by admin
I have another iteration on the cropping design and would appreciate your testing before I slipstream it. The changes are:

* Cropping tool now shows the mod values for the crop values.

* Cropping tool now has an OK button. Exit via OK to retain and use the configured cropping. Exit via the window's X button to discard any changes.

* The 'Export to script' checkbox is eliminated. You now control whether the values get exported by including or not including the __crop__ macro in your template. It's sensible to always include it because it will expand to nothing if cropping is not configured.

* The DGI file now includes a new line called DISP following the SIZ line. This gives the display area, which may differ from the coded size, e.g., when coded height 1088 should be displayed as 1080.

* The DGI file format version is bumped to 22.

* Note: if a stream has a display area smaller than the coded size (e.g., 1080 versus 1088) and cropping is not exported or manually included in DGSource(), then DGSource() will use the display area.

Here are the 64-bit binaries and docs:

Re: Feature Requests

Posted: Fri Jan 25, 2019 6:26 pm
by gonca
Did a quick test.
Went item by item on your list and (no surprise) it worked as described :hat:

Re: Feature Requests

Posted: Fri Jan 25, 2019 7:54 pm
by admin
Thanks for the testing, gonca!

Re: Feature Requests

Posted: Sun Jan 27, 2019 12:25 pm
by sparktank
admin wrote:
Mon Nov 26, 2018 9:48 am
DGI file formats and semantics are described in the DGIndexNV user manual. Is there something missing?
Back to this:

I was thinking like a quick index page or something.
A table sheet where these values are quickly mentioned.
Say, if I were to make a PNG of such values for such codecs (avc/hevc).

For the most part, I don't have to look up much references to such things as most content I deal with is progressive.

But in the case of SD content from DVD, I dig around my PC for a cheat sheet with such info before I go gallivanting around with QTGMC.
I know TV productions can have hybrid formats, but I can't trust my own notes, especially when I don't archive them online anywhere.

A cheat sheet would handy, in addition to the full documentation.

Re: Feature Requests

Posted: Sun Jan 27, 2019 12:28 pm
by sparktank

with regards to this:

in regards to the document (freely available), it's not always easy to remember where to find the document on my PC for the document to narrow down the (possible) values I might encounter.

So something among the lines of a quick reference to these without the document handy would be appreciated.

Re: Feature Requests

Posted: Sun Jan 27, 2019 1:14 pm
by admin
sparktank, I'll see what I can do to make you a happy camper. Thanks for the suggestions.

Re: Feature Requests

Posted: Fri Feb 15, 2019 12:29 am
by Boulder
I have two feature requests:

1) A resize calculator alongside the cropping tool. Currently I usually downscale UHD and HD sources to 1080p and 720p respectively and I need to open one m2ts file in the Avisynth script creator in MeGUI just to do the maths instead of getting all the necessary things out of one tool. Having the calculator in the indexer would make things much simpler. It wouldn't need to be anything too fancy.

2) Add a possibility to output the HDR related information in the Avisynth/Vapoursynth template to easily copy the information to the x265 command line. Currently I need to check things from the dgi file and translate it to the command line syntax.

Thanks in advance for even considering them :)

Re: Feature Requests

Posted: Fri Apr 19, 2019 6:53 am
by renols

I have a request for a new command line option.

Would it be possible to get an option that allows subs to be demuxed as well. I can now choose video and audio but not subs.

To be honest I am trying to replace eac3to in my workflow, because I am experiencing heavy slowdowns using eac3to, where it can take 20+ minutes to demux a bluray, whereas dgindexnv can do the same job in like 5 minutes.

If the option is already there please excuse me. But I can't see it in the command line reference in the help file.

I think that by now, dgindexnv can pretty much do all that eac3to can do when it comes to demuxing, and a great program just continues to get better :D


Re: Feature Requests

Posted: Fri Apr 19, 2019 5:46 pm
by admin
Good point. I'll add this feature. Thanks for the suggestion.