[DoVi_Scripts] Multi-Function Scripts for Dolby Vision processing and a lot more...

[ReciprocalUniverse]

Question:
Can dovi scripts directly make a RPU.BIN from a RPU.XML?

[Kuler087]

Yes, just plot the xml in 6-3 and it should output a rpu.bin

[ReciprocalUniverse]

Originally Posted by Kuler087

Yes, just plot the xml in 6-3 and it should output a rpu.bin

That's perfect, (I think). Couldn't I then with x265

--dolby-vision-profile 8.1 --dolby-vision-rpu filename.bin

...have x265 interleave rpu.bin at runtime instead of injecting it with DoVi tool later to save a step?

[Kuler087]

yes, you can do that but if you crop or downscale, you have to edit your RPU Level 5.

6-3 assume your video is 2160p.

[TDS]

Originally Posted by ReciprocalUniverse

That's perfect, (I think). Couldn't I then with x265

--dolby-vision-profile 8.1 --dolby-vision-rpu filename.bin

...have x265 interleave rpu.bin at runtime instead of injecting it with DoVi tool later to save a step?

I used to do that with RipBot, but because I need an mp4, and RipBot can't output x265 mp4's, it was of no use to me

[ReciprocalUniverse]

Originally Posted by Kuler087

yes, you can do that but if you crop or downscale, you have to edit your RPU Level 5.

6-3 assume your video is 2160p.

Video is from a camera, 7680 x 4320 59.94 fps

[Kuler087]

Originally Posted by ReciprocalUniverse

Video is from a camera, 7680 x 4320 59.94 fps

Then you will have to edit L5 to 8K or use dovi_tool to generate the rpu from XML

"%dovi_tool_path%" generate --xml %XML% --canvas-width %Width% --canvas-height %Height% --rpu-out "%TEMP%P8.RPU.bin"

[ReciprocalUniverse]

Sorry, not trying to be evasive, just substantively clear, in which case I may not be giving you as much information as you need to help me, so let me know.

[ReciprocalUniverse]

Originally Posted by Kuler087

Then you will have to edit L5 to 8K or use dovi_tool to generate the rpu from XML

"%dovi_tool_path%" generate --xml %XML% --canvas-width %Width% --canvas-height %Height% --rpu-out "%TEMP%P8.RPU.bin"

Thanks, L5 meaning profile 5.0, or Dolby level 5? Is L5 something else? Is L5 a call from the script?

I'm sorting in my mind your syntax, so that says dovi tool > XML > 7680 > 4320 > Profile_8 = RPU.bin? I would enter your string on the command line?

Really appreciate your patience with me, already a big help.

[Kuler087]

L5 = Level 5 = the active area of the image without black bars. Dolby Vision is designed to apply tone mapping only to the active area of the image. Incorrect L5 can result in over-cropping or tone mapping applied to the letterbox which could cause raised black.
You can edit L5 with DS workflow 1 or you can use dovi_tool.exe in cli and L5 will be set automatically and correctly according to your input resolution.

D:\DoVi_Scripts\tools\dovi_tool.exe generate --xml D:\DV.metadata.xml --canvas-width 7680 --canvas-height 4320 --rpu-out D:\rpu.output.bin


All of this doesn't matter if your video is 1.78 (no black bars) though.

[ReciprocalUniverse]

Is it less complicated, better or faster to inject? I don't have to do it a particular way. Here's what I did up to this point which worked for 4K but not 8K, I used Resolve to export uncompressed and a timeline.json from an HDR10 analysis, which I interleaved with x265. I muxed in my audio to mkv and got a playable HDR10+ file, then used DDVT_DEMUXER to make it a DV8.1 [BL+RPU] and with DDVT_MKVTOMP4 it became DV playable (in 4k). The same process didn't work for 8k.

I think I'd rather have the DV analysis than HDR10+ but didn't know how to do that with the DDVT scripts I started with. The object is to make a playable 7680x4320 59.94 fps DV compliant file.

[ReciprocalUniverse]

Originally Posted by Kuler087

L5 = Level 5 = the active area of the image without black bars. Dolby Vision is designed to apply tone mapping only to the active area of the image. Incorrect L5 can result in over-cropping or tone mapping applied to the letterbox which could cause raised black.
You can edit L5 with DS workflow 1 or you can use dovi_tool.exe in cli and L5 will be set automatically and correctly according to your input resolution.

D:\DoVi_Scripts\tools\dovi_tool.exe generate --xml D:\DV.metadata.xml --canvas-width 7680 --canvas-height 4320 --rpu-out D:\rpu.output.bin


All of this doesn't matter if your video is 1.78 (no black bars) though.

I am liking this idea!

[ReciprocalUniverse]

If I am understanding correctly, if my uncompressed 7680 x 4320 contained 160 pixel blackbars on top and bottom then:

D:\DoVi_Scripts\tools\dovi_tool.exe generate --xml D:\DV.metadata.xml --canvas-width 7680 --canvas-height 4000 --rpu-out D:\rpu.output.bin

No, ignore that, you already explained, two steps.

[Kuler087]

I muxed in my audio to mkv and got a playable HDR10+ file, then used DDVT_DEMUXER to make it a DV8.1 [BL+RPU] and with DDVT_MKVTOMP4 it became DV playable (in 4k). The same process didn't work for 8k.

I think I'd rather have the DV analysis than HDR10+ but didn't know how to do that with the DDVT scripts I started with. The object is to make a playable 7680x4320 59.94 fps DV compliant file.

Converting HDR10plus to DV is a bad idea. There's a reason my script workflow 3-2 says ''not recommended''. I don't know about DDVT scripts , never used it, and never will.

My scripts though, should work with 8K input. I just tried with the mp4 version in workflow 1 and it works. I don't have a 8K TV to test though

General
Complete name : D:\8K_DV.mp4
Format : mp43
Codec ID : mp43 (isom/mp43/dby1)
File size : 58.0 MiB
Duration : 12 s 555 ms
Overall bit rate : 38.8 Mb/s
Frame rate : 23.976 FPS
Encoded date : 2024-08-15 21:24:53 UTC
Tagged date : 2024-08-15 21:24:53 UTC

Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L6.1@High
HDR format : Dolby Vision, Version 1.0, Profile 8.0, dvhe.08.11, BL+RPU, no metadata compression / SMPTE ST 2086, Version HDR10, HDR10 compatible
Codec ID : dvhe
Codec ID/Info : High Efficiency Video Coding with Dolby Vision
Duration : 12 s 555 ms
Bit rate : 38.8 Mb/s
Width : 7 680 pixels
Height : 4 320 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0 (Type 2)
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.049
Stream size : 58.0 MiB (100%)
Default : Yes
Alternate group : 1
Encoded date : 2024-08-15 21:24:53 UTC
Tagged date : 2024-08-15 21:24:53 UTC
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : Display P3
Mastering display luminance : min: 0.0001 cd/m2, max: 1000 cd/m2
Maximum Content Light Level : 192 cd/m2
Maximum Frame-Average Light Level : 82 cd/m2
Codec configuration box : hvcC+dvcC

D:\DoVi_Scripts\tools\dovi_tool.exe generate --xml D:\DV.metadata.xml --canvas-width 7680 --canvas-height 4000 --rpu-out D:\rpu.output.bin

No, ignore that, you already explained, two steps.

yeah don't do that. canvas must be the input resolution and dovi_tool will set L5 automatically

[ReciprocalUniverse]

I got the *.bin from dovi-tool. Gosh that was simple! Now to test to see if it works.

Thanks for all your help so far. I'll be back very soon.

[Kuler087]

DS MP4 version + workflow 1 would be even simpler. Input 1: video source, Input 2: XML source and the script will read the input resolution, generate the rpu, inject and mux to MP4

[ReciprocalUniverse]

Originally Posted by Kuler087

DS MP4 version + workflow 1 would be even simpler. Input 1: video source, Input 2: XML source and the script will read the input resolution, generate the rpu, inject and mux to MP4

The issue is the learning curve for getting the scripts set up. I'd rather work from the command line. That created a problem too. Although dovi-tools converted the xml to bin, and x265 says it was successful in muxing it, the mediainfo isn't reporting dolby metadata, just HDR10 2086.

[Kuler087]

The issue is the learning curve for getting the scripts set up

For workflow 1, theres nothing to install. It should work out of the box and there's an installation tutorial on the first page.

Although dovi-tools converted the xml to bin, and x265 says it was successful in muxing it, the mediainfo isn't reporting dolby metadata, just HDR10 2086.

raw hevc stream will not show DV metadata, you have to mux it.

[ReciprocalUniverse]

Originally Posted by Kuler087

For workflow 1, theres nothing to install. It should work out of the box and there's an installation tutorial on the first page.


raw hevc stream will not show DV metadata, you have to mux it.

I had muxed the x265 raw hevc into mkv with mkvtoolnix, but no DV metadata was indicated in the mkv.

I am willing to try workflow 1, but I don't know what it is or where to find it. I had already downloaded the toolpack and found Dovi_tool.exe, but all the other stuff, of which half of it at least I already have, and the other half I loathe downloading and installing. I downloaded the Dolby Professional set. Your instructions say I MUST download python, avisynth + 64b, visual C++, lav filters, vapoursynth, madVR.

I played the YT tutorial, I love the Canadians, I worked for them for 11 years, but I don't know French.

[TDS]

Originally Posted by ReciprocalUniverse

I had muxed the x265 raw hevc into mkv with mkvtoolnix, but no DV metadata was indicated in the mkv.

I am willing to try workflow 1, but I don't know what it is or where to find it. I had already downloaded the toolpack and found Dovi_tool.exe, but all the other stuff, of which half of it at least I already have, and the other half I loathe downloading and installing. I downloaded the Dolby Professional set. Your instructions say I MUST download python, avisynth + 64b, visual C++, lav filters, vapoursynth, madVR.

I played the YT tutorial, I love the Canadians, I worked for them for 11 years, but I don't know French.

Admittedly there are several dependencies to be installed, etc, etc, but once that's done, you have FULL use of any workflow.