Dolby Vision now possible through MP4 Mux.

[speeddemon]

Do you/we have any idea why they're doing this?
Is it better to just watch in HDR instead of DV for movies with FEL expansion if a FEL compatible player isn't an option?
Would it be possible to re-write the L1/L2 metadata so it's corrected/"unexpanded"?

4 options:
1- just watch in HDR10
2- bake the EL into the BL
3- generate a proper RPU in resolve for the BL actual brightness.
4- get a proper player

Expanding the brightness makes sense actually. It futureproofs the grade for when the TV will be brighter and it makes the content accurate on more type(brightness, HDR format) of display.

Because this way, people with brighter DV TV(G3) can enjoy brighter HDR and people with low nits DV TV can also get an accurate picture thanks to the trim pass and L1.
Then, people with HDR10-only TVs (low nits) can also get an accurate image with the 1000nits BL. If the BL was as bright as the EL, then those low-nits HDR10 TVs would look bad/clipped.

For a UHD BD like Back to the Future with both Expand Brightness FEL and HDR10+, do you feel it would be better to convert HDR10+ to DoVi with your tools or generate an RPU in Resolve?

[RESET_9999]

IMO, It's better to generate a new RPU in resolve because:

1- if you use hdr10plus, your min_pq will always be 0
2- HDR10plus avg_pq is VERY different than what Dolby Vision produces. DV has some specific calculations for the avg_pq.
3- with Resolve, you can make true CMV4.0 metadata (with L3) which improves tone mapping.

[speeddemon]

IMO, It's better to generate a new RPU in resolve because:

1- if you use hdr10plus, your min_pq will always be 0
2- HDR10plus avg_pq is VERY different than what Dolby Vision produces. DV has some specific calculations for the avg_pq.
3- with Resolve, you can make true CMV4.0 metadata (with L3) which improves tone mapping.

Thanks! Understood.

Another question... have you done much research yet comparing Resolve Analyzed output with typical metadata that includes L2/L8 trims?

[RESET_9999]

Another question... have you done much research yet comparing Resolve Analyzed output with typical metadata that includes L2/L8 trims?

Yes
For some reason, resolve does not export the L8 trims similar to when you set your project to cmv2.9 which does not export L2.
So for the resolve cmv4.0 output, a cmv4.0 device won't have any trims effect: only L1 + L3 but for a cmv2.9 device, automatic L2 trims will brighten everything below the tv capabilities and darken every thing above.

BTW, I think only one time I've seen an actual CMV4.0 rpu with active L8... strangely, everything else doesn't have any L8 trim or it's set to 2048 no effect.
There's a bunch of test files in my GD in which you can test pretty much everything DV related.
https://drive.google.com/drive/u/1/fold ... V0E3VVkhiC

[speeddemon]

So for the resolve cmv4.0 output, a cmv4.0 device won't have any trims effect: only L1 + L3 but for a cmv2.9 device, automatic L2 trims will brighten everything below the tv capabilities and darken every thing above.

Is the L2 part actually true for both CMv2.9 and CMv4 analysis when outputting both when outputting CMv2.9 or CMv4? Or, do you just strip the L2 trims when processing with your script anyways?

[RESET_9999]

part actually true for both CMv2.9 and CMv4 analysis when outputting both when outputting CMv2.9 or CMv4? Or, do you just strip the L2 trims when processing with your script anyways?

trims are reset to 0 or removed depending on your script configuration. You can set the script to keep the trims but by default, they are overwritten as explained a couple of days ago in this thread

[speeddemon]

part actually true for both CMv2.9 and CMv4 analysis when outputting both when outputting CMv2.9 or CMv4? Or, do you just strip the L2 trims when processing with your script anyways?

trims are reset to 0 or removed depending on your script configuration. You can set the script to keep the trims but by default, they are overwritten as explained a couple of days ago in this thread

And you recommend the trims being overwritten for the reasons you stated earlier, correct?

But, just to make sure I understand correctly, can you confirm the following with regards to Resolve?

1. CMv2.9 Analysis & CMv2.9 output = L1
2. CMv4 Analysis & CMv2.9 output = L1+L2
3. CMv4 Analysis & CMv4 output = L1+L3 in CMv4 or L1+L2 in CMv2.9 Fallback

[RESET_9999]

And you recommend the trims being overwritten for the reasons you stated earlier, correct?

But, just to make sure I understand correctly, can you confirm the following with regards to Resolve?

1. CMv2.9 Analysis & CMv2.9 output = L1
2. CMv4 Analysis & CMv2.9 output = L1+L2
3. CMv4 Analysis & CMv4 output = L1+L3 in CMv4 or L1+L2 in CMv2.9 Fallback

That's correct.
Actually, the L8 100nits trim is exported but it's set to 0 and obviously not useful to DV playback.

[speeddemon]

And you recommend the trims being overwritten for the reasons you stated earlier, correct?

But, just to make sure I understand correctly, can you confirm the following with regards to Resolve?

1. CMv2.9 Analysis & CMv2.9 output = L1
2. CMv4 Analysis & CMv2.9 output = L1+L2
3. CMv4 Analysis & CMv4 output = L1+L3 in CMv4 or L1+L2 in CMv2.9 Fallback

That's correct.
Actually, the L8 100nits trim is exported but it's set to 0 and obviously not useful to DV playback.

Which of these typically look most accurate to the original Profile 7?

[valington]

And you recommend the trims being overwritten for the reasons you stated earlier, correct?

But, just to make sure I understand correctly, can you confirm the following with regards to Resolve?

1. CMv2.9 Analysis & CMv2.9 output = L1
2. CMv4 Analysis & CMv2.9 output = L1+L2
3. CMv4 Analysis & CMv4 output = L1+L3 in CMv4 or L1+L2 in CMv2.9 Fallback

That's correct.
Actually, the L8 100nits trim is exported but it's set to 0 and obviously not useful to DV playback.

Reset may be you could do one of your scripts without DRAG AND DROP where we could just put file into the folder and choose programm we need

[RESET_9999]

Which of these typically look most accurate to the original Profile 7?

depends on how the original p7 is I guess? (cmv2.9 or cmv4.0 / trims or not)
the best you can hope as I said, is cmv4.0 without trims and no point using anything else

[RESET_9999]

Reset may be you could do one of your scripts without DRAG AND DROP where we could just put file into the folder and choose programm we need

this won't happen.
Drag and drop is a much better approach because your input can be anywhere in your PC (different drives)

[dapope]

@RESET_9999

Salut, sorry for the maybe silly question but how do I get a DV P8 when baking in FEL using your 6-9 workflow? In changelog you say you added in option to export in DV but I still only get option for HDR or SDR.

[RESET_9999]

@RESET_9999

Salut, sorry for the maybe silly question but how do I get a DV P8 when baking in FEL using your 6-9 workflow? In changelog you say you added in option to export in DV but I still only get option for HDR or SDR.

P7 rpu will be converted to P8 automatically so once the encoding is completed, just remux the hevc with mkvtoolnix or tsmuxer and DV P8 will be present.

[dapope]

@RESET_9999

Salut, sorry for the maybe silly question but how do I get a DV P8 when baking in FEL using your 6-9 workflow? In changelog you say you added in option to export in DV but I still only get option for HDR or SDR.

P7 rpu will be converted to P8 automatically so once the encoding is completed, just remux the hevc with mkvtoolnix or tsmuxer and DV P8 will be present.

Ok, thanks very much! Is there an easy way to tell for myself what FEL titles have this issue?