Ok, I did more testing. It turns out the problem is the x265.exe settings used for the BL regardless of the RPU
The original pattern from the spears and munsil disc = bug on the shield
Re-encoded with x265.exe in multiples ways: in BT2020 or P3, chroma type 2 or not, default or custom slow preset settings, --uhd-bd or not = bug on the shield
Re-encoded in resolve (just regular HDR10, dont even need to be 8.1) with any RPU = no bug
Very weird, I give up...
deadchip12 wrote: Thu May 26, 2022 11:32 pm
Could someone briefly explain what were being discussed in the last few pages? The x700/x800m2 bluray player seem like the ultimate devices for playing back dolby vision files, so what else need to be discussed? I'm just curious, not complaining or anything. Are people trying to make it work on other devices?
Just trying to figure out the shield colors issues.
RESET_9999 wrote: Thu May 26, 2022 11:52 pm
Ok, I did more testing. It turns out the problem is the x265.exe settings used for the BL regardless of the RPU
The original pattern from the spears and munsil disc = bug on the shield
Re-encoded with x265.exe in multiples ways: in BT2020 or P3, chroma type 2 or not, default or custom slow preset settings, --uhd-bd or not = bug on the shield
Re-encoded in resolve (just regular HDR10, dont even need to be 8.1) with any RPU = no bug
However the file I used (multi pattern DV P8.ts) is not the same as the Resolve encode. It has more artifacts.
So either Resolve processed the image or something else.
quietvoid wrote: Fri May 27, 2022 1:27 am
However the file I used (multi pattern DV P8.ts) is not the same as the Resolve encode. It has more artifacts.
So either Resolve processed the image or something else.
thank you
Just tried and the same bug as all the files I did
Okay, another couple of questions. First, I've seen reference to converting P5 to P8 to create "hybrid" streams using the HDR10 BL from the UHD blu-ray combined with the Dolby Vision data available via streaming. Is this ~always the best approach where possible, or are there cases where the blu-ray has scenes encoded at different brightnesses than the streaming base layer, making a madVR measurement the better choice?
Second, if I have a UHD blu-ray of Mulan (2020) along with a Disney+ subscription, is there any way I can capture the RPU metadata myself? E.g., can it be extracted from the streamed data, or is it DRM'd along with the video stream? Is there any tool that can capture the RPU by snooping on a TV-led DV HDMI signal? If not, is there a repository of DV RPU metadata extracted from such sources, or would I have to find a full copy of the streaming version somewhere and extract the RPU from that?
RESET_9999 wrote: Fri May 27, 2022 2:54 am
no bug for that one.
So it means there's an issue in the source that Resolve somehow manages to fix, and it's only affecting the Shield.
So weird...
Not necessarily, I had changed an encoding setting.
Same settings with the non-Resolve video: https://0x0.st/oB-c.mkv
If that still has issues, then not sure.
The only difference in the Resolve image is that I can't seem to match chroma alignment, and it has less banding in the blue part.
quietvoid wrote: Fri May 27, 2022 3:06 am
Same settings with the non-Resolve video: https://0x0.st/oB-c.mkv
If that still has issues, then not sure.
The only difference in the Resolve image is that I can't seem to match chroma alignment, and it has less banding in the blue part.
The answer is definitely that Resolve tone mapped the image, which corrects the gradients.
This is also why Resolve's luma and chroma clip earlier than the original.
Someone replied on the Firecore forum about Apple TV RPU management: "Apple devices always ignore L2 trim in profile 8.4 video. Actually there are two version of Apple’s profile 8.4, the early version is L1 only and old OS (like ios14) doesn’t handle trims at all (except profile 5). The recent version uses newer algorithm which needs L8 trim." https://community.firecore.com/t/dolby- ... /19713/302
quietvoid wrote: Fri May 27, 2022 3:32 am
Clearly the file I have is wrong:
So the only possibibility is that you encoded something else in Resolve.
Or that it did some tone mapping, maybe. https://slow.pics/c/iu90f2Sp
The answer is definitely that Resolve tone mapped the image, which corrects the gradients.
This is also why Resolve's luma and chroma clip earlier than the original.
still doesnt make sense.
The file is the original one unless the bd rip I downloaded got messed up. I dont see how it would cause a luma difference like that and IIRC, the PQ image were identical.
And even stranger, how can it just affect the Shield. And no we did not encode "something" else in resolve.
