[DDVT Tool] Dolby Vision RPU Demuxing / Injecting / Editing.

[von Suppé]

Originally Posted by -QfG-

how i understand the --crop function...

Source: 3840 x 2160 Letterboxed - Target 3840 x 1608 none Letterboxed = no crop switch needed

Can you tell me why no crop would be needed here? Please read from here: https://github.com/quietvoid/dovi_to...ent-1010640787
If I understand quietvoid correctly, the crop values don't matter to dovitool. It would set the size of letterbox bars to zero.
Which does make me wonder if "undercropping" would cause issues. With undercropping I mean cropping, but not entirely removing the black bars.

[-QfG-]

Wrong Informations. Correct answer here:
https://forum.doom9.org/showpost.php...6&postcount=45

[Ryushin]

Originally Posted by von Suppé

@Ryushin

Yes. When extracting RPU from letterboxed source (black bars are part of video), for injecting it back in a cropped version, the crop option is required.

Originally Posted by -QfG-

how i understand the --crop function:

Source: 3840 x 2160 Letterboxed - Target 3840 x 2160 Letterboxed = no crop switch needed
Source: 3840 x 2160 Letterboxed - Target 3840 x 1608 none Letterboxed = no crop switch needed
Source: 3840 x 2160 Letterboxed - Target 1920 x 1080 Letterboxed = no crop switch needed
Source: 3840 x 2160 Letterboxed - Target 1920 x 704 none Letterboxed = crop switch needed

LOL. So some say yes to and some say no cropping. Just to get more clarification I'll ask again Github so I can know what cropping is intended for.

[Boulder]

My assumption is that whenever the final result doesn't have any black borders, you use the cropping option for the RPU.

[quietvoid]

Originally Posted by Boulder

My assumption is that whenever the final result doesn't have any black borders, you use the cropping option for the RPU.

Yes that's correct.

[GZZ]

Originally Posted by quietvoid

Yes that's correct.

I makes sense, but how do you know how it crops the RPU?. I mean you will need to crop the end result just like the Crop function works on the RPU file. But as you dont set any crop resolution, how do you know how it cropped it ?

Ex.
Source UHD: 3840 x 2160 -> Crop RPU = Resolution ? - Reencoded and cropped movie: 3840 x 1680.

So what if the Cropped RPU has a resultion of 3840 x 1685 and the reencoded is 3840 x 1680, then its off by 5 pixel (not sure you can see that).

Wouldnt it be better if Dovi_tool took crop (Top, Bottom, Left, Right) values, so the RPU matches the Reencoded movie ?

[quietvoid]

Originally Posted by GZZ

I makes sense, but how do you know how it crops the RPU?. I mean you will need to crop the end result just like the Crop function works on the RPU file. But as you dont set any crop resolution, how do you know how it cropped it ?

Ex.
Source UHD: 3840 x 2160 -> Crop RPU = Resolution ? - Reencoded and cropped movie: 3840 x 1680.

So what if the Cropped RPU has a resultion of 3840 x 1685 and the reencoded is 3840 x 1680, then its off by 5 pixel (not sure you can see that).

The RPU contains active area offsets, which are set according to the size of the letterbox bars.
For example, a source file with resolution 3840x2160 might have an actual aspect ratio of 2.4 without letterbox bars, so the active area is 3840x1600.
In that case, the RPU has a L5 metadata entry with top and bottom offsets set to 280 pixels.
In playback, some devices would use this offset to apply tone mapping to the active area only.

If the RPU is "cropped", the 280 pixel offsets are set to zero. That indicates to the decoder that the video has no letterbox bars.
If the offsets were kept the same as the original, and the letterbox bars are not in the final video, then some players might overcrop the video on playback.

Originally Posted by GZZ

Wouldnt it be better if Dovi_tool took crop (Top, Bottom, Left, Right) values, so the RPU matches the Reencoded movie ?

You can already do this with the editor. The crop argument is only for convenience.

Say you have a final video of resolution 1920x1080 which contains letterbox bars. And the source is the example above, with actual active area of 3840x1600.
That means the offsets need to be halved to match the new resolution, giving us 140 pixels.

You could edit the RPU active area with this:

{
  "mode": 2,
  "active_area": {
    "presets": [
      {
        "id": 0,
        "left": 0,
        "right": 0,
        "top": 140,
        "bottom": 140
      }
    ],
    "edits": {
      "all": 0
    }
  }
}

[-QfG-]

Dolby_Vision_Tool_v0.34 Online:

-v0.34
*Added Options Menu (you can create Shell Extensions).
*Added info string to crop function.
*Fixed bad FPS settings by muxing in mkv.

[cool advertise]

Originally Posted by quietvoid

You could edit the RPU active area with this:

{
  "mode": 2,
  "active_area": {
    "presets": [
      {
        "id": 0,
        "left": 0,
        "right": 0,
        "top": 140,
        "bottom": 140
      }
    ],
    "edits": {
      "all": 0
    }
  }
}

@-QfG-
Since I am not able to edit the crop values of the rpu, it would be of great use if a future version of the -QfG- tool would allow, after enabling the crop, to set the crop values (left, right, top, bottom) before creating the rpu, in order to adapt it exactly to each encoding.
And I think the left and top crop values are positive, and what to do with the right and bottom crop values? Positive or negative?
Not sure but maybe they all have to be positive (if different from 0).
And finally hdr10plus_tool.exe contained in the -QfG- tool is obsolete (1.2.1), the new version has been released (1.2.2).
By the way, great job to both of you, quietvoid and -QfG-

[quietvoid]

Originally Posted by cool advertise

And I think the left and top crop values are positive, and what to do with the right and bottom crop values? Positive or negative?
Not sure but maybe they all have to be positive (if different from 0).

All active area offset values are positive.
They simply represent the size of the letterbox bars, in pixels.

[cool advertise]

OK, maybe now I understand.
So if I want to do an x265 encode and crop the top and bottom (or left and right) letterbox bars, dovi_tool allows this via the -c command or the CROP RPU "YES" option of the -QfG- tool. If you don't cut letterbox bars then don't use -c or use CROP RPU "NO" of the -QfG- tool.
There is no way or need to specify how many pixels these letterbox bars are via dovi_tool, if coding using crop.
The editor allows via a json configuration file, in case the encoding has letterbox bars and is therefore not cropped to specify the pixel size of these bars by skipping the default ones, or something like that.
I'm writing because I don't have a Dolby Vision TV, and I can't do tests, but I think I understand this.

[halls]

Hi!

Sorry, worng thread

[-QfG-]

v0.35 Online
-v0.35
*Added Active Area Editor in Injector.
*Updated hdr10plus_tool.exe to v1.2.2.

[halls]

Hi!

I know this isn't the specific thread, but i need a little help.

How can i extract the dolby vision meta datas to .xml format?

I have rpu.bin and .json files with using dovi_tool

I need this format /.xml/ for an program.

Thank You!

[quietvoid]

Originally Posted by halls

Hi!

I know this isn't the specific thread, but i need a little help.

How can i extract the dolby vision meta datas to .xml format?

I have rpu.bin and .json files with using dovi_tool

I need this format /.xml/ for an program.

Thank You!

You can't.

[cool advertise]

Originally Posted by -QfG-

v0.35 Online
-v0.35
*Added Active Area Editor in Injector.
*Updated hdr10plus_tool.exe to v1.2.2.

Perfect, but your injector tool is still missing one main function, namely injecting hdr10+ metadata into a hevc or mkv file.

[-QfG-]

This is a Dolby Vision Tool, not a HDR10+ Tool. . I will look to add HDR10+ Injector support on the next Update.

[GZZ]

Originally Posted by halls

Hi!

I know this isn't the specific thread, but i need a little help.

How can i extract the dolby vision meta datas to .xml format?

I have rpu.bin and .json files with using dovi_tool

I need this format /.xml/ for an program.

Thank You!

You can use a online converter to convert from JSON to XML.
It might work, it might not.
https://www.freeformatter.com/json-t...converter.html

[-QfG-]

-v0.35a
*Minor Bugfixes
*Changed colors of any strings

[halls]

Originally Posted by GZZ

You can use a online converter to convert from JSON to XML.
It might work, it might not.
https://www.freeformatter.com/json-t...converter.html

Hi!

Yes, i tried.

.JSON file is to big.....

But Thank You!