Thanks. Yeah, I made a little patch for dovi_tool to verify. The patch corrects the frame indexes, and my patched version generated the same output RPU as dovi_tool 2.1.3, so there must be some normalization of the indexes in a spot of code I didn't check.
Edit: Or maybe, as it appears, there is no frame index in the RPU output. Each frame just has its data, so the index doesn't matter. The data is sequential by nature. So, not clear on why it mattered for HDR10+ -> DV generation.
Actually, that clipping behavior with content brighter than the RPU MDL just got patched in cpm's coreelec build so if you use one of the CE devices, you can now do my initial suggestion of using 1000nits MDL if 10% or less is over 1000nits. Either way, 1000nits is the correct selection for that Seinfeld episode plot but I've seen other episode's plots that spiked to 10 000nits..
If your player is the x800m2/x700 or oppo, then you should respect the mediainfo MDL if there's a shot over the RPU MDL. These 3 players (probably all the bluray players) are altering the RPU that is being sent to the TV. They limit the L1 metadata to the RPU MDL causing the clipping when the content is brighter. In other words, the rpu response differences we noticed years ago between devices are finally explained.
The new CE update removed that limitation so now it sends original metadata to the display and processes the metadata identically to the TV internal player(or the shield and appleTV).
If the content is graded within the MDL, then all of this is pretty much meaningless but there's one even better thing that this update brought. It has enabled the Level 5 metadata and the positive offset lift that never worked on any HDMI device so far. Positive Lift metadata are frequently used in most movies. So this update brought an already great device to perfection levels.
I'm using the Ugoos AM6B+ with the latest nightly build 21.2-Omega. Does this update mean anything? How do I get it?
It's very unlikely. The CE team will hate CPM regardless of how good his builds are. You can't even mention his name on the CE forum; they will censor you.
You have all the info you need to get everything working in the links posted here.
It's very unlikely. The CE team will hate CPM regardless of how good his builds are. You can't even mention his name on the CE forum; they will censor you.
You have all the info you need to get everything working in the links posted here.
So after updating to this CPM build, I shouldn't update to future CE build?
And since this update enables L5 on the Ugoos, when transfering DV to HDR10 bluray file, I need to edit L5 when necessary now?
I just tested the 4 files outside the real content folder and saw no change in brightness at all. The one inside the real content folder with the screenshot you posted showed brightness change, but only the 4000 nit file, not the 1000 nit one.
So after updating to this CPM build, I shouldn't update to future CE build?
And since this update enables L5 on the Ugoos, when transfering DV to HDR10 bluray file, I need to edit L5 when necessary now?
doing L5 correctly is always part of all my tutorials, so if L5 is not set correctly, it will cause issues...
I just tested the 4 files outside the real content folder
the steps test files? they raise lift gradually, you should see a major change, especially over 2600.
Any file in that folder shows a difference on my C2, but of course, the effect is always more evident with a 4000nits RPU.
the steps raise positive lift gradually so it is normal if you don't notice change until it reach 2600+
if it was going from 2048(0) to 2100, you would see a slight change but in the test file, it goes from 2048 to 2055 to 2065 to 2075 to 2085 to 2095 to 2100 etc so you don't really notice the difference between 2095 and 2100. If you don't see it changing after 3079, then there is a problem
the steps raise positive lift gradually so it is normal if you don't notice change until it reach 2600+
if it was going from 2048(0) to 2100, you would see a slight change but in the test file, it goes from 2048 to 2055 to 2065 to 2075 to 2085 to 2095 to 2100 etc so you don't really notice the difference between 2095 and 2100. If you don't see it changing after 3079, then there is a problem
Yeah no change at all. Are my dolby vision settings below correct? When I first updated to this cpm build, I noticed dolby vision was disabled by default. The settings also look different compared to CE build.
Just update to cpm build then put this command in via putty right? No other steps?
nano /storage/.config/autostart.sh
(
echo Y > /sys/module/amdolby_vision/parameters/dolby_vision_keep_source_meta_level_5
)&
Last edited by deadchip12 on Tue Jan 28, 2025 1:46 pm, edited 1 time in total.
not sure how it's possible if L5 works...
I'm using CPM's compiled build(private) while you're using the build(public) compiled by someone else so maybe he did something wrong, I don't know.
Everything works on my end. Try A13
not sure how it's possible if L5 works...
I'm using CPM's compiled build(private) while you're using the build(public) compiled by someone else so maybe he did something wrong, I don't know.
Everything works on my end. Try A13
Just tried A13. Still the same. No change in brightness.
