Dolby Vision now possible through MP4 Mux.

[RESET_9999]

but we're still working with approximation and no full Dolby Vision license, keep in mind.

The license is useless and only needed for manual L2/L8 trim passes. Even if I had a license I would still remove the trims.
The only difference with the original DV that has no trims is the blended shots and scene cuts.

[skull88]

but we're still working with approximation and no full Dolby Vision license, keep in mind.

The license is useless and only needed for manual L2/L8 trim passes. Even if I had a license I would still remove the trims.
The only difference with the original DV that has no trims is the blended shots and scene cuts.

Agreed, what I meant was that we're only able to do so much, and we're not trying to actually replace the proper colourist/grading work that is ideally completed (including additional trims etc.). Leaving the higher L2 trims besides 100-nits from Resolve or other automated analysis is actually changing the image significantly, which I agree we should not do.

And jlpsvk, it doesn't seem to be related to CUDA, but possibly certain proRes files or another bug to do with CPU scheduling or something like that, it also happens when CPU-only run is forced. Most movies run fast for me entire run, even when using my PC, as long as I leave CM window open/foreground. Some slow down no matter what I do.

[RESET_9999]

Most movies run fast for me entire run, even when using my PC, as long as I leave CM window open/foreground. Some slow down no matter what I do.

yeah Windows 10 seem more stable with CM. On my Win11 I just cant touch my PC. Even browsing the web on firefox will slow down the analysis.
I doubt the problem is the prores file since the same file works at full speed in resolve. The script use a very old version of ffmpeg though(because of the audio 5.0 bug) so It might worth testing with the latest ffmpeg.

[skull88]

Most movies run fast for me entire run, even when using my PC, as long as I leave CM window open/foreground. Some slow down no matter what I do.

yeah Windows 10 seem more stable with CM. On my Win11 I just cant touch my PC. Even browsing the web on firefox will slow down the analysis.
I doubt the problem is the prores file since the same file works at full speed in resolve. The script use a very old version of ffmpeg though(because of the audio 5.0 bug) so It might worth testing with the latest ffmpeg.

Ah, interesting. I think all the files I have done proRes conversion independently first in Staxrip using ffmpeg newer version have not slowed down in cm, so you could be onto something? I might do that now anyway and will report if I get another video that slows down reliably and can try to send sample to compare. Cheers.

[thirdmoon]

Source - Prometheus.2012.COMPLETE.UHD.BLURAY

Script Used - DoVi_Scripts_1.9.2.6.beta_MKV
Comparison - https://slow.pics/c/ls8wBmji

Image 1 = CM Analyze Latest - 7 hours (Left it overnight without interference)
Image 2 =1080p Cubic Scaling (DaVinci) - 30min
(Ryzen 5 3600, GTX 1660ti Win10)

I tested the 1080p Cubic scaling DV and CM analyze DV on my TV (Sony 65X80K), and I couldn't personally tell any difference for this particular movie.
Also, 3-1 clipped that 600nit highlight (between 10,000-20,000frame) to 400nit which isn't really helpful?

I will be testing with Expendables 2010 which has higher overall brightness. Will update.

Still not able to see the benefit of 3-1. Genuine doubt.

[RESET_9999]

Source - Prometheus.2012.COMPLETE.UHD.BLURAY

Script Used - DoVi_Scripts_1.9.2.6.beta_MKV
Comparison - https://slow.pics/c/ls8wBmji

Image 1 = CM Analyze Latest - 7 hours (Left it overnight without interference)
Image 2 =1080p Cubic Scaling (DaVinci) - 30min
(Ryzen 5 3600, GTX 1660ti Win10)

I tested the 1080p Cubic scaling DV and CM analyze DV on my TV (Sony 65X80K), and I couldn't personally tell any difference for this particular movie.
Also, 3-1 clipped that 600nit highlight (between 10,000-20,000frame) to 400nit which isn't really helpful?

I will be testing with Expendables 2010 which has higher overall brightness. Will update.

Still not able to see the benefit of 3-1. Genuine doubt.

CM_Analyse with L1 tuning is the latest version of the Dolby Algo which evolved a lot since Dolby was created. It went from fully dynamic with very aggressive/higher L1 values to lower & less dynamic metadata(10nits/1000nits floor). I wonder if they did that because of the complaints you often hear about DV being darker than HDR10.

With dark movies like Expendables and Prometheus, the difference is small. You'll notice a more significant difference with a brighter movie like in the example below.

Higher L1 means:
- more tone mapping, less clipping, darker image compared to HDR10
Lower L1 means:
-less tone mapping, *more clipping, brighter image closer to HDR10
* more clipping only if your TV is not capable of displaying the actual brightness. Basically, it just means that the image is displayed with less tone mapping, similar to static HDR10.

And here's a direct comparison using my x800m2 and an HDMI capture card:
PQ: https://slow.pics/c/vnEnoTiU
Plot: https://slow.pics/c/3QzuYren

the main benefit of CM:
- you can use official studios scene cuts.
- latest/best version of the Dolby algo
- Black metadata improved
- No need to use some strange resolve settings (1080p cubic)
- CLI tool. can be scripted/batch mode.

Not sure why it's still slow even when you don't touch your PC because I did 5 movies last night in batch mode with workflow (3-2) and some movie does indeed take more time but nothing close to your 7h
These time results include: Prores conversion, CM analyse, demuxing, Injection and mixing.



first movie took about 1h30 to process
2nd 1h20
3rd : took 3h
4th: took 2h
5th: took 1h20

[thirdmoon]

Thanks for the clarification @RESET_9999

I will test some brighter movies. Also will test the force CPU function, I think that might make a difference.

[RESET_9999]

it slow down with the CPU too and overall, much slower than using the GPU cuda

[V.Florin]

I have the Philips HDMI Sync Box between the tv and both players (Sony and Zidoo). The Sync Box synchronizes the lights of different Philips hue products to the image on the screen.

The Sync Box works with Dolby Vision only if it’s player-led (LLDV). It doesn’t work with TV-led Dolby Vision, unless I switch on the “Dolby Vision Enhanced compatibility” option inside the Sync Box settings. This option basically forces the player to switch to LLDV and then the lights work. So if the Hue lights sync without the DV enhanced compatibility option checked - it’s player-led DV. If they don’t work - it’s TV-led DV.

Hello,
Can you explain me (step by step) how you connect each device with the other one?
I wish to make a sync hue lights also.

[Gatorman]

@RESET_9999

I'm happy to see you're taking donations. Thank you for taking the time to consistently update your script.

To anyone who is looking for the link, it's in the TOOLS_README doc.

https://docs.google.com/document/d/1JQF ... p=drivesdk

[RESET_9999]

[Trees]

I'm trying to get a brightness plot of this:

HDR format :
Dolby Vision, Version 1.0, dvhe.08.07, BL+RPU, HDR10 compatible / SMPTE ST 2094 App 4, Version 1, HDR10+ Profile B compatible

I've used various versions of Dovi Scripts with various errors.

Is it not possible to plot Profile 8 Level 7 DV? I do not see Level 7 in DoVi_Scripts_1.9.2_MKV workflow 6-2-3/4/5.

Any guidance to plot said DV would be great.

Also, where would the plots be stored? In the same folder as the source MKV/MP4 or?

Thanks!

[RESET_9999]

I'm trying to get a brightness plot of this:

HDR format :
Dolby Vision, Version 1.0, dvhe.08.07, BL+RPU, HDR10 compatible / SMPTE ST 2094 App 4, Version 1, HDR10+ Profile B compatible

I've used various versions of Dovi Scripts with various errors.

Is it not possible to plot Profile 8 Level 7 DV? I do not see Level 7 in DoVi_Scripts_1.9.2_MKV workflow 6-2-3/4/5.

Any guidance to plot said DV would be great.

Also, where would the plots be stored? In the same folder as the source MKV/MP4 or?

Thanks!

6-2-3 can plot any dv file.
It sounds like you're missing tools (check your pm). The default output path is the dovi_script folder so the graph picture will be in there.

[Trees]

I'm trying to get a brightness plot of this:

HDR format :
Dolby Vision, Version 1.0, dvhe.08.07, BL+RPU, HDR10 compatible / SMPTE ST 2094 App 4, Version 1, HDR10+ Profile B compatible

I've used various versions of Dovi Scripts with various errors.

Is it not possible to plot Profile 8 Level 7 DV? I do not see Level 7 in DoVi_Scripts_1.9.2_MKV workflow 6-2-3/4/5.

Any guidance to plot said DV would be great.

Also, where would the plots be stored? In the same folder as the source MKV/MP4 or?

Thanks!

6-2-3 can plot any dv file.
It sounds like you're missing tools (check your pm). The default output path is the dovi_script folder so the graph picture will be in there.

Thank you ever so much! it worked straight away!

Quick question:

Why isn't converting HDR10+ to Dolby Vision not recommended? Is this because the Dolby Algorithm is just better or are there other reasons?

[speeddemon]

Why isn't converting HDR10+ to Dolby Vision not recommended? Is this because the Dolby Algorithm is just better or are there other reasons?

Because you can now supply an HDR10+ file to the 3-1 process which will provide you with a Dolby Vision file using Dolby's latest algorithm and the original HDR10+ scene cuts, which is better.