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

[ReciprocalUniverse]

It is wonderful you are active and involved here and with Resolve. I hope you can help me with some answers. I can't afford the Dolby license for Resolve Studio but I can run the HDR10+ analysis and encode with x265 to get a compatible HDR10+ file. Running some of the DDVT scripts I made it into a playable DV Profile 8.1 (BL + RPU).

1.) With DV, there is a collection of available target RPU's. With HDR10+, you don't get that. So when a script converts HDR10+ json metadata to DV RPU, what exactly is the tone mapping target you end up with? 100 nit? 200 nit? Something else?
2.) If I upload an HDR10 to YouTube, they render a version in SDR. If the file is not streamed, it needs an HDR and SDR copy. A dual layer DV (BL + EL + RPU) would not be of help for a player not supporting DV. However, if it was supporting of DV what would be the point of an SDR layer if the player/display can already do the HDR layer? Part of my question then relates to, what is the special relevance of tone mapping to the 100 nit SDR level for a DV device?

As an aside, I don't think it's visually essential to encode a jpeg2000 sequence or open exr for the source to HEVC. DNxHR or Prores is fine.

**************************************************

Unrelated to the above questions, it came up in the conversation about doing trims on individual frames, and the amount of work involved. I would add that outside of the DV realm, grading a scene clip doesn't have to always involve every single frame or grading just one frame. Example, the bride is wearing a white dress in the bright sun, and when she is followed by the camera into a dark hallway, the scene darkens, the scene ends up with very different exposure than it started with. Another example is an unmanned camera on a tripod filming an outdoor wedding ceremony. Suddenly the sky darkens as clouds move overhead. The scene again ends up with very different exposure than it started with. In my opinion, these are not the intended situations for frame by frame dynamic metadata. The approach I take is to use Resolve keyframes to 'transition' between the changing conditions, averaging across a sequence of frames. Frame by frame would take too long. Carry on and thanks again!

[Kuler087]

I can't afford the Dolby license for Resolve Studio
DV is free for any user to use. Only the manual level 8 or 2 artistic trims require a license.

With HDR10+, you don't get that. So when a script converts HDR10+ json metadata to DV RPU, what exactly is the tone mapping target you end up with? 100 nit? 200 nit? Something else?
I don't know much about HDR10plus but in DV only the trim passes have targets which are used to tonemap the image more accurately according to the colorist's shot-by-shot adjustments.
HDR10plus doesn't have trim passes, so it most likely works like DV without trims and uses the TV internal target brightness to apply tone mapping according to the metadata.

A dual layer DV (BL + EL + RPU) would not be of help for a player not supporting DV.
The metadata in DV can be used on any display, HDR10 and SDR. This is done by forcing the player to decode the image + metadata (LLDV) and mapping the tone according to the EDID target brightness.

what would be the point of an SDR layer if the player/display can already do the HDR layer?
The 100nits SDR DV trim pass is extrapolated and can tone map to any target between 100-10 000nits. The point of doing the SDR trim pass(maximum compression an HDR grade can get) is that the colorist can control the tone mapping regardless of the display capabilities.

After grading the HDR master shot by shot, they do the automated DV metadata generation and then they monitor shot by shot(again) the mapping to different targets (100-600-1000-2000). They make adjustments to the trims target if they are not satisfied by Dolby default mapping.
They almost never do more than a 100nits trim since it's the lowest point of tone mapping possible but I've seen a couple of bluray that cancel the 100-600-1000nits interpolation(They do the 100nits trim and reset to 0 the 600nits-1000nits values which create a blank 600 trim). This is useful when they want to be more aggressive with the 100nits trim that will be used for the SDR bluray delivery without affecting the 600-1000 target interpolation mapping.




Unrelated to the above questions, it came up in the conversation about doing trims on individual frames, and the amount of work involved.
I've checked pretty much all the DV releases on this planet and only one time I've seen frame by frame metadata and it was for the Amazon show Jack Ryan. But they did not do any trim pass. I cant imagine how long it would take to grade a movie frame by frame.

[ReciprocalUniverse]

DV is free for any user to use. Only the manual level 8 or 2 artistic trims require a license.

Yes, the DV trim panels are enabled with a license only. Without a license Resolve can still export an RPU.XML from an automated analysis of clips but not a DV compliant HEVC file. Perhaps not even with the license can you export compliant HEVC? Are you saying Resolve's licensed involvement stops with enabling the trim panel and generating an RPU.XML, but not generating a RPU.BIN or HEVC? I had assumed previously that with the license you could export compliant, playable DV HEVC files, but that may have been wrong.


I don't know much about HDR10plus but in DV only the trim passes have targets which are used to tonemap the image more accurately according to the colorist's shot-by-shot adjustments.
HDR10plus doesn't have trim passes, so it most likely works like DV without trims and uses the TV internal target brightness to apply tone mapping according to the metadata.

The Resolve DV display targets can be selected without the DV license but not the trim panel. For HDR10+ there are no selectable display targets, so my question to you was what then does it use which you didn't have the answer for, which is okay. I assume it really does not matter because the HDR10+ processing inside the display will use it appropriately.

The HDR10+ trim panel was enabled in Resolve until V.17 when it was disabled at the request of Samsung. Otherwise, the process workflow of running an automated analysis is identical. A json sidecar file is generated with dynamic metadata that can be interleaved in x265 with the HDR10 BL to produce a playable HDR10+ HEVC file. The x265 process for DV is similar except the RPU has to be in binary form, requiring the extra step from CMD tools (or yours) to convert the RPU.XML to binary.

Okay so the one, 100 nit target level is potentially sufficient to accommodate any DV display.

I've checked pretty much all the DV releases on this planet and only one time I've seen frame by frame metadata and it was for the Amazon show Jack Ryan. But they did not do any trim pass. I cant imagine how long it would take to grade a movie frame by frame.

Ignore my prior remarks about frame by frame, dynamic metadata as with Profile 8.4, it was a misunderstanding by me.

In summary, what this all boils down to for me is that HDR10+ only has intended application for Samsung tv's, and if you want to make playable HEVC files for DV tv's with Resolve, you will still need the DoVi tools whether you have a licensed Resolve copy or not. Have I got that right?

[ReciprocalUniverse]

Here's my final question, thanks for your patience!

Using the DoVi scripts and x265 is it possible to make a profile 8.4 playable HEVC from Resolve with no DV license?

I hope I'm clear about that. I'm not talking about manually doing a sequence of trim passes. I'm talking about automatic, frame by frame bitstream insertion of metadata for every single frame, like an i-Phone can do, with no trim passes.

[Kuler087]

Without a license Resolve can still export an RPU.XML from an automated analysis of clips but not a DV compliant HEVC file. Perhaps not even with the license can you export compliant HEVC?
Resolve hevc encoding sucks anyway so just export the XML and inject it with dovi_scripts workflow 1 but yes, a DV license will enable the P5/P8 hevc encoding in resolve delivery page. The best option is to deliver to a lossless codec and do the encoding with x265.exe and inject the xml/rpu.
FYI If you know how to change your edid, you can use this custom one (https://mega.nz/file/8DNC2D6J#aB8reR8iUSMGLXW7dqLUbEPsV3z3OSuj7n5wJkNOs84) that will allow P5/P8 encoding without a DV license.

Resolve P5/P8 encoding though, will ignore your existing shot by shot analysis and create new frame by frame metadata.

or HDR10+ there are no selectable display targets, so my question to you was what then does it use which you didn't have the answer for, which is okay. I assume it really does not matter because the HDR10+ processing inside the display will use it appropriately.

The HDR10+ trim panel was enabled in Resolve until V.17 when it was disabled at the request of Samsung. Otherwise, the process workflow of running an automated analysis is identical.

I'm no expert with HDR10plus but I think the process is 100% automated and is never monitored unlike DV trims creation. So there's no target AFAIK, it just creates shot by shot brightness metadata but I could be wrong.

Using the DoVi scripts and x265 is it possible to make a profile 8.4 playable HEVC from Resolve with no DV license?

My script cannot encode the HLG base layer but if you input any XML with an HLG video in workflow 1, the XML file will be converted to an 8.4 RPU and injected into your HLG BL. I've done it many times with BBC TV shows.

EG. You convert the HLG file to HDR10 prores with workflow 8-2-3, generate an XML as usual, and inject it with Workflow 1.

[ReciprocalUniverse]

Resolve hevc encoding sucks anyway so just export the XML and inject it with dovi_scripts workflow 1 but yes, a DV license will enable the P5/P8 hevc encoding in resolve delivery page. The best option is to deliver to a lossless codec and do the encoding with x265.exe and inject the xml/rpu.
FYI If you know how to change your edid, you can use this custom one (https://mega.nz/file/8DNC2D6J#aB8reR8iUSMGLXW7dqLUbEPsV3z3OSuj7n5wJkNOs84) that will allow P5/P8 encoding without a DV license.

Resolve P5/P8 encoding though, will ignore your existing shot by shot analysis and create new frame by frame metadata.



I've tried lossless to x265 for P5.0 but without RPU got no DV. Would injecting shot by shot rpu.xml with DoVi tools give me compliant P5.0 DV?

[Kuler087]

P5 encoding from scratch requires the proprietary Dolby engine.

You can do that with Workflow 8-2-6 but you first have to configure your path to DEE.exe. Input can be prores mov, jpeg-2000 mxf, hevc DVP8/7, HDR10, HLG.
For mov, mxf, HDR10 and HLG inputs, you must provide an XML and Dolby default encoding scripts produce garbage 2-pass hevc encoding so you should modify it as I say in workflow 8-2-6 to allow custom settings and CRF encoding.

Also there's a bug in the latest version of dovi_scripts with mov and prores if you don't crop, so get the latest beta. (https://drive.google.com/file/d/128gq8aDUTKA_aT7SQsM9dkjA1EP1sosR/view?usp=drive_link)

[guest]

P5 encoding from scratch requires the proprietary Dolby engine.

You can do that with Workflow 8-2-6 but you first have to configure your path to DEE.exe. Input can be prores mov, jpeg-2000 mxf, hevc DVP8/7, HDR10, HLG.
For mov, mxf, HDR10 and HLG inputs, you must provide an XML and Dolby default encoding scripts produce garbage 2-pass hevc encoding so you should modify it as I say in workflow 8-2-6 to allow custom settings and CRF encoding.

Also there's a bug in the latest version of dovi_scripts with mov and prores if you don't crop, so get the latest beta. (https://drive.google.com/file/d/128gq8aDUTKA_aT7SQsM9dkjA1EP1sosR/view?usp=drive_link)

There are quite a few things you "need" DEE for with DS, BUT, where to get it, is the question.

Shame there's a bug in the latest release, I only just got it the other day, so I guess 3.0.2 might be out soon'ish...

[Kuler087]

There are quite a few things you "need" DEE for with DS
not really... only workflow 8-2-6 8-2-5 and 8-1-3

Shame there's a bug in the latest release, I only just got it the other day, so I guess 3.0.2 might be out soon'ish...
No, not soon. Nothing new and its a minor bug only in 8-2-6 and only when you don't crop and only with prores jpeg-2000 input.

[guest]

not really... only workflow 8-2-6 8-2-5 and 8-1-3

Maybe "need" wasn't the right word, it's a "nice to have", and adds extra functionality to the app :)


No, not soon. Nothing new and its a minor bug only in 8-2-6 and only when you don't crop and only with prores jpeg-2000 input.

OK, well that IS a fairly particular "bug".

All good, :thanks:

Your 300th post :)

[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]

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.

[guest]

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]

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]

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]

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]

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]

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]

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.

[guest]

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.

[ReciprocalUniverse]

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

I appreciate that, but I am one functional bin file away from finishing this.

[Kuler087]

all the things to install are for the very technical stuff. If you just want to inject and mux to mp4, workflow 1 doesn't need any of these softwares.

Sure my Windows is in French, but the instructions are in English and pretty easy to follow if you dont install the extra software and just use workflow 1:

Create a folder
put the tools folder in it
put the bat file(mkv mp4 or ts) you want to use in it
click on the bat file
select a workflow
drag and drop input 1, 2 and press enter. You can skip all the user prompts by pressing enter.

or

just drag and drop a file on the bat file, then the metadata and press enter.

[ReciprocalUniverse]

I love ALL Canadians, our neighbors and friends to the north, anything that's mine is yours except Lord Stanley's Cup.

I can handle that workflow I think. I will try.
:-)

[ReciprocalUniverse]

My 8K Samsung as everyone knows doesn't do Dolby Vision, but the 8K-hevc.mkv before injection plays perfectly in HDR10 on everything,
but after the RPU.XML is input to workflow 1,the output MP4 file plays in HDR10 in the Windows Media Player, but only haltingly in MPC-HC,
and not at all from the tv's own media player. Isn't DV P8.1 backward HDR10 compatible? The metadata seems okay.

General
Complete name : C:\Users\Monstro\Videos\Captures\8K_Sunset_DV.mp4
Format : MPEG-4
Format profile : Base Media / Version 2
Codec ID : mp42 (mp42/dby1/isom)
File size : 119 MiB
Duration : 11 s 542 ms
Overall bit rate mode : Variable
Overall bit rate : 86.3 Mb/s
Frame rate : 59.940 FPS
Encoded date : 2024-08-16 03:35:16 UTC
Tagged date : 2024-08-16 03:35:16 UTC

Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L6.1@Main
HDR format : Dolby Vision, Version 1.0, dvhe.08.12, BL+RPU, HDR10 compatible / SMPTE ST 2086, HDR10 compatible
Codec ID : dvhe
Codec ID/Info : High Efficiency Video Coding with Dolby Vision
Duration : 11 s 528 ms
Bit rate : 86.2 Mb/s
Width : 7 680 pixels
Height : 4 320 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 59.940 (60000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.043
Stream size : 118 MiB (100%)
Writing library : x265 3.6+35-dd594f59d:[Windows][MSVC 1940][64 bit] 10bit
Encoding settings : cpuid=1111039 / frame-threads=3 / numa-pools=12 / wpp / no-pmode / no-pme / no-psnr / no-ssim / log-level=2 / input-csp=1 / input-res=7680x4320 / interlace=0 / total-frames=0 / level-idc=0 / high-tier=1 / uhd-bd=0 / ref=3 / no-allow-non-conformance / repeat-headers / annexb / no-aud / no-eob / no-eos / no-hrd / info / hash=0 / temporal-layers=0 / open-gop / min-keyint=25 / keyint=250 / gop-lookahead=0 / bframes=4 / b-adapt=2 / b-pyramid / bframe-bias=0 / rc-lookahead=20 / lookahead-slices=8 / scenecut=40 / no-hist-scenecut / radl=0 / no-splice / no-intra-refresh / ctu=64 / min-cu-size=8 / no-rect / no-amp / max-tu-size=32 / tu-inter-depth=1 / tu-intra-depth=1 / limit-tu=0 / rdoq-level=0 / dynamic-rd=0.00 / no-ssim-rd / signhide / no-tskip / nr-intra=0 / nr-inter=0 / no-constrained-intra / strong-intra-smoothing / max-merge=3 / limit-refs=1 / no-limit-modes / me=1 / subme=2 / merange=57 / temporal-mvp / no-frame-dup / no-hme / weightp / no-weightb / no-analyze-src-pics / no-deblock / no-sao / no-sao-non-deblock / rd=3 / selective-sao=0 / early-skip / rskip / no-fast-intra / no-tskip-fast / no-cu-lossless / b-intra / no-splitrd-skip / rdpenalty=0 / psy-rd=2.00 / psy-rdoq=0.00 / no-rd-refine / no-lossless / cbqpoffs=-3 / crqpoffs=-3 / rc=cbr / bitrate=85000 / qcomp=0.60 / qpstep=4 / stats-write=0 / stats-read=0 / vbv-maxrate=85000 / vbv-bufsize=70000 / vbv-init=0.9 / min-vbv-fullness=50.0 / max-vbv-fullness=80.0 / ipratio=1.40 / pbratio=1.30 / aq-mode=2 / aq-strength=1.00 / cutree / zone-count=0 / no-strict-cbr / qg-size=32 / no-rc-grain / qpmax=69 / qpmin=0 / no-const-vbv / sar=1 / overscan=0 / videoformat=5 / range=0 / colorprim=9 / transfer=16 / colormatrix=9 / chromaloc=0 / display-window=0 / master-display=G(13574,32227)B(7617,2686)R(33496,15723)WP(14063,14209)L(10000000,300) / cll=985,27 / min-luma=0 / max-luma=1023 / log2-max-poc-lsb=8 / vui-timing-info / vui-hrd-info / slices=1 / no-opt-qp-pps / no-opt-ref-list-length-pps / no-multi-pass-opt-rps / scenecut-bias=0.05 / no-opt-cu-delta-qp / no-aq-motion / hdr10 / no-hdr10-opt / no-dhdr10-opt / no-idr-recovery-sei / analysis-reuse-level=0 / analysis-save-reuse-level=0 / analysis-load-reuse-level=0 / scale-factor=0 / refine-intra=0 / refine-inter=0 / refine-mv=1 / refine-ctu-distortion=0 / no-limit-sao / ctu-info=0 / no-lowpass-dct / refine-analysis-type=0 / copy-pic=1 / max-ausize-factor=1.0 / no-dynamic-refine / no-single-sei / no-hevc-aq / no-svt / no-field / qp-adaptation-range=1.00 / scenecut-aware-qp=0conformance-window-offsets / right=0 / bottom=0 / decoder-max-rate=0 / no-vbv-live-multi-pass / no-mcstf / no-sbrc
Default : Yes
Alternate group : 1
Encoded date : 2024-08-16 03:35:16 UTC
Tagged date : 2024-08-16 03:35:16 UTC
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : R: x=0.669920 y=0.314460, G: x=0.271480 y=0.644540, B: x=0.152340 y=0.053720, White point: x=0.281260 y=0.284180
Mastering display luminance : min: 0.0300 cd/m2, max: 1000 cd/m2
Maximum Content Light Level : 985 cd/m2
Maximum Frame-Average Light Level : 27 cd/m2
Codec configuration box : hvcC+dvcC

Audio
ID : 2
Format : AAC LC
Format/Info : Advanced Audio Codec Low Complexity
Codec ID : mp4a-40-2
Duration : 11 s 542 ms
Bit rate mode : Variable
Bit rate : 192 kb/s
Maximum bit rate : 198 kb/s
Channel(s) : 2 channels
Channel layout : L R
Sampling rate : 48.0 kHz
Frame rate : 46.875 FPS (1024 SPF)
Compression mode : Lossy
Stream size : 275 KiB (0%)
Default : Yes
Alternate group : 2
Encoded date : 2024-08-16 03:35:16 UTC
Tagged date : 2024-08-16 03:35:16 UTC

[guest]

My 8K Samsung as everyone knows doesn't do Dolby Vision, but the 8K-hevc.mkv before injection plays perfectly in HDR10 on everything,
but after the RPU.XML is input to workflow 1,the output MP4 file plays in HDR10 in the Windows Media Player, but only haltingly in MPC-HC,
and not at all from the tv's own media player. Isn't DV P8.1 backward HDR10 compatible? The metadata seems okay.

I'm sure someone will correct me if I'm wrong, but from what I understand the RPU.bin is only for Dolby Vision.

So why are you injecting it into a file that plays properly on your Samsung ?? when you clearly know that your Samsung does not support DV anyway.

And, if the 8K .mkv plays, why convert it to .mp4, when you probably don't need to ??

And where did this come from:- dvhe.08.12

[ReciprocalUniverse]

I'm sure someone will correct me if I'm wrong, but from what I understand the RPU.bin is only for Dolby Vision.

So why are you injecting it into a file that plays properly on your Samsung ?? when you clearly know that your Samsung does not support DV anyway.

And, if the 8K .mkv plays, why convert it to .mp4, when you probably don't need to ??

And where did this come from:- dvhe.08.12

Your point about RPU.bin specific to Dolby Vision is true but profile 8 is backward compliant to the HDR10 base layer, so anything should play it, without RPU metadata of course.

You're right, I can play 8K HDR10 without DV but I have a pal, we are both shooting Nikon Z8, 8K 60fps, he has an LG 8K model with DV and we want to see if it's possible to make 8K Dolby Vision. I'm also doing 8k HDR10+. My Samsung can play that, his LG cannot, we want to compare these, so enough, we have our reasons, no one is harmed.

I have been making HDR10 videos since 2014, and one of them you've probably seen because it played around the globe in 2015 in every Magnolia HiFi showroom on Sony Z9D demo loops. I have one of the very first HDR videos of any kind on YouTube, within the first week or 10 days of the HDR service being offered. I have graded videos in HDR internationally with credits. So back off, friend! Let's be positive.

As for where dvhe.08.12 came from, that probably means profile 8, level 12, level 12 is for 7680 x 4320 up to 60 fps. It is not a parameter set by the user but is reported by x265. I also saw it reported at 08.0C, which is the hex representation for P08 L12.

[guest]

Your point about RPU.bin specific to Dolby Vision is true but profile 8 is backward compliant to the HDR10 base layer, so anything should play it, without RPU metadata of course.

You're right, I can play 8K HDR10 without DV but I have a pal, we are both shooting Nikon Z8, 8K 60fps, he has an LG 8K model with DV and we want to see if it's possible to make 8K Dolby Vision. I'm also doing 8k HDR10+. My Samsung can play that, his LG cannot, we want to compare these, so enough, we have our reasons, no one is harmed.

Interesting, OK, AFAIK, LG TV's will ONLY play DV from .mp4, .m2ts or .ts.

Up until recently (a couple of months) I had a 2018 LG 4K 55" TV, that would only play DV (using this great app), when using the "old" version of the mp4 muxer, but then that TV died, and I now have an LG C4 65", and it seems to work OK with both the "old" & "new" mp4 muxer's

Sux for you, that you have a Samsung.

I have been making HDR10 videos since 2014, and one of them you've probably seen because it played around the globe in 2015 in every Magnolia HiFi showroom on Sony Z9D demo loops. I have one of the very first HDR videos of any kind on YouTube, within the first week or 10 days of the HDR service being offered. I have graded videos in HDR internationally with credits. So back off, friend! Let's be positive.

A little bit aggressive at the end, not sure where that came from, but kudos to your self promotion, and no I wouldn't have seen that, and where's Magnolia HiFi ???, I'm in Australia !!

As for where dvhe.08.12 came from, that probably means profile 8, level 12, level 12 is for 7680 x 4320 up to 60 fps. It is not a parameter set by the user but is reported by x265. I also saw it reported at 08.0C, which is the hex representation for P08 L12.

That explains that too, only doing 4K here.

[ReciprocalUniverse]

A little bit aggressive at the end, not sure where that came from, but kudos to your self promotion, and no I wouldn't have seen that, and where's Magnolia HiFi ???, I'm in Australia !!



I'm a fan of your country and a customer of Australia's Blackmagic Design and Grant Petty, and own a few cameras including the Ursa Mini Pro 12K, other stuff too. Magnolia HiFi's were a department of the higher end Best Buy retail stores.

I think I have a working 8k DV file. My pal is going to test it tomorrow. Fingers crossed. I'll report the findings as soon as I know, and thanks to everyone for the help.

[ReciprocalUniverse]

Results are in for the LG Z3, 8K Dolby Vision OLED television, and they are a no-go for 8K-60 fps DV playability. I don't think there is anything wrong with these 8K-60 files, which you can download from my Google Drive account to do as you wish, inspect them for metadata, play them, share them, I don't care. They were shot with the Nikon Z8 in 8K60 NRaw/NLog, graded in DaVinci Resolve Studio 19.0B, Dolby Vision DV dvhe.08.12, HEVC based, CMv4.0, XML version 5.1.0 profile 8.1 Level 12 for 7680x4320 at 60 fps.

I tried (3) methods to get them to play.

1.) Workflow 1 in DoVi_Scripts method as described by Kuler087: https://drive.google.com/file/d/1IZUaMXnINCEHWOnoxsfhVXlntOU2DUnK/view?usp=sharing
2.) XML.BIN from Dovi_tool interleaved in x265: https://drive.google.com/file/d/1wz2Bg3sTAYRF5K9g46kakLkwwji1xMAH/view?usp=sharing
3.) Method 2 file RPU injected with DDVT_DEMUXER: https://drive.google.com/file/d/142IR3r96pERxclXxFTdIRTiv8Hpn-64a/view?usp=sharing

All 3 methods result in playable HDR10 files on both Samsung 8K and LG Z3, but were not playable in DV on Z3. The same clip encoded in 4K does play in DV on Z3 and my Hisense U8. Again, I don't think anything is wrong with the files, my judgement is the Z3 does not support dvhe.08.12. I am only aware of one other possible DV compliant 8K-60-fps television, The Sony Z9K. Maybe we'll get around to that one.

[ReciprocalUniverse]

I'm having a hard time with this notion of the LG Z3 not being DV compliant at 8K/60. I'm going to make one more shot at DV by dropping the bitrate to 60 Mbps, down from 85 Mbps, before pronouncing the Samsung 8K king since it is able to support 8K/60 HDR10+ streamed and USB flash drive.

[Kuler087]

Please, try these: https://drive.google.com/drive/folders/1JFepTfCgk3jGK8N-3Qq-ch4N5H3ZWBGM?usp=sharing

[guest]

Please, try these: https://drive.google.com/drive/folders/1JFepTfCgk3jGK8N-3Qq-ch4N5H3ZWBGM?usp=sharing

I thought I'd try a couple of these, but of course, they wouldn't play, as they are 8K after all.

But one thing I did notice, these are dvhe.08.11, not dvhe.08.12...

And also the Codec ID was either, hev1, hvc1 or dvhe depending on the mp4 muxer being used.

Anyway, I guess we'll have to wait for a reply, after they've tested them.

[Kuler087]

dvhe.08.11, not dvhe.08.12...

different framerate

they wouldn't play, as they are 8K after all.
They are all working(LLDV) correctly on Windows Energy player (https://apps.microsoft.com/detail/9p9zh5fl1bfk?hl=en-US&gl=US) + DV extension (https://apps.microsoft.com/detail/9pltg1lwphlf?activetab=pivot%3Aregionofsystemrequirementstab&hl=en-us&gl=US).

hev1, hvc1 or dvhe
hev1 = latest mp4muxer which strangely doesn't work on my Win11 PC but works fine on my Win10 PC.
dvhe= old mp4muxer
hvc1= Resolve and mp4box

[guest]

They are all working(LLDV) correctly on Windows Energy player (https://apps.microsoft.com/detail/9p9zh5fl1bfk?hl=en-US&gl=US) + DV extension (https://apps.microsoft.com/detail/9pltg1lwphlf?activetab=pivot%3Aregionofsystemrequirementstab&hl=en-us&gl=US).

I should have mentioned that I tried them on my LG C4....they do play with PotPlayer on my little laptop.

[Kuler087]

they do play with PotPlayer on my little laptop.
yes of course, but without decoding the DV metadata. The player I'm talking about processes the metadata(P5-P8-P7).

[ReciprocalUniverse]

Kuler087, your 8K hybrid "p8.1.HDR10plus.8K DS_NEW_mp4box.mp4" played perfectly in HDR10+ on my Samsung 8K, in 7680x4320 - 23.98 fps.

The 4000 nit grade of the Yellowstone Park clipped in HDR10 but tone mapped beautifully in HDR10+. I'll try the others soon.

[ReciprocalUniverse]

Update:

"p8.1.HDR10plus.8K DS_NEW_mp4box.mp4" does not play on LG 8K Z3, "file not supported".

[Kuler087]

You should try all the variants. They all have something ''different'' that could make them work or not.

[ReciprocalUniverse]

You should try all the variants. They all have something ''different'' that could make them work or not.

But you said this, "P5 encoding from scratch requires the proprietary Dolby engine,"

...so not interested in P5 file list unless we can make them without license.

P8.1 works on the Z3, just in 4k not 8k.

The (3) other remaining files have HDR10+ naming inclusions, are they DV compliant?

[ReciprocalUniverse]

Never mind, I see that they have DV. We'll try them.