Dolby Vision now possible through MP4 Mux.

[FubbAyH]

That Dolby Vision UHD 8.1 glass blowing test file doesn't have dvhe set as the codec ID (bug of their Dolby MP4 muxer)

Here is the file with the correct codec ID set: https://mega.nz/file/1XRRCS5C#1tRtdkEet ... XHiMOymkeU

Thank you for that fixed Dolby file. That one plays as HDR10 both in Plex in Infuse.

The P5s play as expected but the P4s play as SDR.

Thank you for doing the testing.

It has frustrated me that the players seem to be ignoring the RPU in my P5 test files, because I was assuming that P5 was the one thing that would work reliably. I'm wondering if it's just an Infuse bug causing that, so I'll investigate that.

[RESET_9999]

It has frustrated me that the players seem to be ignoring the RPU in my P5 test files, because I was assuming that P5 was the one thing that would work reliably. I'm wondering if it's just an Infuse bug causing that, so I'll investigate that.

just because the file mediainfo says profile 5 DV doesn't mean the actual RPU is profile 5. The rpu is still p7 or p8 regardless of the profile it's muxed because the dv-tool doesn't support p7(or p8) to p5. And an actual true p5 rpu probably wouldn't work with an HDR10 BL
you can check the rpu data with this cmd:

Code: Select all

dovi_tool.exe info --input RPU.bin -f 0

[FubbAyH]

Ah, I see what you mean. I didn't realise that the RPU data includes which profile it is for. So it's actually reasonable that Infuse would ignore the RPU in my hacked-together file because it's for the wrong profile. So we don't have any evidence that Infuse is playing profile 5 files incorrectly. I'll keep investigating. Thanks again for all your help!

[FubbAyH]

(Sorry if I'm boring anyone to tears with this saga, I'll shut up soon.)

I've now found a profile 5 RPU and have injected that into my test file and it also seems to be ignored when playing back in Infuse (and in Plex). My (LG B7 OLED) TV's built-in video player gives dramatic color changes when playing the test file so it appears to be processing the RPU correctly. I've sent the sample and a video of the LG's playback to the Infuse developers, and I'll report back if they reply.

[glc650]

...I'll shut up soon.)

Please don't..if it really is ignoring RPU appreciate the work getting it fixed.

I've sent the sample and a video of the LG's playback to the Infuse developers, and I'll report back if they reply.

I worked with them years ago with an SMB issue. They were slow to get it fixed but did. Hopefully here they will be quick to confirm any issues and get them fixed.

[Manixx2020beyound]

Few more p5 Spares.

[RESET_9999]

(Sorry if I'm boring anyone to tears with this saga, I'll shut up soon.)

I've now found a profile 5 RPU and have injected that into my test file and it also seems to be ignored when playing back in Infuse (and in Plex). My (LG B7 OLED) TV's built-in video player gives dramatic color changes when playing the test file so it appears to be processing the RPU correctly. I've sent the sample and a video of the LG's playback to the Infuse developers, and I'll report back if they reply.

nah keep going, this thread is all about experimenting with DV.
in order to properly test if rpu is used, you probably should modify/unsync a true p5 file instead of injecting a p5 rpu to a random HDR10 BL.
You can delay the rpu metadata with a JSON edit and inject it back into the original p5 bl and it should produce visible brightness changes. the file would still follow dv specs.

this json will delay the metadata 120frames.

Code: Select all

{
	"duplicate": [
		{
			"source": 0,
			"offset": 0,
			"length": 120
		}
	]
}

[FubbAyH]

Please don't..if it really is ignoring RPU appreciate the work getting it fixed.

nah keep going, this thread is all about experimenting with DV.
in order to properly test if rpu is used, you probably should modify/unsync a true p5 file instead of injecting a p5 rpu to a random HDR10 BL.

I'll probably have to wait until next weekend to do any more experiments, but thanks very much for the encouragement

[quietvoid]

That would help the grading community,
For those guys like myself 4k,6k,8k cameras
And do their own grading without doblyvision license fees
No secondary trim pass doe.
To my knowledge the doblyvision fees are only for secondary trim passes/Rpu creation & final encode of the doblyvision master to hevc

I did a first attempt at generating a RPU from XML: https://github.com/quietvoid/dovi_tool/pull/43
Still need to figure out if the L2 trims are correct..

L1 should be fine though, the rest needs testing and sample XML files..
Missing proper L5 (aspect ratio), since I don't really know how to decide whether it's horizontal or vertical letterbox bars.

[RESET_9999]

oh wow. so we can now convert HDR10plus to DV. Amazing, thank you!!
we have to compare original DV with this conversion now..

@manix??? Alita bluray has hdr10+ and DV I believe...

[quietvoid]

I've watched a couple episodes of The Expanse with the new HDR10+ to DoVi, to me they looked fine..
Black crush in comparison to HDR10, as expected from the Firestick. Didn't affect a lot of scenes though.

Some titles which include both, that I know of:
Doctor Sleep
Wonder Woman 1984
Godzilla vs Kong

Just off the top of my head..

[RESET_9999]

yep, WW-84 is the ideal title since the bluray is MEL DV and hdr10plus. There's also a profile 5 web-dl. @manix, I'm making you samples to test with your Shogun.

btw, I hope you hide behind a VPN, Dolby must be real mad at you if they are aware of your tool lol...

[Manixx2020beyound]

That would help the grading community,
For those guys like myself 4k,6k,8k cameras
And do their own grading without doblyvision license fees
No secondary trim pass doe.
To my knowledge the doblyvision fees are only for secondary trim passes/Rpu creation & final encode of the doblyvision master to hevc

I did a first attempt at generating a RPU from XML: https://github.com/quietvoid/dovi_tool/pull/43
Still need to figure out if the L2 trims are correct..

L1 should be fine though, the rest needs testing and sample XML files..
Missing proper L5 (aspect ratio), since I don't really know how to decide whether it's horizontal or vertical letterbox bars.

Fantastic! great news!!
Thanks, so much will be testing tonight.
“NO BANZ TO MAKE DV DANCE”
Raw footage:
Now I can create a dv music video
With l1
Testing a dv/hdr10plus xml master of beckett which also has secondary trims too
Created by resolve
For raw footage we should be able to define the aspect ratio in the final encoding settings

[RESET_9999]

I'm getting this error:



EDIT. ok looks like im not using the right CMD-LINE...
Can we just convert HDR10plus json straight to DV like this :

Code: Select all

dovi_tool.exe generate --hdr10plus-json D:\HDR10plus.JSON --rpu-out D:\RPU_generated.bin

or do we have to make a json and enter the lenght, target nits etc ? how do we know which value to use? or do we just enter the lenght and static metadata and the tools do the rest ?


does this json correct for WW-84?:

Code: Select all

dovi_tool.exe generate --hdr10plus-json D:\HDR10plus.JSON --json D:\edited.json --rpu-out D:\RPU_generated.bin

Code: Select all

{
    "length": 217408,
    "level2": [
        {
            "target_nits": 100
        },
        {
            "target_nits": 600
        },
        {
            "target_nits": 1000,
            "trim_power": 2096,
            "trim_saturation_gain": 2128
        },
        {
            "target_nits": 2000,
            "trim_slope": 2048,
            "trim_offset": 2048,
            "trim_power": 2048,
            "trim_chroma_weight": 2048,
            "trim_saturation_gain": 2048,
            "ms_weight": 2048
        }
    ],
    "level6": {
        "max_display_mastering_luminance": 1000,
        "min_display_mastering_luminance": 1,
        "max_content_light_level": 596,
        "max_frame_average_light_level": 200
    }
}

[quietvoid]

I'm getting this error:



EDIT. ok looks like im not using the right CMD-LINE...
Can we just convert HDR10plus json straight to DV like this :

Code: Select all

dovi_tool.exe generate --hdr10plus-json D:\HDR10plus.JSON --rpu-out D:\RPU_generated.bin

or do we have to make a json and enter the lenght, target nits etc ? how do we know which value to use? or do we just enter the lenght and static metadata and the tools do the rest ?

You have to specify the config JSON for generating, since the HDR10+ info is only used for L1 metadata.

So something like this:

Code: Select all

dovi_tool generate -j assets/generator_example.json --hdr10plus-json metadata.json

The length is not optional in master, but it's overriden by whatever is in the HDR10+ file. Target nits or specific L2 can be used.

For the L2 to have no effect, something like this should work:

Code: Select all

"level2": [
        {
            "target_nits": 100
        },
        {
            "target_nits": 600
        },
        {
            "target_nits": 1000
        },
        {
            "target_nits": 2000
        }
]