Dolby Vision now possible through MP4 Mux.

[quietvoid]

that's right, I just tested this too. Once the rpu is modified(7/3079), DV becomes blown-out like(but not as much) HDR10 @10k nits and i can see the same color difference as in the vincent video
So the LLDV bug is caused by the player not sending the correct trim pass when it's decoding DV? So the brighter the HDR grade is, the more the LLDV bug will be visible.

The bug is definitely the same thing, because creative adjustments aren't being applied by the player. I think Stacey mentioned that the L2 metadata was ignored, and that's what causes the image to be worse.
Obviously the brighter the grade, then L2 metadata has stronger adjustments depending on target display nits.

However that's all creative intent, so it would be complicated to add "proper" adjustments for non-DoVi HDR10 movies.

[RESET_9999]

yep, it all makes sense now.

the eagle beak still remains relatively yellow though while in LLDV with original fel, it turns greenish.

[chros]

I have the perfect pitch black room with light absorbent material on walls, ceiling, and floor ( black velvet)

That's a hardcore setup, congrats!

Btw, since you are the DoVi guru (and we know a lot about hdr10), I don't really understand what the min (max) limunance setting does in reality. I don't see the point. Do you know anything about this? Thanks

I'm not sure what min/max you're talking about, in the RPU metadata?
It's usually the measured values for a frame/scene, so that's the dynamic part..

Also, setting the source min and max PQ in the RPU to proper values for limited has an effect.
Now I see down to 78 with 62/3696 (as spec says for profile 7), and 74 with 7/3079

Somehow 7/3079 is also being used in UHD BD.

From the data I can collect with the level 6 metadata (mastering display)..
Max 1000, min 1-10 should be 7/3079.
Max 4000, min 50 should be 62/3696.

oh wow... it is the first time I can see 66 flashing with a DV black pattern. Usually can only see around 72 flashing

I'm actually seeing 72 flashing with L2 metadata target for 600 nits, source min/max 7,3079 and L6 metadata MDL 1000,1. That was a generated RPU.
So with MDL 1000 metadata, LG player shows down to 68. Firestick to 72.
So maybe this black level pattern is not really useful, thanks Dolby.

Nah 66 is clearly visible using the C8 internal player with the 7/3079 sample ... I'm not sure what that means though, I would like to know what Stacey thinks about that.

That's a really interesting finding!
I meant the measured values for a frame/scene in the RPU, but I thought there's a min value as well, but there isn't, only maxCLL and maxFall per frame.
But you now brought up the "Source min and max PQ", what does it mean exactly? And what are those "7/3079" and "62/3696" numbers corresponding to? Which metric? (I bet it's not nits.)
And what is the L1 min_pq/max_pq/avg_pq?

Here all the 3 sources (internal Plex, Oppo, Firestick4k) produces different results with those files
Firestick4k is the best with the 3079 sample (as you said), here I can see 74 flashing, but it cuts everything under it, no matter which picture preset I select.
The brightest source out of all is the internal Plex, 2nd is Oppo, then Firestick at the last place (Maybe HDMI signal cuts black at certain point as well, not sure.)

This has been implemented in v0.4.0
You can now generate RPU metadata in v0.4.0, see documentation

wow this is great.. thank you works great... so much easier than before!!!!
...
BTW, I watched two p8 injected DV movies this weekend. Not a single issue. works just perfect. really amazing work man!!!

Indeed, You have created an amazing, useful tool, thank You!
E.g. now we can easily create DoVi test patterns out of our HDR10 ones
Here's the previously posted DP p8.1 DoVi banding sample (05-2160p_23fps_dovi_p81-dp_s02e03_banding.ts) with generated RPU (I measured the maxFALL with madvr's madmeasure):

Code: Select all

{
    "length": 1000,
    "target_nits": 1000,
    "level6": {
        "max_display_mastering_luminance": 1000,
        "min_display_mastering_luminance": 1,
        "max_content_light_level": 1000,
        "max_frame_average_light_level": 67
    }
}

What is the "target_nits" for? (for L2 target_max_pq?) Is it in nits? If so, can we use any value here? (e.g. 2435)
Initially I used 600 (as in your sample), but the result didn't "pop", after that I did it with 1000 and it's much better this way.
So, if you also agree, then this value needs to be changed in your sample as well.

I just tried the S&M benchmark with generated Dolby Vision and it looks the exact same as the TV-led vs player-led comparison.
That's probably because the trim passes aren't present, so saturation is wrong.

So the LLDV bug is caused by the player not sending the correct trim pass when it's decoding DV?

I think Stacey mentioned that the L2 metadata was ignored, and that's what causes the image to be worse.

I guess you meant the 10.000 nits SM version.
Nice finding, again! But what is a trim pass in DoVi world and what is it used for? (I saw it in the RPU as well.)

[Manixx2020beyound]

I have the perfect pitch black room with light absorbent material on walls, ceiling, and floor ( black velvet)

That's a hardcore setup, congrats!

Btw, since you are the DoVi guru (and we know a lot about hdr10), I don't really understand what the min (max) limunance setting does in reality. I don't see the point. Do you know anything about this? Thanks

I'm not sure what min/max you're talking about, in the RPU metadata?
It's usually the measured values for a frame/scene, so that's the dynamic part..

Also, setting the source min and max PQ in the RPU to proper values for limited has an effect.
Now I see down to 78 with 62/3696 (as spec says for profile 7), and 74 with 7/3079

Somehow 7/3079 is also being used in UHD BD.

From the data I can collect with the level 6 metadata (mastering display)..
Max 1000, min 1-10 should be 7/3079.
Max 4000, min 50 should be 62/3696.

oh wow... it is the first time I can see 66 flashing with a DV black pattern. Usually can only see around 72 flashing

I'm actually seeing 72 flashing with L2 metadata target for 600 nits, source min/max 7,3079 and L6 metadata MDL 1000,1. That was a generated RPU.
So with MDL 1000 metadata, LG player shows down to 68. Firestick to 72.
So maybe this black level pattern is not really useful, thanks Dolby.

Nah 66 is clearly visible using the C8 internal player with the 7/3079 sample ... I'm not sure what that means though, I would like to know what Stacey thinks about that.

That's a really interesting finding!
I meant the measured values for a frame/scene in the RPU, but I thought there's a min value as well, but there isn't, only maxCLL and maxFall per frame.
But you now brought up the "Source min and max PQ", what does it mean exactly? And what are those "7/3079" and "62/3696" numbers corresponding to? Which metric? (I bet it's not nits.)
And what is the L1 min_pq/max_pq/avg_pq?

Here all the 3 sources (internal Plex, Oppo, Firestick4k) produces different results with those files
Firestick4k is the best with the 3079 sample (as you said), here I can see 74 flashing, but it cuts everything under it, no matter which picture preset I select.
The brightest source out of all is the internal Plex, 2nd is Oppo, then Firestick at the last place (Maybe HDMI signal cuts black at certain point as well, not sure.)

This has been implemented in v0.4.0
You can now generate RPU metadata in v0.4.0, see documentation

wow this is great.. thank you works great... so much easier than before!!!!
...
BTW, I watched two p8 injected DV movies this weekend. Not a single issue. works just perfect. really amazing work man!!!

Indeed, You have created an amazing, useful tool, thank You!
E.g. now we can easily create DoVi test patterns out of our HDR10 ones
Here's the previously posted DP p8.1 DoVi banding sample (05-2160p_23fps_dovi_p81-dp_s02e03_banding.ts) with generated RPU (I measured the maxFALL with madvr's madmeasure):

Code: Select all

{
    "length": 1000,
    "target_nits": 1000,
    "level6": {
        "max_display_mastering_luminance": 1000,
        "min_display_mastering_luminance": 1,
        "max_content_light_level": 1000,
        "max_frame_average_light_level": 67
    }
}

What is the "target_nits" for? (for L2 target_max_pq?) Is it in nits? If so, can we use any value here? (e.g. 2435)
Initially I used 600 (as in your sample), but the result didn't "pop", after that I did it with 1000 and it's much better this way.
So, if you also agree, then this value needs to be changed in your sample as well.

I just tried the S&M benchmark with generated Dolby Vision and it looks the exact same as the TV-led vs player-led comparison.
That's probably because the trim passes aren't present, so saturation is wrong.

So the LLDV bug is caused by the player not sending the correct trim pass when it's decoding DV?

I think Stacey mentioned that the L2 metadata was ignored, and that's what causes the image to be worse.

I guess you meant the 10.000 nits SM version.
Nice finding, again! But what is a trim pass in DoVi world and what is it used for? (I saw it in the RPU as well.)

Trim pass process.
https://learning.dolby.com/hc/en-us/art ... Trim-Pass-

[quietvoid]

That's a really interesting finding!
I meant the measured values for a frame/scene in the RPU, but I thought there's a min value as well, but there isn't, only maxCLL and maxFall per frame.
But you now brought up the "Source min and max PQ", what does it mean exactly? And what are those "7/3079" and "62/3696" numbers corresponding to? Which metric? (I bet it's not nits.)
And what is the L1 min_pq/max_pq/avg_pq?

Source min and max PQ are PQ code values in 12 bit, converting to nits should be simple, it's just a division by 4095 and converting from PQ to nits.
I'm not exactly sure what they specify, but I think it might have to do with the mastering display, since they seem correlated to the L6 metadata.

L1 metadata are measurements done per frame/scene (depends) by analysis. It's supposed to help with the tonemapping.

What is the "target_nits" for? (for L2 target_max_pq?) Is it in nits? If so, can we use any value here? (e.g. 2435)
Initially I used 600 (as in your sample), but the result didn't "pop", after that I did it with 1000 and it's much better this way.
So, if you also agree, then this value needs to be changed in your sample as well.

Target nits is for L2 target_max_pq, yes. It is in nits.
Normally it is used for creative adjustments per trim ("different displays"), because the grading is done at multiple brightness to map properly across the whole range while keeping creative intent.
I didn't think a single L2 target would make any difference, but maybe. Currently everything is left default, so no adjustments at all.

From what I noticed, highlights are tonemapped OK but I'm not sure if FALL is lower. Saturation might be different for higher nits.
I didn't really compare properly with different targets.

I don't really expect generated metadata to be very useful, since it's missing creative intent and measurements.
And since measurements often depend on denoised video (L4 metadata) and properly separated scenes, it would be quite complex to do.

[RESET_9999]

Hi guys im getting crazy with this, i dont even know if its possible or not.

I have a dolby vision single layer mp4, ripped from web, inside theres multiple audio tracks so i just want to have the dolby vision single layer with 1 track.

there is no EL in profile 5 DV from streaming.
demux, then :

Code: Select all

mp4muxer_64bits.exe --dv-profile 5 --input-file X:\video.hevc --input-file X:\audio.ec3 --output-file output.mp4

Hi, sorry for the noob question but how and what do i need to use to extract both layer from the dv web mp4 rip? for dovi tool i need the hevc already but how i go from the dv mp4 ripped from web and the hevc keeping both layers?
with mp4demux i only get 1 hevc that doest contain the dolby layer...

you have to extract and convert the RPU to profile 8(step #2). Once you know the frame difference with the bluray remux, you make a json and you can inject the rpu from the web-dl.

[RESET_9999]

Tnx for your answer

1. when i use that line for mp4muxer i get a SDR file with greenish look, using the .h265 (not .hevc) that is extracted with mp4demuxer.

2. how do i extract the rpu from a mp4 (not .hevc) DV rip from disney plus?

1- probably because you are using the latest mp4muxer which doesnt work for me as well. Try with this old version instead: https://drive.google.com/file/d/1yZ1EgB ... sp=sharing


2- demux to hevc(or h265) with tsmuxer, ffmpeg, mp4demuxer etc...
then:

Code: Select all

dovi_tool.exe -m 3 extract-rpu DV.hevc

[Poker354]

Hi guys im getting crazy with this, i dont even know if its possible or not.

I have a dolby vision single layer mp4, ripped from web, inside theres multiple audio tracks so i just want to have the dolby vision single layer with 1 track.

there is no EL in profile 5 DV from streaming.
demux, then :

Code: Select all

mp4muxer_64bits.exe --dv-profile 5 --input-file X:\video.hevc --input-file X:\audio.ec3 --output-file output.mp4

Hi, sorry for the noob question but how and what do i need to use to extract both layer from the dv web mp4 rip? for dovi tool i need the hevc already but how i go from the dv mp4 ripped from web and the hevc keeping both layers?
with mp4demux i only get 1 hevc that doest contain the dolby layer...

you have to extract and convert the RPU to profile 8(step #2). Once you know the frame difference with the bluray remux, you make a json and you can inject the rpu from the web-dl.

Tnx for your answer

1. when i use that line for mp4muxer i get a SDR file with greenish look, using the .h265 (not .hevc) that is extracted with mp4demuxer.

2. how do i extract the rpu from a mp4 (not .hevc) DV rip from disney plus?

What I do with the Mp4 file is run it through MKVToolnix (latest v60) to create a mkv file
then use the command line: mkvextract.exe tracks YourFileName.mkv -f 0:DV.hevc

then extract the RPU with the command line: dovi_tool.exe -m 3 extract-rpu DV.hevc

[RESET_9999]

Im confused too, i have that file too and its in mkv, its only hdr10 or Dv? i only understand the merge or the rpu and the uhd disc rip hdr10 file but the result is a hdr or dv mkv? if its a dv in mkv theres any way to revert back and get 2 layers to form a mp4 dv? i only have a x700 to reproduce dv so i all mkv, dv or hdr10 shows as hdr.

anyway that file is dv or hdr?

It's both DV and HDR10 compatible. For playback on your x700, just remux the file with tsmuxer .
you will have to add the AC3 core back into the TrueHD stream if you want to keep Atmos.

[RESET_9999]

not true and it has been discussed many times in this thread (even kept the pictures, i knew someone else would say that again one day lol)....
again, just remux it to TS or M2TS and you will get true DV profile 8 . I actually watched both Endgame and Infinity war on the x700 in DV + atmos

real DV (ts dual layer but works with single layer too):



fake DV (ts AVC):

[RESET_9999]

1. where did you got a infinity war p8 mkv or mp4 other than the single layer mp4 from disney plus?

2. how do you know that .ts in the x700 is player as dual layer and not single layer?
i did the test with venom and bumblebee like a year ago, comparing mp4 dual layer versus full rip in m2ts and there was a big difference in picture brightness and detail. both displayed as dolby vision on tv and x700

1- I did the P8 remux myself... You can as well, all the info on how to do it is available in this thread.
2- @manix and I did many comparisons with the original, you can find all of them right here in this thread. The x700 is a 1:1 DV device and support all the profiles

[DennisTheMenace]

I don't know if this is already known, but the justplayer now also supports Dolby Vision (mkv) and dts-hd sound

https://github.com/moneytoo/Player/releases

[glc650]

Well i though that m2ts just was read as 1 layer dv but good to know now, even when all my dv movies are on mp4.

m2ts is what blu-ray uses so not sure how you got that idea.

[glc650]

4. isnt the dv backup dual layer the best a movie can be seen?

P7 FEL (blu-ray, DTDL) is the best DV available. I believe all streaming services use Profile 5 which is STSL (so no EL). P8 is STSL as well.

[RESET_9999]

After reading here and there im getting confusing with the dv profiles the mp4muxer and the m2ts/ts files.

I have a Lg C1 and a Sony x700

1. i used to rip a dv movie and just make the mp4 dual layer way putting profile 7 always. That changes for a mel or fel movies?.

2. knowing now i was wrong and i could use a m2ts instead of a mp4 file for a dual layer playback, do i lose something if i change that profile 7 dv mp4 with mkvtoolnix and then tsmuxer?

3. p7 > p8 > p5 ?

4. isnt the dv backup dual layer the best a movie can be seen?

5. is better a dovip8 movie than a p7 mp4 muxed movie with their native dual layers from the disk?

Im feeling like a retard with these 4 years old questions but if anybody can explain me this would be very nice.

As glc650 said, the best DV is FEL P7 (dual-layer) but not all the movies are FEL. Note that your TV internal app won't play FEL movies properly because it lack of a 2nd decoder but your x700 will play properly pretty much anything you throw at him

P7 fel(always dual layer) = 1 HDR10 base layer 10bits + 12bits data in EL(2 extra bits) + dynamic metadata in RPU
P7 mel (always dual layer) = 1 HDR10 base layer 10bits + blank EL (no extra bit) + dynamic metadata in RPU
P8 (always mel and single layer) = 1 HDR10 base layer 10bits + dynamic metadata in RPU
P5 (always single layer) = none-tonemapped DV base layer(green and purple colors) + dynamic metadata in RPU
P4 (dual layer,FEL or MEL) = 1 SDR base layer + FEL or MEL + dynamic metadata in RPU

so it goes like this:
P7 fel > P7 mel = P8 = P5

*Profile 7 can be merged in a single track (makemkv) but it's still dual layer DV.
*Profile 8 can also have an HLG base layer (iphone recording) so this format is compatible with HLG, SDR and DV.
*profile 5 DV : I'm not sure if it's 12bits or 10 bits because there's this description about my profile 5 patterns: ''10bits encoded remapped 12bits''. Not really sure what it means but it sounds like profile 5 could be 12bits as well.

- Dolby Laboratories
Since current Dolby Vision test patterns are limited, we decided to create an entire suite utilizing profile 5, the most commonly used profile amongst manufacturers. Profile 5, typically utilized for streaming Dolby Vision content, encompasses Dolby Vision’s proprietary IPT for color primaries and color matrix, along with the use of full range for RGB. This test pattern suite incorporates an UltraHD 3840x2160 resolution, proprietary IPT similar to BT.2100 ICtCp, 10-Bit encoded/12-bit remapped and a ST.2084 transfer function. This project follows the same idea behind our “UltraHD|HDR-10 Test Pattern Suite”, an attainable solution to calibrate and/or measure your new HDR display, without having to spend thousands on a new UHD/HDR test pattern generator.