Build number please to confirm we’re on the latest beta when we report back?
EDIT: NVM saw the beta post 21038, i’ll try now and report back.
BTW my green shift issues seemed to have gone away today. Maybe it has something to do with this “dolby vision not configured correctly all the time” issue. But all the same films that failed yesterday were fine today. (Both the rerips under 1.15.3 and the reprocessing from 1.15.1 to 1.15.3) I’ll report back again shortly.
Reporting back, already had the HDR10 issue. First time I loaded an MKV (1.15.3) it triggered dolby vision. Let it play a few min, used back arrow to quit out back to menu, started again and HDR10…
Seems like its not fixed…
I have the latest beta version (posted today) on a Shield 2019. PMS is version 1.20.2.3402 and I have several DV rips. Re-analyzed all of them for testing. Shield is connected to a Sony AVR compatible with HDR, Atmos and even DV. Screen is an LG C9. This is what I’m getting:
Edit: “Joker” was not reporting DV metadata on the server “Get Info” screen. I’m going to use 1.15.3 on it and try again.
I’m seeing audio transcoding happening from time to time when I try to play a DV MKV, so DTruHD ends up as DD+ even though my processor (Anthem AVM60) can, and does, handle all formats.
Also, are you planning to update the flagging of DV rips so that there is an indication on the film’s main page?
For instance, the Video info could include DV alongside the current info (4K (HEVC Main 10 HDR)).
Beta 8.8.0.21038
PMS 1.20.3.3401
I have two NVShield Pro’s, one for the Master Bedroom and one for the LVR. I am keeping the Master Bedroom on 8.8.0.20999 as a control.
LVR Beta 8.8.0.21038 - still getting the HDR 1/2 the time, rather than DV. When DV does kick in, I am getting MAJOR color shift problems: whites are a hot fuscia/hot pink, for example. Logs attached (hopefully)Plex Media Server Logs_2020-10-08_20-57-38.zip (4.1 MB)
Let me know if you need anything else.
After I upgrade the PMS to the latest version, I can see the DOVI information.
Codec HEVC
Bitrate 63735 kbps
D O V I B L Present true
D O V I E L Present true
D O V I Level 6
D O V I Present true
D O V I Profile 7
D O V I R P U Present true
D O V I Version 1.0
Bit Depth 10
Chroma Subsampling 4:2:0
Coded Height 2160
Coded Width 3840
Color Primaries bt2020
Color Range tv
Color Space bt2020nc
Color Trc smpte2084
Frame Rate 23.976 fps
Height 2160
Level 5.1
Profile main 10
Ref Frames 1
Stream Identifier 4117
Width 3840
Display Title 4K (HEVC Main 10 HDR)
Extended Display Title 4K (HEVC Main 10 HDR)
Where do you see the DV information like that?
If your using the latest beta (8.8.0.21038-beta) and are still having Dolby Vision issues, can you provide the client logs and I will take a look. It should be kicking in correctly as long as it was detected and your device and display support Dolby Vision.
Information about fetching the client logs is available here: https://support.plex.tv/articles/201573117-android-android-tv-fire-tv-logs/
Sounds like we are trying to use refresh rate switching when you have Dolby Vision enabled, we have to disable refresh rate and resolution switching when Dolby Vision is detected on a stream as it’s not possible for us to determine which display mode supports Dolby Vision. Would you be able to grab the client logs for me and I will take a look.
I’ve had another look at it and the issue seems to be caused by the Firestick itself.
With the device’s own refresh rate matching enabled, it happens before Plex and results in inconsistent playback in Dolby Vision.
Disabling it in the device’s settings fixes all the issues for me. 
I’m not sure if Plex is triggering the device’s refresh rate switching, as it’s the same displayed message as other built in apps like Prime Video.
Meanwhile, other apps that support refresh rate switching like Kodi do it on their own and that works well with Dolby Vision from Netflix.
For example, if I play the profile 7 MEL sample, it shows Dolby Vision very briefly before switching to HDR10.
Here are client logs for both: plex-dovi-logs.zip (14.4 KB)
The one where the Firestick refresh rate matching is disabled consistently plays in Dolby Vision.
I think there might be an issue with films that have Dolby Atmos/TruHD soundtracks and DV (A Star is Born and Top Gun). I can only get sound out from these or standard HDR with the TruHD transcoded to DD+.
I don’t see the same issue with DTS soundtracks (Gladiator, DTS:X; Universal Soldier, DTS HD-MA).
Nope. I have been converting all my .TS files to MKV and 9 of the 16 I have done so far have Atmos and all play without issue.
Go to a movie with DV.
Beta 8.8.0.21038
Win 10 PMS 1.20.3.3401
NVShield Pro 2019
I turned refresh rate and resolution switching both off and it solved my weird color issue. The only problem I still have is not immediately detecting DV. I have seen HDR10, Normal and DV. I have to start and restart several times to get DV to kick in.
My understanding is that this is a known issue and engineering is working on it. However, if you still need/want the Media Player app logs from the NVShield, I can provide. Just let me know.
I have no issues with DV and ATMOS playing in the same media file.
Beta 8.8.0.21038 Clean Install
Win 10 PMS 1.20.2.3402 public
Shield Pro 2019 latest public
The only problem I had was that files with Atmos and the selected PGS subtitle didn’t start. I previously analyzed the folder with the DV files and read in all metadatas again. I had to deselect the subtitle first and then I could start. Then I could select it again while he was playing and it continued. Now I could just start the file directly with subtitles. I haven’t tried newly added files yet, maybe it’s because of that. I will report.
The good news is that everything works so far. Auto frame rate switching, 24hz, 60hz, all DTS and Dolby tracks, subtitles and chapters 
… I will of course test everything in detail one by one. my first look is good.
Hi All.
I have been able to get Dolby Vision and Dolby Atmos with MKV working with the following config (see notes of issues though):
The issue I get is that I have to stop and start the movie a number of times at the beginning because it continues to default to HDR. However, after a number of attempts of starting and stopping and starting again, it selects Dolby Vision and plays just fine! Can’t wait for Plex to iron out that bug and we are good to go.
Also, should the same behaviour occur on the Apple TV4K Plex? I have tried and it goes from Dolby Vision to HDR in about 1 second and won’t remain in Dolby Vision,
Hi, back when we was putting these in mp4 container and playing back via Plex on LG, bumblebee was one that would play back with a green hue,and yellow was actually orange? it had to stay dual track to play correctly.
Have you tried FEL to MEL conversion first?
I downloaded the latest beta and I still have problems with The Fifth Element loading in HDR and transcoding the audio 90% of the time, if I close Plex fully then restart the movie I get DV?
Playback is locally from USB3 drive.
Ps The Fifth element has a strange mastering thing where the studio canal logo is only True-HD 5.1 then the Movie is 7.1 Atmos.
Maybe Plex doesn’t understand this?
Just mux the MKV without the Studio Canal logo, select the slightly smaller file in MakeMKV.
I finally got around to testing my problem with repetitive playback and the "Server not powerful enough to cover video) under the Plex for Android 8.8.0.21038-beta, and the problem still exists, but somewhat less frequently. Attached please find the Plex Media Client Logs after the ERROR was reproduced several times.
