@RESET_9999 Just wanted to say thanks for the Dolby_vision_stuff sheet but I just noticed that the link is broken. Is the sheet hosted somewhere else now? Thanks again!
Yeah, I'm stupid. I was making space in my Google Drive and deleted a folder that contained the Excel sheet. I did a backup recently, so only one month of data is missing.
the new link in my signature should work
thanks but unfortunately, the Google Drive account was created with a VERY old email address(hotmail.com) I no longer have access and they require email verification.
This still means that cmv4.0 isn't supported, right? Just want to be sure.
How should I convert the RPU to be the most compatible with my setup?
yes this file has a cmv2.9 fallback metadata block. If your devices don't support cmv4.0, you don't have to worry about any of this and any RPU work fine.
This still means that cmv4.0 isn't supported, right? Just want to be sure.
How should I convert the RPU to be the most compatible with my setup?
yes this file has a cmv2.9 fallback metadata block. If your devices don't support cmv4.0, you don't have to worry about any of this and any RPU work fine.
what devices did you try?
Just on my trusty old Philips TV 65oled934 (2019).
Then on a LG G3 with dune premier pro running corelec I get everything when set to player led. With tv led I don't see any trims unfortunately, but this is expected, right?
Then on a LG G3 with dune premier pro running corelec I get everything when set to player led. With tv led I don't see any trims unfortunately, but this is expected, right?
No, cmv4.0 should work with TV-LED. CE player-led supports only cmv2.9. (at least on the ugoos)
Your G3 TV internal DV config is probably higher than 1000nits so the trims are probably ignored when the RPU MDL is 1000nits. Make sure that you use the test files that say ''4000-MDL''
Then on a LG G3 with dune premier pro running corelec I get everything when set to player led. With tv led I don't see any trims unfortunately, but this is expected, right?
No, cmv4.0 should work with TV-LED. CE player-led supports only cmv2.9. (at least on the ugoos)
Your G3 TV internal DV config is probably higher than 1000nits so the trims are probably ignored when the RPU MDL is 1000nits. Make sure that you use the test files that say ''4000-MDL''
will any cmv4.0 rpu have an cmv2.9 fallback or do I have to inject one?
Also my Philips TV 65oled934 has 800nit peak brightness. Don't I have to add a 800nit trim to the RPU to get the most brightness out of it?
Sorry for the dumb questions, seems I'm still not getting it.
@RESET_9999 Just wanted to say thanks for the Dolby_vision_stuff sheet but I just noticed that the link is broken. Is the sheet hosted somewhere else now? Thanks again!
Yeah, I'm stupid. I was making space in my Google Drive and deleted a folder that contained the Excel sheet. I did a backup recently, so only one month of data is missing.
the new link in my signature should work
yes all cmv4.0 movies have cmv2.9 fallback metadata. Your G3 + CE device should support cmv4.0.
Don't I have to add a 800nit trim to the RPU to get the most brightness out of it?
All the trims(100-600-1000) work together and the metadata can be extrapolated to any target brightness.
Cool, what would be the best way to create dv from hdr10 cm_analyzer or davinci resolve?
My primary device is still the cmv2.9 Philips TV 65oled934.
What I want is to create cmv4.0 DV Profile 8 with most compatibility for my my old philips tv while future proof for device like LG G3 and up as I share content with multiple deolby vision devices.
Cool, what would be the best way to create dv from hdr10 cm_analyzer or davinci resolve?
CM is 100% automated but can be slow and relies on madvr for the scene-cut detection
Resolve is not automated but is much faster and has slightly better scene-cut detection.
Cool, what would be the best way to create dv from hdr10 cm_analyzer or davinci resolve?
CM is 100% automated but can be slow and relies on madvr for the scene-cut detection
Resolve is not automated but is much faster and has slightly better scene-cut detection.
got you, I trying out both now. I'm on macos, so I'm running windows in parallels and davinci on macos.
what about comatibility with cmv2.9, any difference there?
What is the use case for "Transfer RPU levels" workflow 2-3?