Yes, the L2 trims are removed by default in (3-1). I watched a couple of CM_analyze generated movies and it looks better than ever.
Is there any way to speed up the process of 3-1. For me it is literally 10x slower than DaVinci. (30min DaVinci, 7-8hour on 3-1)RESET_9999 wrote: ↑Wed Aug 30, 2023 10:05 pm
Yes, the L2 trims are removed by default in (3-1). I watched a couple of CM_analyze generated movies and it looks better than ever.
The latest Dolby algo is much better than the old one that Resolve uses and the fact that we can use HRD10plus scene cuts(or any official ones) is great. example: https://slow.pics/c/3EyCFPu9
The only way is to not touch your PC while CM is running. It takes about 1h and the speed goes from 0.050 to 0.400
The question is how much do you care about the difference between cm_analyze vs. Resolve algorithm output in the final image, or even the (sometimes flawed/lazy/inaccurate) retail DV metadata, which is how 99.9% of the world sees the films, lol. Have you A/B tested a sample or movie yet? I find CM is best at this point, but Resolve is a close 2nd and in a blind-test, you may even end up preferring one or the other for a particular film. RESET is rightly focused on accuracy and upholding the original intent of the colourist/filmmakers as much as possible, but we're still working with approximation and no full Dolby Vision license, keep in mind. As far as the question of speed, Dolby obviously expects people to have dedicated server or workstation for running their pro tools, so your call how much time/resources you want to dedicate to this entire process, especially if you don't get much enjoyment out of the technical details/testing/troubleshooting aspect.thirdmoon wrote: ↑Thu Aug 31, 2023 7:45 amIs there any way to speed up the process of 3-1. For me it is literally 10x slower than DaVinci. (30min DaVinci, 7-8hour on 3-1)RESET_9999 wrote: ↑Wed Aug 30, 2023 10:05 pm
Yes, the L2 trims are removed by default in (3-1). I watched a couple of CM_analyze generated movies and it looks better than ever.
The latest Dolby algo is much better than the old one that Resolve uses and the fact that we can use HRD10plus scene cuts(or any official ones) is great. example: https://slow.pics/c/3EyCFPu9
or in other words, starting to use less and less gpu power... watched it recently, started at 26% GPU usage (LAST FRAME: 0.05s), and in one third of the analysis, it was down to 12% (LAST FRAME: 0.6s). 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.
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.RESET_9999 wrote: ↑Thu Aug 31, 2023 2:52 pmThe 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.
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.
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.RESET_9999 wrote: ↑Thu Aug 31, 2023 3:21 pmyeah 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.
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.thirdmoon wrote: ↑Mon Sep 04, 2023 9:24 amSource - 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.
Hello,Amused wrote: ↑Fri Aug 05, 2022 7:02 amI 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.