Server Version#: 1.32.6.7371
Player Version#: Latest
I have a few files that have Dolby Vision HDR. My TV can play the files without issues as direct play. Some other clients (Samsung TVs) and specifically, my phone Pixel 7 Pro, cannot play the files at all. It seems that clients that support HDR, but not DV, just fail to play the file. If the client doesn’t support HDR, it transcodes to SDR and plays without issues.
The file shows this for HDR information:
Dolby Vision, Version 1.0, dvhe.08.06, BL+RPU, HDR10 compatible / SMPTE ST 2094 App 4, Version 1, HDR10+ Profile B compatible
I tried muxing the file from mkv to mp4, but the file still fails to play on HDR enabled devices and also strips DV.
I have this happening on multiple different files.
I am not sure what that means nor exactly how it was produced. Can you tell that it was a P5 source from the information that I provided? I thought it was a P8 based on “dvhe.08.06”?
After testing the file the reason it won’t direct play on Samsung is there are more than 30 Streams it is a limitation on Samsung listed in this article, I stripped out the majority of subtitles and it direct plays fine on a Samsung TV when less than 30 streams. Though I see you remuxed it to mp4 which should not have had that issue then. The issue with playback on your Pixel, Do you get an error at all and would you be able to provide client logs
Sorry, I know that question was a bit of a distraction from “why won’t it play?”. I’m just curious, not suggesting the file is good/bad/etc.
No, I don’t think the file is P5. But I also don’t think there are any sources for media that’s DV P8 with HDR10+. So I think the file was Frankenstein’d from multiple sources.
Your question is still reasonable - why isn’t it falling back to HDR10? And you’ve gotten more info from @morganj, and a request for client logs - you’re in better hands.
The audio for that file is out of sync and sounds like it’s playing at 2x speed like the Chipmunks and the video keeps freezing and jumping ahead skipping 4-8 seconds each time
This is a converted copy of the same file using Box4
I am still waiting on the Samsung user to test, but the issue with my Pixel 7 Pro was because I guess it doesn’t support EAC3. Or at least according to the logs, it didn’t like that. So I then added an AAC stream at 2.1 to ensure it wouldn’t transcode and it plays without issue.