Dolby Vision now possible through MP4 Mux.

[RESET_9999]

I dont know, but you can always test the original and generated tone mapping with workflow 7-4 and decide which one you prefer.

@RESET_9999 given this:
Since L2 trims are not static, what is the best practice here: generating new metadata or keeping retail RPU?

[LV8HD]

I dont know, but you can always test the original and generated tone mapping with workflow 7-4 and decide which one you prefer.

@RESET_9999 given this:
Since L2 trims are not static, what is the best practice here: generating new metadata or keeping retail RPU?

Wouldn't it be wrong to keep retail?

The movie was mastered at 4000 nits; proven by a HDR analysis, MaxCLL: 4427 nits, MaxFALL: 2325 nits.

On the other hand, Dolby Vision L1 is statically capped at 650 nits. Doesn't this mean that even if a TV hypothetically supported up to 4427 nits, using Dolby Vision would cap all content at 650 nits? Possibly wrongly tonemapped as well.

Generating a new RPU and transferring retail L2 metadata to it can be a solution?

[extranet]

Simple question but probably not a simple answer. I want to rip DV FEL files and keep FEL. Staxrip converts to 8.1 but doesn't keep FEL. I understand with Dovibaker it is possible? But although I've used Avi/Vapoursynth a lot, I'm still not really an expert at working out how to import files to the script. What is the simplest way rip DV FEL and keep FEL?

[RESET_9999]

Wouldn't it be wrong to keep retail?

The movie was mastered at 4000 nits; proven by a HDR analysis, MaxCLL: 4427 nits, MaxFALL: 2325 nits.

On the other hand, Dolby Vision L1 is statically capped at 650 nits. Doesn't this mean that even if a TV hypothetically supported up to 4427 nits, using Dolby Vision would cap all content at 650 nits? Possibly wrongly tonemapped as well.

Generating a new RPU and transferring retail L2 metadata to it can be a solution?

Some colorists prefer to keep L1 static and do most of the work in the trims, and that can work. However, looking at the L2 trims here, they’re not dimming the image very much (gamma brightens and slope dims equally) , and given that this is an insanely bright HDR grade, I’d expect proper CMv4.0 metadata to perform better overall.

That said, I’d still generate a few tone-mapping samples using workflow 7-4 and verify the results. There’s no need to guess anything, it takes about 10 minutes to produce tone-mapping samples with both the original metadata and the generated one, and then you can directly compare the output.

cmv4.0 generated: https://drive.google.com/file/d/1ec1rWd ... drive_link
original: https://drive.google.com/file/d/1VqXaGX ... drive_link

[RESET_9999]

Simple question but probably not a simple answer. I want to rip DV FEL files and keep FEL. Staxrip converts to 8.1 but doesn't keep FEL. I understand with Dovibaker it is possible? But although I've used Avi/Vapoursynth a lot, I'm still not really an expert at working out how to import files to the script. What is the simplest way rip DV FEL and keep FEL?

workflow 8-2-1 in dovi_scripts:
https://forum.doom9.org/showthread.php?t=185317

[extranet]

Simple question but probably not a simple answer. I want to rip DV FEL files and keep FEL. Staxrip converts to 8.1 but doesn't keep FEL. I understand with Dovibaker it is possible? But although I've used Avi/Vapoursynth a lot, I'm still not really an expert at working out how to import files to the script. What is the simplest way rip DV FEL and keep FEL?

workflow 8-2-1 in dovi_scripts:
https://forum.doom9.org/showthread.php?t=185317

Thanks. Maybe there should be a way to extract data from an existing DV 7 file to add to the same file but encoded to DV 8.1? I had a couple of files with both files still present and it might have been quicker rather than having to set up the encoding parameters and re-encode. But at least this preserves FEL Maybe one day this will be incorporated into StaxRip.

[LV8HD]

Some colorists prefer to keep L1 static and do most of the work in the trims, and that can work. However, looking at the L2 trims here, they’re not dimming the image very much (gamma brightens and slope dims equally) , and given that this is an insanely bright HDR grade, I’d expect proper CMv4.0 metadata to perform better overall.

That said, I’d still generate a few tone-mapping samples using workflow 7-4 and verify the results. There’s no need to guess anything, it takes about 10 minutes to produce tone-mapping samples with both the original metadata and the generated one, and then you can directly compare the output.

But as I pointed in the previous post, can I generate a new RPU with dynamic L1, CMv4.0 and transfer L2 trims from the original RPU? Is this going to preserve the colorist intention or is it incompatible with the newly generated L1? If so, I think I am going to stick with the generated metadata since, as you expected, performs better.

[RESET_9999]

But as I pointed in the previous post, can I generate a new RPU with dynamic L1, CMv4.0 and transfer L2 trims from the original RPU?

no