Dolby Vision now possible through MP4 Mux.

[RESET_9999]

So @manix converted the "mutli pattern" to profile 5 and as expected, no more colorspace conversion/clipping issues on the Shield. No blue banding as well.

We discovered something else, something quite big. The DV 8.1 MP4 encoded directly from Resolve doesn't have the famous color issue bug on the Shield!!!! what the hell!!!
So it means there is something in quietvoid/yusesope/makemkv DV remuxing that the Shield doesnt like at all... Strange though that only the Shield seem to be affected.

no color issues:
P5 pattern : https://drive.google.com/file/d/1gFrasF ... sp=sharing
P8.1 pattern (DV MP4 straight from resolve) : https://drive.google.com/file/d/1fCjcMH ... sp=sharing

color issues:
P8.1 pattern (dovi_tool XML from resolve) :https://drive.google.com/file/d/1Aq3v03 ... sp=sharing
P8.1 pattern (dovi_tool madvr) : https://drive.google.com/file/d/1NbXM2p ... sp=sharing


We are going to make a P8.1 of Doctor Sleep in resolve, I bet there's no more red push...

[mtotheb]

This has to be one of the biggest news in this thread in a while. Hopefully the difference can be reverse engineered (looks hopeful at @quietvoid). I really thought we’d need to wait for a complete new SoC to maybe one day get DV (at least MEL)+Passthrough Audio in a device to simply stream like the Shield.

[quietvoid]

We discovered something else, something quite big. The DV 8.1 MP4 encoded directly from Resolve doesn't have the famous color issue bug on the Shield!!!! what the hell!!!
So it means there is something in quietvoid/yusesope/makemkv DV remuxing that the Shield doesnt like at all... Strange though that only the Shield seem to be affected.

The encoded files aren't comparable.
Resolve: BT.2020 mastering display, 10000/256 CLL, chroma location center.
Other: DCI-P3 mastering display, 1000/400 CLL, chroma location top-left.

And in the RPU, L6 and L9 are different (Resolve matches BT.2020 primaries, dovi_tool uses DCI-P3 by default).
I doubt L11 makes a difference unless the display supports CM v4.x.
Finally, Resolve doesn't support shot based metadata, so every frame carries "scene_refresh_flag": 1.

Those should obviously be matched first before jumping to conclusions.
MakeMKV shouldn't be doing anything different, as the source isn't modified.

Also, these MP4 files are missing the proper compatibility ID for 8.1.

After that, what you can try:
- Adding a default 100 nits L2 trim
- Copying the L3
- Copying the L4

[RESET_9999]

We discovered something else, something quite big. The DV 8.1 MP4 encoded directly from Resolve doesn't have the famous color issue bug on the Shield!!!! what the hell!!!
So it means there is something in quietvoid/yusesope/makemkv DV remuxing that the Shield doesnt like at all... Strange though that only the Shield seem to be affected.

The encoded files aren't comparable.
Resolve: BT.2020 mastering display, 10000/256 CLL, chroma location center.
Other: DCI-P3 mastering display, 1000/400 CLL, chroma location top-left.

And in the RPU, L6 and L9 are different (Resolve matches BT.2020 primaries, dovi_tool uses DCI-P3 by default).
I doubt L11 makes a difference unless the display supports CM v4.x.
Finally, Resolve doesn't support shot based metadata, so every frame carries "scene_refresh_flag": 1.

Those should obviously be matched first before jumping to conclusions.
MakeMKV shouldn't be doing anything different, as the source isn't modified.

Also, these MP4 files are missing the proper compatibility ID for 8.1.

the spears and munsill pattern is encoded with maxcll/fall 1000/400 but resolve and madvr measure it 10 000nits
Resolve automatically calculated a new maxcll/fall at delivery, same for L6. It defaults to chroma type 1 as well, i dont think we can change that.

I'll match the color primaries for the 2nd clip but i doubt it will make any difference. As for L9 i dont know.

Also, these MP4 files are missing the proper compatibility ID for 8.1.

correct me if i am wrong but I use the first version of the mp4muxer (because the newest one doesnt work) and --dv-bl-compatible-id 1 doesnt work. ( i think it was added later)

[quietvoid]

I'll match the color primaries for the 2nd clip but i doubt it will make any difference. As for L9 i dont know.

L9 needs to be matched too.

correct me if i am wrong but I use the first version of the mp4muxer (because the newest one doesnt work) and --dv-bl-compatible-id 1 doesnt work. ( i think it was added later)

I think the latest version of mp4muxer doesn't work only on LG TV internal player?
So you can use latest version for the Shield, or tsmuxer.

If I can find time I'll try reencoding the pattern with my suggestions.
Maybe this weekend.

[RESET_9999]

If I can find time I'll try reencoding the pattern with my suggestions.

thanks , that would be great because i have no idea how to do L3,L4

[quietvoid]

If I can find time I'll try reencoding the pattern with my suggestions.

thanks , that would be great because i have no idea how to do L3,L4

It's pretty simple. Run dovi_tool info on the Resolve RPU, copy paste the blocks into the generate config.
Example: https://github.com/quietvoid/dovi_tool/ ... e.json#L16

Also, can you clarify which bug is fixed with the Resolve file on the Shield?
The red push or also the blue banding?

[RESET_9999]

Also, can you clarify which bug is fixed with the Resolve file on the Shield?
The red push or also the blue banding?

the red push , i dont know yet.
The blue banding and colorspace conversion/clipping are fixed. It looks perfect like the C8 and X700/X800m2

reference (dovitool version): https://slow.pics/c/ga3ytybR

resolve version (not same camera settings as the old comparison):

[RESET_9999]

red push is still present with the resolve files

re-injecting the same rpu doesnt trigger the bug but reinjecting it to the other video does so the injecting part is fine.
Why does the bug happen with madvr generated RPU as well and only on the shield? I guess just editing L5/L6 for madvr is not enough. very strange...

L9 needs to be matched too.

EDIT: it happens only when the BL is BT2020 MD. so yeah it's a colorspace mismatch but it only causes problems on the shield.
How do to make the rpu bt2020 instead of p3 with madvr measurement to Dovi?
0= P3
1= bt2020 ???
{
"Level9": {
"length": 1,
"source_primary_index": 0
}

[realbabilu]

I'll match the color primaries for the 2nd clip but i doubt it will make any difference. As for L9 i dont know.

L9 needs to be matched too.

correct me if i am wrong but I use the first version of the mp4muxer (because the newest one doesnt work) and --dv-bl-compatible-id 1 doesnt work. ( i think it was added later)

I think the latest version of mp4muxer doesn't work only on LG TV internal player?
So you can use latest version for the Shield, or tsmuxer.

If I can find time I'll try reencoding the pattern with my suggestions.
Maybe this weekend.

my android hisense tv works with mp4muxer mp4 pc / m4v subler mac for p5 p7 p8.1, it support atmos too.
except playing p7 fel single layer (somehow jitter...), and lazy cannot play subtitle inside mp4/m4v
any p7 double layer fel that converted to p8.1 will downgraded to HDR10 with DVtool.
Any TSmuxer converted will have sync issue, may the subtitles hdv alone, or out of sync audio.
I definitely suggest subler muxer for any Apple devices, may including ATV perhaps, not tested on that.

So basically mp4muxer has more compatibility in my internal tv player, except that doesnt have delay audio offset. it will outsync when the audio have offset.
My question:
what is --dv-bl-compatible-id option did on mp4muxer? especially for p8 profile, that is said must have.
can mp4box fix outsync offset from mp4muxer?

[phbart]

I tried the latest version, but it's still not triggering DV. I remuxed as "blu-ray disc". Do I need to change the mux settings?

you remuxed as bluray folder and tried to play the m2ts ? that's the problem.
You have to mux your BD straight to TS or M2TS.

Now it worked like a charm! Thank you!

[quietvoid]

EDIT: it happens only when the BL is BT2020 MD. so yeah it's a colorspace mismatch but it only causes problems on the shield.
How do to make the rpu bt2020 instead of p3 with madvr measurement to Dovi?
0= P3
1= bt2020 ???
{
"Level9": {
"length": 1,
"source_primary_index": 0
}

Use this for BT.2020:

Code: Select all

{
    "Level9": {
        "length": 1,
        "source_primary_index": 2
    }
}

So does the Shield only have the bug with the BL using mastering display DCI-P3 for HDR10?
If so there's really nothing we can do. Most titles are mastered in DCI-P3.

The original pattern you shared as "multi pattern DV P8.ts" is BT.2020, though. It didn't have L9 metadata.

[RESET_9999]

So does the Shield only have the bug with the BL using mastering display DCI-P3 for HDR10?
If so there's really nothing we can do. Most titles are mastered in DCI-P3.

Thankfully it's the other way around, MDP P3 BL is fine.
I will do more tests tonight but regardless of the rpu, it looks like as soon as the HDR10 BL was mastered on a bt2020 monitor, the bug happens.
I'll check some bt2020 DV movies too. Such as the Matrix.

The original pattern you shared as "multi pattern DV P8.ts" is BT.2020, though. It didn't have L9 metadata.

yep, I did the first version with CMV2.9. So since that one doesn't have an MDP mismatch, it could confirms my suspicion that the shield has problems with movies mastered on a BT2020 display?
I redid the pattern because I based the dv analysis on maxcll 1000, when the clip actually is 10 000nits. So L1/L2 were incorrect. I guess I went too fast for the color settings in CMV4.0 for the second version

Code: Select all

{
    "Level9": {
        "length": 1,
        "source_primary_index": 2
    }
}

thank you, but with the madvr generated DV from a BT2020 MDP video, L9 defaults to P3 ?
could that be automated?

Code: Select all

        {
          "Level9": {
            "length": 1,
            "source_primary_index": 0
          }

[quietvoid]

thank you, but with the madvr generated DV from a BT2020 MDP video, L9 defaults to P3 ?
could that be automated?

You can use a JSON config along with a madVR measurement file.

[deadchip12]

Could someone briefly explain what were being discussed in the last few pages? The x700/x800m2 bluray player seem like the ultimate devices for playing back dolby vision files, so what else need to be discussed? I'm just curious, not complaining or anything. Are people trying to make it work on other devices?