Most support the RPU just fine, regardless of whether the EL is used or not.
FireTV devices panic and die when playing them.
Still black screens on 4K Max, with profile 7 MEL + HDR10+ files as well as profile 7 FEL.
The profile 8 sample also black screens.
At this point if you’re still trying fixes that aren’t altering the bitstream, it should be clear that they don’t work with the 4K Max.
Compatibility is better.
It’s not working on the FireTV Max so compatibility hasnt changed for this particular device, im unsure on what devices it allows things to plag on that wouldnt of played it before except maybe the Apple TV but then the colours would be incorrect as its following p8 instead of p7.
I’m working through what allows DoVi to play on the devices we have which is now working as expected without any bitstream changes. We can’t really drop HDR10+ as its supported so if we remove it from the stream we would be breaking HDR10+ support.
I’ve yet to see any DoVi video that breaks a FireTV in this way, except for the Max that is mentioned in this thread.
It’s only not working because of the HDR10+, doesn’t have anything to do with the Dolby Vision profile here.
Correct, the only solution is to have a setting for it, which might not be desirable.
Though either way it could be good for users to be able to pick between Dolby Vision or HDR10+.
What about this one: https://0x0.st/HsL5.mkv
It will only break if you allow profile 7 playback, otherwise your build falls back to HDR10 on most FireTV devices (except the 4K Max).
Technically I could make a sample that works around the profile 7 limitation, as only the container metadata is verified.
It doesn’t break anything when allowing that file to playback as DoVi it does however end up as HDR despite using the DoVi decoder.
We’ve tried a 4K Max here and have confirmed none of the samples work, we will have a discussion about what we should do about it, but we will most likely inform Amazon about the problem and let them fix it since it’s the only device that is broken. Messing with the bitstream might be possible, but it depends on the legal ramifications so can’t promise we can implement this.
Maybe my 2018 4K stick just has too old firmware and it does still break.
Good to know the issue isn’t present on other devices, though.
I have always expected all FireTV devices to behave similarly with these files.
Profile 5 might be more common with streaming services, but it’s impossible for end-users to use it unless they’re illegally acquiring their media. It’s also a suboptimal solution for the way Plex currently works because many incompatible devices will select it even if a compatible HDR10 version exists.
Profile 7 is incompatible with most devices while Profile 8 works with many devices. Apple TV, LG WebOS, Fire TV, CCwGTV (FEL movies fail), and Shield (DV trigger & flashing issue) all are compatible with Profile 8 while incompatible with Profile 7 (there are additional players as well I’m not listing that benefit from Profile 8.
Colors are incorrect on Plex for Apple TV when using P7, but accurate when using P8 aside from Plex putting the Apple TV in Dolby Vision mode when it is actually ignoring the RPU and just sending the HDR10 Base Layer (unless the file is packaged as a P5 MP4 to trick the Apple TV Plex app and the Apple TV). Infuse on Apple TV illustrates what is possible on Apple TV and is now able to play P8 MKV files in their current Beta builds and is soon to be releasing this generally.
We would select the HDR10 version if a DoVi P5 and HDR copy of the media exist and the user doesnt have a DoVi compatible setup.
Whats the flashing issue? I’ve never seen this and the SHIELD is my primary device - I play a lot of DoVi and all my rips are kept as P7 FEL. Same goes for the Chromecast I’ve not seen any problems with P7 FEL, or any compatible device.
Sadly not, each device has a bunch of its own quirks.
We should be able to add a bitstream filter to remove the HDR10+ to allow these files to play on the Max.
My experience is that MKV P5 will be selected over HDR10 on either Plex for LG WebOS or Plex for Apple TV (I haven’t tested either in a while, so I can’t remember which, since my focus is on P8 after running into many Plex P5 fallback compatibility bugs) and playback as YCbCr showing incorrect colors even though it is ICtCp.
I personally gave up on the Shield 2019 since it sounds like the Red Push issue can’t be fixed, but I do recall seeing this issue when I had one. The P7 issue is described on the Dolby_Vision_stuff Google Sheet (DoVi Playback Devices tab) that is frequently referenced by the community.
Here’s what it says about the Shield 2019:
PROFILE 7 DOLBY VISION SINGLE-TRACK DUAL-LAYER FEL SUPPORT: NO
M2TS & TS & MKV
- EL is ignored and only the dynamic metadata in the RPU is processed
- some fel movie will have annoying flashes
- not perfectly stable, can take 2-3 times to trigger DV
- red push issue
MP4 mp4muxer
- not as stable as TS/M2TS/MKV
Here’s what it says about the CCwGTV:
PROFILE 7 DOLBY VISION SINGLE-TRACK DUAL-LAYER FEL SUPPORT: YES
M2TS & TS & MP4 & MKV
- Watched 3 FEL movies and so far so good but a lot of FEL P7 movies cannot be FF/RW or even resumed (regardless of the software used to mux ST-DT). I suspect those movies were the ones that went out of sync before the latest update.
- Seems to produce a brighter image compared to the x800m2/C2 but more test needed.
Can’t say I’ve seen any of those issues with the SHIELD or the Google TV, DoVi always get’s enabled whenever I play DoVi content and it’s never flashed.
Can’t speak for the red push issue, I don’t play movies side by side another device to be able to spot any difference, watching them on my TV and I never notice that things are overly red but each to their own.
What these devices can do (playing P7) isn’t exactly what Dolby intended them to do so it’s not surprising they aren’t perfect, no non-bluray player actually advertises support for profile 7, when it work’s it just happens too not of been blocked by the device. Sadly there’s no real audience for making it work compared to streaming, since ripping discs is a bit of a grey area in some countries.
Agreed that Dolby didn’t intend for P7 to be used this way, but they did for P8. That’s why I mentioned Profile 8.1 in the title of this thread and included a P8 sample. Even iPhones capture videos in P8 (Profile 8.4 specifically).
For the typical Plex Admin that’s backing up P7 UHD Blu-rays that aren’t compatible with the majority of playback devices, it’s fortunately really simple these days to convert P7 to P8 with RESET_9999’s DoVi_Scripts.
Looking forward to hearing what develops between Plex and Amazon on this one (once/if anything can be shared with us). The Fire TV seems like a great device outside this issue. I keep one on hand only for testing and don’t actually use it myself. I opened this thread more than anything in hopes of helping the Plex community.
Wouldn’t it somehow be possible to build in a switch into Plex Android TV player settings so that Plex tells ExoPlayer that there is no DV functionality? This way people with Fire TV could at least make use of HDR fallback.
On my end I’m using quietvoid’s Kodi with PlexMod now.
Makes P8 out of P7 on the fly and ignores HDR10+. So it turned out to be a play-everything-solution for the Fire TV 4K (Max) at the moment.
Would be great though if the Plex developers found a solution for a problem that lots of people should have, since the Fire TV is a popular device and the market keeps producing the problematic formats.
Couldn’t Plex offer a simple on-the-fly losless removal of the HDR10+ metadata on server side for this case?
That is, if a FireTV 4K Max is detected, an MKV with DV Profile 8 plus HDR10+ and a DV capable TV, then this workaround is executed.
I’m just trying to think a little outside the box if the problem can’t be solved on the codec side.
So sth. like …
ffmpeg -i input.mkv -c copy -map 0 -bsf:v "filter_units=remove_types=39" output.mkv
This would be an incredible solution if the Fire TV didn’t have an ST2084 tracking issue producing a darker image:
I thought about possibly trying this as well on a CCwGTV but it looks like it has issues with producing a brighter than reference image:
And then the Shield TV is too red:
I wish I could find a device that could run PlexMod on Kodi with color accurate support for DoVi P8 and Atmos TrueHD + DTS:X audio passthrough.
Wouldn’t that be a SHIELD with kodinerd’s Kodi 20 builds (DoVi support) and PlexMod? (Passthrough all the things)
You still have to contend with the red push issue then, right?
I sold my Shield after seeing this issue: Dolby Vision | Slowpoke Pics
Hmm, not sure. The referenced YT video proof is half a year old (e.g. pre-9.1.1/newer android).
If I understand the source of the issue correctly, it’s hardware problem and not a software problem unfortunately. It’s also a reasonably well-known issue so I’d imagine someone would have posted if it was fixed
I witnessed the Shield red push issue myself on a calibrated display and it was bad enough that I considered it a deal-breaker. Not everyone cares about accuracy though so to each their own.
What the…??
The issue affects multiple Firesticks. Firestick 4k, Firestick 4k Max, and even the 1080p one.
I have all 3, and most of my library is freaking unusable on Plex with Firestick cause of this.
Quickly skimming through the thread here and I don’t understand how you are unable to reproduce it.
I have dozens of samples I can share that have DV & HDR10+ that all produce a simple Black Screen exclusively while using PLEX
For example:
Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5@Main
HDR format : Dolby Vision, Version 1.0, dvhe.08.06, BL+RPU, HDR10 compatible / SMPTE ST 2094 App 4, Version 1, HDR10+ Profile B compatible
Codec ID : V_MPEGH/ISO/HEVC
This is not an issue on other apps where I can move the Firestick around, and have DV or HDR10+ play fine.
It’s not a hardware issue. Firestick supports DV fine, and HDR10+ fine. This was non issue until a couple weeks ago when a Plex update magically broke things.
I don’t understand why they keep using the same version numbers for clearly different builds across different devices if they function differently.
