Dolby Vision now possible through MP4 Mux.

[RESET_9999]

Since baking in FEL with StaxRip I've been getting validate_metadata errors like these, when adding the converted RPU. Is this normal?

Code: Select all

WARNING: L1=0,0,0 metadata at shot: UniqueID = e822cd1d-e184-4959-bd7f-4fcc0f6754fb @[0-43].

Code: Select all

WARNING: shot: UniqueID = bc0fa9d6-cce2-4d50-b990-9b3f88a48802 @[175549-175794] contains target trim(s) without a 100-nit, Rec.709 trim.

This is the same in the original RPU. The p7 to p8 conversion does not touch the dynamic metadata (L1/L2 etc..)
BTW, the warnings in metafier is not really a problem. Errors on the other hand is a problem.


FYI, in the new Mission Impossible, it looks like the colorist missed the memo about L2 0.025 lift. These shots will most likely result in grey letterbox on devices that ignore L5
And you can clearly see on this video how the trims raise the brightness: https://www.youtube.com/watch?v=Hk6ria8_PFo

Code: Select all

WARNING: Positive Level2 lift value at shot: UniqueID = b42d5b72-2b5c-431a-a160-d7204bb67330 @[18280-18325]
WARNING: Positive Level2 lift value at shot: UniqueID = 3cff3948-45b7-4179-9260-51d41aadbdb8 @[18326-18421]
WARNING: Positive Level2 lift value at shot: UniqueID = 64ab0852-6218-435c-ab93-80c821f553c8 @[19192-19290]
WARNING: Positive Level2 lift value at shot: UniqueID = 64ab0852-6218-435c-ab93-80c821f553c8 @[19192-19290]
WARNING: Positive Level2 lift value at shot: UniqueID = 2b8c89f0-82ae-449f-a2e8-f25cbb26ff19 @[19380-19479]
WARNING: Positive Level2 lift value at shot: UniqueID = 40c08837-aa0e-4eb6-a42c-d4b19fa30530 @[19914-19932]
WARNING: Positive Level2 lift value at shot: UniqueID = 40c08837-aa0e-4eb6-a42c-d4b19fa30530 @[19914-19932]
WARNING: Positive Level2 lift value at shot: UniqueID = 43bb1490-66a7-4b78-b6f4-b2f2d9bbb6a6 @[50546-50583]
WARNING: Positive Level2 lift value at shot: UniqueID = 43bb1490-66a7-4b78-b6f4-b2f2d9bbb6a6 @[50546-50583]
WARNING: Positive Level2 lift value at shot: UniqueID = 9819a8e5-d54b-4617-bbf4-555f0da2482b @[201575-201632]
WARNING: Positive Level2 lift value at shot: UniqueID = 9f396c99-2bbc-4546-8be6-341c36b6cde9 @[222752-223708] and frame: 223036 (offset=284)
WARNING: Positive Level2 lift value at shot: UniqueID = 9f396c99-2bbc-4546-8be6-341c36b6cde9 @[222752-223708] and frame: 223037 (offset=285)
WARNING: Positive Level2 lift value at shot: UniqueID = 9f396c99-2bbc-4546-8be6-341c36b6cde9 @[222752-223708] and frame: 223038 (offset=286)
WARNING: Positive Level2 lift value at shot: UniqueID = 9f396c99-2bbc-4546-8be6-341c36b6cde9 @[222752-223708] and frame: 223039 (offset=287)
WARNING: Positive Level2 lift value at shot: UniqueID = 9f396c99-2bbc-4546-8be6-341c36b6cde9 @[222752-223708] and frame: 223040 (offset=288)
WARNING: Positive Level2 lift value at shot: UniqueID = 9f396c99-2bbc-4546-8be6-341c36b6cde9 @[222752-223708] and frame: 223041 (offset=289)
WARNING: Positive Level2 lift value at shot: UniqueID = 9f396c99-2bbc-4546-8be6-341c36b6cde9 @[222752-223708] and frame: 223042 (offset=290)
WARNING: Positive Level2 lift value at shot: UniqueID = 9f396c99-2bbc-4546-8be6-341c36b6cde9 @[222752-223708] and frame: 223043 (offset=291)
WARNING: Positive Level2 lift value at shot: UniqueID = 9f396c99-2bbc-4546-8be6-341c36b6cde9 @[222752-223708] and frame: 223044 (offset=292)
WARNING: Positive Level2 lift value at shot: UniqueID = 9f396c99-2bbc-4546-8be6-341c36b6cde9 @[222752-223708] and frame: 223045 (offset=293)
WARNING: Positive Level2 lift value at shot: UniqueID = 9f396c99-2bbc-4546-8be6-341c36b6cde9 @[222752-223708] and frame: 223046 (offset=294)
WARNING: 17 Shots contain identical Level1 values
WARNING: 15 Shots contain identical Level2 values

[Gatorman]

FYI, in the new Mission Impossible, it looks like the colorist missed the memo about L2 0.025 lift. These shots will most likely result in grey letterbox on devices that ignore L5
And you can clearly see on this video how the trims raise the brightness: https://www.youtube.com/watch?v=Hk6ria8_PFo

Regarding this film, it looks like the MDL of the BL and RPU is .0050/4000 and the MaxCLL is 997 for both. Does the MDL need to be changed to 1/1000, when baking in the FEL with StaxRip? Perhaps the trims take care of this?

BTW, 6-2 is crashing for me when I try to plot HDR.

[Trees]

Quick question; when generating CMv4.0 content (3-1), how does one determine what Mastering Display to use? I assuming higher isn't necessarily better?

2 options:

1- just use the static metadata from your source HDR10
2- check the brightness first with madvr. If 95% of the movie is under 1000nits, use 1000nits MDL else, 4000.

Option 2 is better because some movies have a static MDL of 4000nits but the actual brightness is under 1000nits.
A 4000nits RPU is a lot darker than a 1000nits one regardless of the content's actual brightness and in my opinion, 4000nits MDL + low nits content is wrong without L2 trim passes because if you look at the generated(or original) trims with a 4000nits analysis, they brighten/compensate a lot for the darkness a 4000 rpu brings.

https://slow.pics/c/uVX5iFOD

So I finally got round to do this. Question, though. The files I want to eventually CMv4.0 analyze are HDR10+. The plots are all coming back as dynamic, even though you instructed me to plot the static data (6-2). Is madVR checking the dynamic HDR10+ portion of the video instead of the HDR10 static metadata portion of the video? Is something going wrong? Or will it automatically check the dynamic metadata if the file is HDR10+?

[RESET_9999]

FYI, in the new Mission Impossible, it looks like the colorist missed the memo about L2 0.025 lift. These shots will most likely result in grey letterbox on devices that ignore L5
And you can clearly see on this video how the trims raise the brightness: https://www.youtube.com/watch?v=Hk6ria8_PFo

Regarding this film, it looks like the MDL of the BL and RPU is .0050/4000 and the MaxCLL is 997 for both. Does the MDL need to be changed to 1/1000, when baking in the FEL with StaxRip?

no

BTW, 6-2 is crashing for me when I try to plot HDR.

In the latest version, I removed the 10nits and 100nits floor so you need to add in your tools folder, the modified version of the dovi_tool linked in the release note.

So I finally got round to do this. Question, though. The files I want to eventually CMv4.0 analyze are HDR10+. The plots are all coming back as dynamic, even though you instructed me to plot the static data (6-2). Is madVR checking the dynamic HDR10+ portion of the video instead of the HDR10 static metadata portion of the video? Is something going wrong? Or will it automatically check the dynamic metadata if the file is HDR10+?

6-2 is useful to find out about the content brightness you're about to generate DV. It helps you select a better MDL, that's it.
In 3-1, any dynamic metadata(only the scene cuts matter) regardless of the source is used for the Shot list during the CM analysis.
Shot list source is selected in this order:

1- any external file with the same filename as the input (rpu, json, text)
2- internal RPU (in case of original rpu that has no shot, add ''IGNORERPU'' in the input filename.)
3- internal hdr10plus
4- if no dynamic metadata is found, it uses madvr to generate a shot list which means that if your source doesn't have any dynamic metadata, you can use the generated RPU from your previous 6-2 measurement.

[Gatorman]

In the latest version, I removed the 10nits and 100nits floor so you need to add in your tools folder, the modified version of the dovi_tool linked in the release note.

Sorry about that. I've added dovi_tool_no_floor. However, 6-2 still crashes. I'm running LAVFilters 0.78.

[RESET_9999]

In the latest version, I removed the 10nits and 100nits floor so you need to add in your tools folder, the modified version of the dovi_tool linked in the release note.

Sorry about that. I've added dovi_tool_no_floor. However, 6-2 still crashes. I'm running LAVFilters 0.78.

does your input filename contain'')''
I just noticed that input with '')'' doesn't work in 6-2. I introduced this bug when I added profile 5 support in 6-2

[Gatorman]

does your input filename contain'')''
I just noticed that input with '')'' doesn't work in 6-2. I introduced this bug when I added profile 5 support in 6-2

There was a ")" in the path. It works fine now. Thank you.

[DjObama]

Yes, the 2018 LG TVs support FEL but indeed, the support in TS/M2TS containers is not great for the Single track rip (makemkv) and the dual track rip will not work.
So the best option for FEL playback on this TV is the MP4 container and DV is processed properly(BL+EL+RPU) as far as I know.

Thank you. Shouldn't it also be possible to mux flac 5.1 audio (converted from dts-hd or truehd) to p7 DT-DL MP4 file?

[RESET_9999]

Thank you. Shouldn't it also be possible to mux flac 5.1 audio (converted from dts-hd or truehd) to p7 DT-DL MP4 file?

yes, but i don't know if the TV supports it, I never tried.

[Hellboy.]

RESET_9999 i seeing movies that say "DV HEVC HYBRID REMUX" with "Dolby Vision Profile 8 Level 6".

1) Is not necessary to encode the movie to add "Dolby Vision Profile 8 Level 6", this are true Remux?
2) Is possible to convert "Dolby Vision Profile 8 Level 6" to BDMV UHD folder "DT-DL"?

Thanks

[staknhalo]

What's this baking the FEL thing?

Just encoding the FEL info into BL and leaving RPU info aside to make profile 7 FEL into profile 8 but with BL still looking fine for ones where it needs EL + BL ?

[tjayz]

I have been trying to ascertain the hype behind it as well.

I have watched Reset's videos on youtube for lldv and understand the difference clearly compated to hdr and sdr but I'm not understanding the advanatages of lldv vs just playing dv p7 FEL in say a x800m2? Does baking it in somehow make the x800 look more like the CX/C2 etc oled internal players? If not, what's the point... simply to not lose FEL in the p7 to p8 conversion?

[RESET_9999]

RESET_9999 i seeing movies that say "DV HEVC HYBRID REMUX" with "Dolby Vision Profile 8 Level 6".

1) Is not necessary to encode the movie to add "Dolby Vision Profile 8 Level 6", this are true Remux?
2) Is possible to convert "Dolby Vision Profile 8 Level 6" to BDMV UHD folder "DT-DL"?

Thanks

1. Hybrid means two sources were used for either the audio/subs or P8 DV metadata. Yes these are true remux as long as they come from the same grade.
2. no

What's this baking the FEL thing?

Just encoding the FEL info into BL and leaving RPU info aside to make profile 7 FEL into profile 8 but with BL still looking fine for ones where it needs EL + BL ?

I have been trying to ascertain the hype behind it as well.

I have watched Reset's videos on youtube for lldv and understand the difference clearly compated to hdr and sdr but I'm not understanding the advanatages of lldv vs just playing dv p7 FEL in say a x800m2? Does baking it in somehow make the x800 look more like the CX/C2 etc oled internal players? If not, what's the point... simply to not lose FEL in the p7 to p8 conversion?

Baking fel is just for the people that use a device that cannot process the EL (shield, atv, zidoo etc..).
Dont waste your time with it if you have a x800m2 or an oppo.

[tjayz]

Baking fel is just for the people that use a device that cannot process the EL (shield, atv, zidoo etc..).
Dont waste your time with it if you have a x800m2 or an oppo.

Thanks for the clarification.

[Trees]

Quick question; when generating CMv4.0 content (3-1), how does one determine what Mastering Display to use? I assuming higher isn't necessarily better?

2 options:

1- just use the static metadata from your source HDR10
2- check the brightness first with madvr. If 95% of the movie is under 1000nits, use 1000nits MDL else, 4000.

Option 2 is better because some movies have a static MDL of 4000nits but the actual brightness is under 1000nits.
A 4000nits RPU is a lot darker than a 1000nits one regardless of the content's actual brightness and in my opinion, 4000nits MDL + low nits content is wrong without L2 trim passes because if you look at the generated(or original) trims with a 4000nits analysis, they brighten/compensate a lot for the darkness a 4000 rpu brings.

https://slow.pics/c/uVX5iFOD

So I finally got round to do this. Question, though. The files I want to eventually CMv4.0 analyze are HDR10+. The plots are all coming back as dynamic, even though you instructed me to plot the static data (6-2). Is madVR checking the dynamic HDR10+ portion of the video instead of the HDR10 static metadata portion of the video? Is something going wrong? Or will it automatically check the dynamic metadata if the file is HDR10+?

Thank you for this!

Baking fel is just for the people that use a device that cannot process the EL (shield, atv, zidoo etc..).
Dont waste your time with it if you have a x800m2 or an oppo.

Thank you again. Do you think the Shield will ever support Dual Layer in the future? Or is it physically not capable of it? Also, do you have an example of a DoVi Baked MediaInfo output? I'm curious to see what it's like.