Any update? I have a new series I want to watch. I have two copies, but both run into this problem. Thanks.
Sorry I donāt have an update.
What is the color space of the files. What device are you trying to play them on.
if it is Dolby Vision please be specific about details maybe provide the plex media info. As far as I know there are multiple profiles of Dolby Vision. one for streaming (Profile 5) and others for blurays. most devices can only play the streaming type.
The server cannot transcode Dolby Vision and I am wondering if a clients issue being more specific about what it can play and since server cannot transcode the client ends up showing that error.
Why canāt the server transcode DV?
Is this on the roadmap?
It is a codec licensing thing. Not a technical thing.
If this is an issue across the board for Plex, is any of that relevant? Maybe I misunderstood. So this does work for certain files and certain clients?
Iām just trying to understand what folks have so I can be as precise as I can in bug report. I realized this weekend when thinking about this some folks are just saying āHDRā as a catch all for HDR10 and DV.
Devices can play what they can play based on the licensing they support. Apple TV can direct play DV profile 5 in an mp4 only as far as I know for example. if it in an MKV or if anything causes transcoder ( which also handles direct streams from one container to another) to get involved it canāt.
I have this issue, and in my case itās DV.
Is there something we can do to bypass this issue? Like replacing an ffmpeg binary or something?
I have a quick question related to that. Is it really out of the question for Plex to license Dolby Vision for both servers and players? It would solve the problem of some players not supporting some flavors of DV, and might also solve the problem about not being able to transcode DV (if Dolby allows such a thing with a license).
It could even maybe be a great new Plex Pass feature.
not that I am aware of. our ffmpeg is highly customized and i donāt think it can jsut be replaced based on how I think it is baked in but not something I have ever tried.
I donāt think it would help - Plex makes the decision to attempt transcoding (or not), and what parameters to use, before calling the transcoder.
If we could Iām sure we would. Iām not a lawyer and donāt know all the details of it but I got the impression it is not as simple as just paying Dolby X amount for the rights
I have an mkv and an mp4 copy of Godless. Let me know what all info would be helpful to relay the issue better. Trying to watch on web client - server version 1.26.0.5715 - Fedora 35 server core.

A problematic HDR File on 1.25.4.5468. It has wrong colours on direct play.
Why do you say HDR10?
Thatās āD O V I Profile 5ā per the displayed info.
I think this is a true statement: All streamed DV content is Profile 5.
you are totaly rightā¦
On 1.26.0.5715 I got a error for āno profile for http, mkv and hevcā
Yep I guess my examples of this issue are all DV too. Maybe another example will help.
I can also confirm that when I downgrade to PMS 1.25.4.5468 I can see the media in the correct colors on my w/ my NVidia Shield TV but on my PC or iPhone/iPad the color looks waaaaay off.
And when I play on any PMS version newer than that I get the error I posted in the screenshot on April 17th on this thread on any device I own including the Nvidia Shield.
Can somebody share the Codec ID for a few problematic DV Profile 5 videos? Are they dvhe or hev1 or dvh1?
The Codec ID is visible in current PMS XML Info, or with mediainfo -f.
And/or PM me some samples, or source links for examples?
Plex displays wrong colours with Dolby Vision on AppleTV 4k - #346 by Volts
DVHE is a problem
Plex team: Love you guys, but come on⦠This is a pretty major usability bug thatās been skipped over for several versions for nearly 3 months.
The last version that didnāt have this issue was 1.25.4.5487ā¦
This is absurd. Please fix.
What is the most concise way to express the root cause here? Why does Infuse work for everyone while the Plex client does not? Is this a DV licensing (financial) issue or a code bug?

