Support forum for DG Tools

Hi Donald
.mp4 files may include the parameter "Rotation" (in degrees). After demuxing with DGdecNV this parameter gets lost, i.e. it is neither kept in the .dgi nor in the elementary video stream.
Would it be possible to include it at the end of the .dgi (similar to the resolution) ?
Mobile phone video clips can be taken in portrait or landscape (at 0, 90, 180, 270 degrees). Preserving the correct orientation is essential for re-encoding to avoid turned and flipped pictures (I think).

admin wrote: ↑

Fri Dec 14, 2018 2:24 pm

Don't push your luck.

gonca wrote: ↑

Fri Dec 14, 2018 3:29 pm

I just select three or four spots and compare the crop values

Me too. On really old restored movies, such as ones from Criterion, AR varies according to the found positives. It's really hard and time consuming but, hey, we are talking about masterpieces.

'Export to script' checkbox added to Cropping Tool in slipstream 164. Refer to the user manual for proper operation.

Sharc wrote: ↑

Sat Dec 15, 2018 4:47 am

Hi Donald
.mp4 files may include the parameter "Rotation" (in degrees). After demuxing with DGdecNV this parameter gets lost, i.e. it is neither kept in the .dgi nor in the elementary video stream.
Would it be possible to include it at the end of the .dgi (similar to the resolution) ?
Mobile phone video clips can be taken in portrait or landscape (at 0, 90, 180, 270 degrees). Preserving the correct orientation is essential for re-encoding to avoid turned and flipped pictures (I think).

You can't tell what the required rotation is just by looking at the video? I'm reluctant to add container specific data to the DGI file.

admin wrote: ↑

Mon Dec 17, 2018 11:36 am

Sharc wrote: ↑

Sat Dec 15, 2018 4:47 am

Hi Donald
.mp4 files may include the parameter "Rotation" (in degrees). After demuxing with DGdecNV this parameter gets lost, i.e. it is neither kept in the .dgi nor in the elementary video stream.
Would it be possible to include it at the end of the .dgi (similar to the resolution) ?
Mobile phone video clips can be taken in portrait or landscape (at 0, 90, 180, 270 degrees). Preserving the correct orientation is essential for re-encoding to avoid turned and flipped pictures (I think).

You can't tell what the required rotation is just by looking at the video? I'm reluctant to add container specific data to the DGI file.

Yes, I can always look at the video of course. However, when I want to automate the process it would be useful to have the the value automatically extracted.
I understand your reluctance though, so maybe I should better extract that value outside of DGindex; perhaps with MediaInfo or similar.

One little cosmetic: don't make the black borders appear again after closing the cropping window AND the script export is selected.

Guest 2 wrote: ↑

Tue Dec 18, 2018 8:39 am

One little cosmetic: don't make the black borders appear again after closing the cropping window AND the script export is selected.

Oops, I screwed up your post by hitting edit instead of quote. Sorry. Feel free to edit it back to the original.

Thanks for the new suggestion. I'll do it for next slipstream.

admin wrote: ↑

Tue Dec 18, 2018 10:41 am

Oops, I screwed up your post by hitting edit instead of quote. Sorry. Feel free to edit it back to the original.

There were only some congratulations for the good job you do every time.

Hint: add a "thank" button for posts we would like to thank. Dunno if technically possible for phpBB.

Hi. I haven't tested our latest release but may I ask how the cropping tool handle border % 2 != 0 ?
( Personally speaking, it should not be over-cropped? )

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().

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:

http://rationalqm.us/misc/CropRedesign.zip

Did a quick test.
Went item by item on your list and (no surprise) it worked as described

Thanks for the testing, gonca!

admin wrote: ↑

Mon Nov 26, 2018 8: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.

Addendum:

with regards to this:
viewtopic.php?f=8&t=677

COLORIMETRY 2 2 2
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.

sparktank, I'll see what I can do to make you a happy camper. Thanks for the suggestions.

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

Hi.

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

renols

Good point. I'll add this feature. Thanks for the suggestion.

Hehe, it already works. Everything is demuxed with -a. I need to update the user manual. Let me know if it is not working for you.

Upgrade to cropping tool
Would it be possible to have an auto setting where the tool scans the video and picks the crop values?
Reason:
Some movies (one of the latter Batman movies comes to mind) are filmed with different cameras and different resolutions, i.e. one can be 1980 x 1040 while the other camera could be 1980 x 800 and the footage will be mixed
Usage:
Tool would sample video at set points (hard-coded or user select-able number of points) and produce crop values based on the "largest" resolution

If it is too much bother don't worry about it
P.S.
How is the swim team doing?

gonca wrote: ↑

Tue Apr 23, 2019 3:48 pm

Upgrade to cropping tool
Would it be possible to have an auto setting where the tool scans the video

Similar to another topic I opened.

I updated the user manual to mention that -a demuxes all audio and subtitle streams and replaced it in the 175 slipstream. Slipstreamed a slipstream, LOL.

On the cropping tool requests I am still thinking it over.

Thank you for the update

P.S.
I want to see it when you update a slipstream to a slipstream that was slipstreamed to update it