Dolby Vision now possible through MP4 Mux.

[dapope]

And I'm having another problem, this time with 3-1.
Using the version from a couple of days ago I could agree to manual L5 entry, Dovi_scripts would then give me the suggested L5 settings to enter for that file.
Now it started giving me an error that .avs had no file association.
I switched the file association to notepad and it just opens this document, note that it always reads 0,2.5,255,0,255 regardless of the aspect ratio.
https://imgur.com/a/SvmMVCE

[RESET_9999]

OK done.
Do you think you could please help me make sense of this DV vs HDR graph as I'm looking for FEL brightness extension?
https://slow.pics/c/mzG9Nk9K
HDR reports a higher maxFALL, however DV reports a higher average maxCLL.
When I use 4-2 to convert the file to Profile 8 it produces an identical DV plot as the Profile 7 file... Which is confirmation that there's no FEL brightening, correct?
So why does it report a higher average maxCLL than HDR?

Thanks!

Dolby and madvr avg_pq (maxfall) is calculated differently and will never be the same so those values can be ignored.
When you convert P7 to P8, it doesn't change the metadata, so it will always be the same as the original P7 L1.
To find expanded brightness video, export screenshots in 7-1 or look for comparisons here (I did not check Carrie though but by the look of the plot, it doesn't expand luminance):
https://docs.google.com/spreadsheets/d/ ... =917134052

And I'm having another problem, this time with 3-1.
Using the version from a couple of days ago I could agree to manual L5 entry, Dovi_scripts would then give me the suggested L5 settings to enter for that file.
Now it started giving me an error that .avs had no file association.
I switched the file association to notepad and it just opens this document, note that it always reads 0,2.5,255,0,255 regardless of the aspect ratio.
https://imgur.com/a/SvmMVCE

Yes, this is normal.
I removed the L5 suggestions in the manual mode and now the script will launch avspmod with a black level tweak that makes manual cropping a LOT easier, especially for dark movies.
Levels(0, 2.5, 255, 0, 255, coring=false) is not the L5 but parameters that raise black levels(inspired by staxrip latest build).

If you were blindly using the suggestion in the manual mode, then just use the Auto mode and it will be the same as before.

[RESET_9999]

btw, I got a response from Dolby about the Cm_analyze.exe slow performance:

Our Professional Tools make use of Apple’s ProRes decoding library and we have identified performance bugs, including lack of GPU accelerated decoding on Windows and Linux, and a severe performance hit when running on some AMD chips, including their high-performance scalable EPYC chips.

Unfortunately, we are dependent on Apple updating their ProRes libraries to get this fixed.
Until we get an update from Apple, the only recommendation we can offer is to use JPEG2000 which has full GPU decoding support.

I'm sorry I can't give you any better news.
Let me know if there's anything else we can support with.

Thanks,

Michael

[dapope]

Yes, this is normal.
I removed the L5 suggestions in the manual mode and now the script will launch avspmod with a black level tweak that makes manual cropping a LOT easier, especially for dark movies.
Levels(0, 2.5, 255, 0, 255, coring=false) is not the L5 but parameters that raise black levels(inspired by staxrip latest build).

If you were blindly using the suggestion in the manual mode, then just use the Auto mode and it will be the same as before.

OK got all of this, thanks. I think for now the only thing I can't figure out is how to get those heatmaps. Dovi_scripts says "creating heatmap" but there's never any output. I've tried installing python to the default install location in appdata/local/programs and ran pip install numpy colour-science opencv-python-headless. But I don't really know what I'm doing with python.

[RESET_9999]

OK got all of this, thanks. I think for now the only thing I can't figure out is how to get those heatmaps. Dovi_scripts says "creating heatmap" but there's never any output. I've tried installing python to the default install location in appdata/local/programs and ran pip install numpy colour-science opencv-python-headless. But I don't really know what I'm doing with python.

did you also pip install:
cv2/colour/matplotlib/scikit-image

[dapope]

OK got all of this, thanks. I think for now the only thing I can't figure out is how to get those heatmaps. Dovi_scripts says "creating heatmap" but there's never any output. I've tried installing python to the default install location in appdata/local/programs and ran pip install numpy colour-science opencv-python-headless. But I don't really know what I'm doing with python.

did you also pip install:
cv2/colour/matplotlib/scikit-image

How do I do that? python -m pip install cv2/colour/matplotlib/scikit-image does not work.

[RESET_9999]

install them one by one??
pip install scikit-image
etc...

[dapope]

install them one by one??
pip install scikit-image
etc...

Haha I thought that you writing out a directory. I didn't realise they were separate items.
It's working now!
For anyone following after me, to install cv2 you don't install cv2, you install opencv-python (I don't really know what that means but there you go). like so: python -m pip install opencv-python.
Also I think you have to add Python to your PATH variables:
https://www.youtube.com/watch?v=AMAE0S_NzxE

[dapope]

@RESET_9999
Does this show that Carrie.1976 has brightness expanded via FEL (by a very small amount)?
https://slow.pics/c/093yE6ed

[RESET_9999]

Not really. FEL improves grain which probably affects the pixels reading a bit.

When fel expands brightness, you won't have any doubt:
https://slow.pics/c/dCcoN9UP
https://slow.pics/c/IQmKJTCY

[Trees]

Quick question; when generating CMv4.0 content (3-1), how does one determine what Mastering Display to use? I assuming higher isn't necessarily better?

[RESET_9999]

Quick question; when generating CMv4.0 content (3-1), how does one determine what Mastering Display to use? I assuming higher isn't necessarily better?

2 options:

1- just use the static metadata from your source HDR10
2- check the brightness first with madvr. If 95% of the movie is under 1000nits, use 1000nits MDL else, 4000.

Option 2 is better because some movies have a static MDL of 4000nits but the actual brightness is under 1000nits.
A 4000nits RPU is a lot darker than a 1000nits one regardless of the content's actual brightness and in my opinion, 4000nits MDL + low nits content is wrong without L2 trim passes because if you look at the generated(or original) trims with a 4000nits analysis, they brighten/compensate a lot for the darkness a 4000 rpu brings.

https://slow.pics/c/uVX5iFOD

[Trees]

Quick question; when generating CMv4.0 content (3-1), how does one determine what Mastering Display to use? I assuming higher isn't necessarily better?

2 options:

1- just use the static metadata from your source HDR10
2- check the brightness first with madvr. If 95% of the movie is under 1000nits, use 1000nits MDL else, 4000.

Option 2 is better because some movies have a static MDL of 4000nits but the actual brightness is under 1000nits.
A 4000nits RPU is a lot darker than a 1000nits one regardless of the content's actual brightness and in my opinion, 4000nits MDL + low nits content is wrong without L2 trim passes because if you look at the generated(or original) trims with a 4000nits analysis, they brighten/compensate a lot for the darkness a 4000 rpu brings.

https://slow.pics/c/uVX5iFOD

Thank you for your reply.

How do I check the brightness? Can I not plot the file with Dovi_Scripts to check the brightness? I've managed to install both MPC-BE and madVR, but whenever I play the file I want to add DV to, it will just play. I've also checked the madVR options, but nothing. Or is it a command line-only thing?

[RESET_9999]

6-2 is the workflow to measure HDR with madvr.

[dapope]

Quick question; when generating CMv4.0 content (3-1), how does one determine what Mastering Display to use? I assuming higher isn't necessarily better?

2 options:

1- just use the static metadata from your source HDR10
2- check the brightness first with madvr. If 95% of the movie is under 1000nits, use 1000nits MDL else, 4000.

Option 2 is better because some movies have a static MDL of 4000nits but the actual brightness is under 1000nits.
A 4000nits RPU is a lot darker than a 1000nits one regardless of the content's actual brightness and in my opinion, 4000nits MDL + low nits content is wrong without L2 trim passes because if you look at the generated(or original) trims with a 4000nits analysis, they brighten/compensate a lot for the darkness a 4000 rpu brings.

https://slow.pics/c/uVX5iFOD

If you have a display with a max brightness under 1000 nits, is there any point to using the 4000 nits option?