Dolby Vision now possible through MP4 Mux.

[Rororororo]

@RESET_9999

I'm just checking to see what's new in v.2.0.9 and see it provides some new info in 2-2 etc

1st Frame is a Scene Cut: NO(fix with 2-1-1)
Consecutive Scene Cuts: NO (good)

If I understand correctly, I can fix it with "Fix Scene_Refresh_Flag=S"?

[RESET_9999]

the DV metadata (RPU) usually starts with a scene cut flag and this is why when you sync a RPU, you don't remove or duplicate the first frame. Instead, you use the 2nd frame.
It doesn't seem to cause any playback issue but yes, you can edit it with workflow 2-1-1

[Rororororo]

When injecting P7 MEL CMv4.0 to BL would it be possible to add a workflow to output it straight as P8 mkv? I mean without using 4-1 after 1-1

[RESET_9999]

I dont see a use case for that ? Why did you extract the P7 rpu in the first place if you wanted a p8 rpu? just process the original P7 rip into 4-1?
I never had to inject a P7 rpu to a different BL.

[Rororororo]

I dont see a use case for that ? Why did you extract the P7 rpu in the first place if you wanted a p8 rpu? just process the original P7 rip into 4-1?
I never had to inject a P7 rpu to a different BL.

I meant P7 with WEB CMv4.0 bloc from 2-6

[RESET_9999]

I meant P7 with WEB CMv4.0 bloc from 2-6

In that case, just inject the synced cmv4.0 P5 rpu with (1-1) as you would do for any P8 hybrid release. The script will convert P5 to P8.
That's what I do for the MEL P7 movie I want to add the cmv4.0 bloc, no need to transfer the cmv4.0 to P7 for those movies if what you want is P8.

[Rororororo]

I meant P7 with WEB CMv4.0 bloc from 2-6

In that case, just inject the synced cmv4.0 P5 rpu with (1-1) as you would do for any P8 hybrid release. The script will convert P5 to P8.
That's what I do for the MEL P7 movie I want to add the cmv4.0 bloc, no need to transfer the cmv4.0 to P7 for those movies if what you want is P8.

The more you know, thanks!

One thing I noticed, after converting P5 to P8 (Dune: Part Two), the Metafier reports a lot of positive Level 8 lift values. Can these warnings be safely ignored?

Code: Select all

WARNING: Positive Level8 lift value at shot: UniqueID = cde4f9ee-e827-4cc9-80d6-e0a583667ac6 @[6926-7019]
WARNING: Positive Level8 lift value at shot: UniqueID = ee1d2741-c522-43bf-a66e-21e96d1fe3d9 @[7055-7101]
WARNING: Positive Level8 lift value at shot: UniqueID = 2e295c16-58cb-4243-9c30-c4725f4c89b6 @[7381-7434]
WARNING: Positive Level8 lift value at shot: UniqueID = df9739dc-3b5b-4fd8-b46f-bcfa6183d72e @[7634-7857]
WARNING: Positive Level8 lift value at shot: UniqueID = b688ce45-b34a-45e6-8624-26864f72ea11 @[8460-8546]
WARNING: Positive Level8 lift value at shot: UniqueID = fb10dc96-8668-44b5-8b4c-81ea88848eed @[8639-8719]
(...)

[RESET_9999]

those warnings are normal and they are for the colorist who did the metadata.

metafier has two modes:
mode 0 in the script = find offset values over 2048
mode 1 in the script = find offset values over 2100 which causes raised black bars.
but the thing is any offset positive value(over 2048) is ignored by the HDMI players so DV cannot have raised letterbox anyway.

I did some positive lift test files here: https://drive.google.com/drive/u/1/fold ... fx6vRYDEfs

Metafier warnings are fine, errors are not.

[FonduemangVI]

2- Windows Energy Player

whatever problems watching at the computer/windows platform aside - is that the best windows store dv player then outside of any official dv pcs player etc?

and it's only because I know him personally and I know that he always does all the necessary checks.
Some older framestor releases are wrong and I just checked the Captain America hybrid is still available on BHD even though it's a VERY different grade and the RPU is not even in sync with the BL.
Same for their Black Widow release and others.

You can pm the list of hybrids you're not sure and I can have a look if i can find them.

Framestor Mando S02E08 Hybrid UHD out of sync too - prob all the (d+ or iT/D?) stuff

I just had a chance to check Mando and I can't see any sync issue. Can you provide a particular timestamp?

[mulucy]

Life is busy, havent been able to monitor the development of DV. Can someone explain why is it a big deal CMv2.9 vs. CMv4.0? I see the latter mentioned a lot here. I read the official document, but dont understand why its a big deal. Thanks!

[sw5163]

Life is busy, havent been able to monitor the development of DV. Can someone explain why is it a big deal CMv2.9 vs. CMv4.0? I see the latter mentioned a lot here. I read the official document, but dont understand why its a big deal. Thanks!

CM v4.0 provides creators more control over tone mapping, thus it's more accurate when applied properly.
https://professionalsupport.dolby.com/s ... v-4-0-FAQs
https://professionalsupport.dolby.com/s ... tween-them

[LV8HD]

Hi everyone, I'm using cm analyze to calculate MaxCLL and MaxFALL values of a video file.
Unfortunately the cm analyze process gets killed randomly during the measurement thus, making it freeze forever. It must be a bug related to cm analyze itself. Has anyone else experienced this problem when using cm analyze?

Here it is a brief log:

Code: Select all

Drag and drop your file: C:\Muxing\500.Days.of.Summer.2009.WEB-DL.2160p.HDR.mov
Set the Image Aspect Ratio: 2.4

--------------------------------------------------

Starting workflow...

Workflow started

Command being used: "C:\Dolby\DoVi_Scripts\tools\cm_analyze.exe" --bda --source-format "bt2020 pq" --aspect-ratios 1.77777777777777777778 2.4 C:\Muxing\500.Days.of.Summer.2009.WEB-DL.2160p.HDR.mov "C:\Muxing\500.Days.of.Summer.2009.WEB-DL.2160p.HDR.xml"

--------------------------------------------------

Copyright (c) 2013-2024 Dolby Laboratories, Inc. All Rights Reserved
07/18/2024/19:37:30.562000000 CPU: AMD Ryzen 7 7700X 8-Core Processor              (AuthenticAMD) [ mmx mmxext sse sse2 sse3 ssse3 sse41 sse42 sse4a avx avx2 avx512f avx512dq avx512cd avx512bw avx512vl avx512bmi fma ]
07/18/2024/19:37:30.564000000 atom: WARNING Unknown Video Sample Description Extension: pasp
07/18/2024/19:37:30.588000000 quicktime: WARNING ignoring media track of type text
07/18/2024/19:37:30.621000000 atom: WARNING Unknown Video Sample Description Extension: pasp
07/18/2024/19:37:30.647000000 quicktime: WARNING ignoring media track of type text
07/18/2024/19:37:30.661000000 cm_analyze:                Source: 'C:\Muxing\500.Days.of.Summer.2009.WEB-DL.2160p.HDR.mov'
07/18/2024/19:37:30.661000000 cm_analyze:        Master Display: 1000-nit, BT.2020, D65, ST.2084, Full
07/18/2024/19:37:30.661000000 cm_analyze:              Src Info: '3840x2160x3 u16 interleaved 422 le tight 0-136841 23.976fps top_left pq ycbcr_bt2020 video bt2020'
07/18/2024/19:37:30.661000000 cm_analyze:                Frames: 0 - 136841
07/18/2024/19:37:30.661000000 cm_analyze:            Frame rate: 24000/1001
07/18/2024/19:37:30.661000000 cm_analyze:     Algorithm Version: 4
07/18/2024/19:37:30.661000000 cm_analyze:           XML Version: 4.0.2
07/18/2024/19:37:30.669000000 cm_analyze: Metadata aspect ratios: canvas 1.777778e+00, image 2.400000e+00
07/18/2024/19:37:30.670000000 cm_analyze: setting letterbox to (0,280,0,280) based on aspect ratios
07/18/2024/19:37:30.671000000 cuda: initializing CUDA
07/18/2024/19:37:30.747000000 cuda: using CUDA version 9.2.0
07/18/2024/19:37:30.747000000 cuda: NVIDIA GeForce RTX 3060: compute 8.6, cores 3584*1837MHz, memory 12287MB
Frame 18070 complete. Last frame: 0.040 seconds. ETA: 6:18:13.280

[RESET_9999]

yeah, I have the same issue on my Windows 11 PC. I can no longer use cm_analyze, it crashes after about 10 minutes.
Are you on Windows 11? I spent a couple of hours trying to debug it and nothing worked so I suspect a recent Win11 update caused this bug because I'm using the same Nvidia drivers on my Windows 10 PC and there's no issue.

PS: You should use madVR instead anyway, it will be 10 times faster, and no need to convert to prores.

[LV8HD]

yeah, I have the same issue on my Windows 11 PC. I can no longer use cm_analyze, it crashes after about 10 minutes.
Are you on Windows 11? I spent a couple of hours trying to debug it and nothing worked so I suspect a recent Win11 update caused this bug because I'm using the same Nvidia drivers on my Windows 10 PC and there's no issue.

PS: You should use madVR instead anyway, it will be 10 times faster, and no need to convert to prores.

Yup, I'm using Windows 11 latest release:
OS Name: Microsoft Windows 11 Pro
OS Version: 10.0.22631 N/A Build 22631

How can I use MadVR to do that?

[RESET_9999]

you measure HDR with madMeasureHDR.exe and it will tell you maxcll/fall. You can also use workflow 6-2 in dovi_scripts which use madvr.

Code: Select all

madMeasureHDR.exe input.mkv