I upgraded to 1.29.1 and my entire Dolby Vision profile 5 content no longer works when transcoding is required. These files played back perfectly fine before the upgrade, now I am getting this error:
I have briefly discussed this with @ChuckPa and from what I understand, this should have never worked - even before 1.29.1 - but it did. There is also this notion that there is nothing to discuss.
But I want to understand why it worked before. To me, this is a regression.
Some browsers can tone map it.
The transcoder itself never could and never will (by definition of the Profile specification).
PMS will let the browser handle the tone mapping.
If you turn off Tone Mapping, Does it work ?
Regardless, this isnât a regression. Profile 5 wonât tone map by FFMPEG.
Prove it! Share a file, share media info?
Share server dashboard status during playback?
Safari on Mac is the only one Iâm aware of, are there others?
Iâm 99.9% sure that wonât help.
Thatâs âsomeâ 
Safari is the only one I know of.
Chrome can tonemap HDR10 on the right platform.
I didnât know the browser was doing the tonemapping. That explains it then. In my case, it is Chrome, btw. So it looks like pre-1.29.1 Plex just left it to the browser. With 1.29.1 Plex outright refuses to play these files. Thatâs a regression, in my books.
If youâre transcoding a Profile 5 file â Youâve already broken the rules.
Now, because PMS contains the native support, you got caught.
Sorry 
Itâs fine. I just needed to understand whatâs going on. I donât usually watch my content in the browser.
You say these looked fine?
DV P5 usually looks like green dystopian garbage when it isnât processed correctly.
But thereâs also a minor misguided movement out there, producing files that CLAIM to be DV P5, though they arenât really DV P5.
PM me a sample?
They looked perfectly fine - and if the browser was doing the tonemapping, that explains why.
Case is closed for me. I understand whatâs going on, thatâs all I needed. Thank you though.
I donât! So Iâm still curious.
If they are DV P5, they shouldnât have worked before. Chrome wouldnât tonemap these. (Google is even starting a project with competing color and dynamic HDR standards to avoid Dolby.)
If they are HDR10, they should still work.
But if youâre satisfied, thatâs OK.
I suspect this is going to surprise a lot of folksâŠ
It also means people will be âacquiringâ new HDR files
Samsung already has a Dolby alternative: HDR10+
Sure, but Google has the worst case of Not-Invented-Here Syndrome.
Googleâs byline should be â80% there â Next!â
(Plex hat OFF )
This is more or less why I just completely avoid anything with DV on it. Saves the trouble.
I bought a DoVi TV and DirectPlay everything
LOL
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
