Latest Beta fixed Dolby Vision (Single Layer) in an MKV container but killed it for MPEGTS container. Please fix it again since most of my DV are in MPEGTS containers.
2 Likes
Did that use to work before this beta?
Edit - Can you provide the XML for such a movie as an example?
Yes it did work perfectly.
Not sure what you are looking for with the XML file?
Just checking that PMS has identify the DV in the file?
See support article for details. Zip or save as txt then attach to thread, forum does not permit .xml attachments (drag into compose window, will insert at cursor location).
https://support.plex.tv/articles/201998867-investigate-media-information-and-formats/
177623.txt (26.7 KB)
That is the XML file from one of the SL DV movies in an MPEGTS container that used to work until the most recent beta update.
That doesn’t look like PMS analyzed the DV information fully. Try hitting analyze for that movie and see if that changes things.
Anyone noticing any strange color shifts with the new beta with dolby vision triggered? I’m seeing something very strange on BumbleBee. Initial rip was with 1.15.1 and I reprocessed it with 1.15.3. Then I reripped directly in 1.15.3 and still seeing the same thing. LIghts are showing a severe green push. Trying to figure out if its just this title, or something with the beta. I’ll be trying more shortly.
UPDATE: 2001 A Space Odyssey is doing the same thing (both reprocessed and reripped from 1.15.3). Seems like there is something going on here besides my source files, something with the beta itself…
What do I do wrong!?
My setup is: Nvidia shield tv pro 2019, Panasonic hz1000, all ok for DV. Using the previous version of Plex, 8.7, Dolby Vision was triggered when playing some test files or single video channel mp4 with DV. Now after installing latest beta 8.8 Dolby Vision is not being displayed in any files.
Dolby vision is enabled in Nvidia shield.
Where can the problem be?
Nothing changes. Just to be clear, the server version 1.19.3.2764-ef515a800, if that matters.
Why do you say it is not analyzed fully? I can not see any DV information in the XML either, I have tried 5 DV files of mine.
I upload my XML file hereBumblebee.2018.2160p.Bluray.DoVi.TrueHD-7.1.m2ts.xml.txt (126.7 KB) , the file container is m2ts, and I am sure PMS has analyzed the file.
This file can trigger Dolby Vision correctly.
I am not using the BETA version.
Sorry for my bad English. I hope the BETA version can handle Dolby Vision mkv, m2ts and ts perfectly.
I have noted a playback problem using the Beta Release of Plex for Nvidia Shield displaying on a 2016 LG OLED and with Dolby Vision UHD conversion using either MakeMKV 1.15.2 or the recently released 1.15.3. Usually I can start with movie playback without problems the first time I press play. If I immediately stop the playback after a few seconds, then start playback of the same movie or even a different Dolby Vision MKV movie file the screen hesitates (turns black), then after a few seconds the playback stops and the screen shows “ ERROR The server is not powerful enough to convert video ”. If I then press play again (or sometimes a third time), Dolby Vision playback resumes.
The error displayed really does not make any sense since transcoding has been turned off and the player is streaming the video file directly from my 2019 MacPro without any conversion.
Not sure, but there should be other parameters related to DV. Here is an example.
streamType=“1” codec=“hevc” index=“0” bitrate=“53630” language=“English” languageCode=“eng” DOVIBLCompatID=“6” DOVIBLPresent=“1” DOVIELPresent=“1” DOVILevel=“6” DOVIPresent=“1” DOVIProfile=“7” DOVIRPUPresent=“1” DOVIVersion=“1.0” bitDepth=“10” chromaSubsampling=“4:2:0” codedHeight=“2160” codedWidth=“3840” colorPrimaries=“bt2020” colorRange=“tv” colorSpace=“bt2020nc” colorTrc=“smpte2084”
You description sounds like the file failed to play so PMS tried to fallback to transcoding, but since you have it off, you will see this error message. Would need more details and logs to see why it might have failed.
The PMS version matters, Dolby Vision metadata is only analyzed correctly for MKVs on version 1.20.2.
The problem isn’t MKVs, though. I honestly don’t care about MKV as almost all of my DV files are in MPEGTS and they used to work perfectly on current server version and all betas previous to this release.
Plex Media Server Logs_2020-10-08_17-17-32.zip (3.0 MB)
Attached please find the Nvidia Shield server logs that hopefully shows the reason for the “ERROR The server is not powerful enough to convert video” problem playing back Dolby Vision containing MKV files.
A new beta has been released with Dolby Vision fixes from the update in the previous beta, if you are still having trouble playing back Dolby Vision content, let me know.
Could you provide the client logs after experiencing the issue?
Dolby Vision works great for Jaws a d Forrest Gump. When I try Schindler’s List, Saving Private Ryan, John Wick 3, Superman only come up HDR. Great to see that it’s heading in the right direction though! Playing great on my 2019 Nvidia Shield Pro
Cheers for the update.
My feedback is on a FireTV Stick 4K.
I’m testing with MakeMKV’s test samples.
They all trigger Dolby Vision on first try without refresh rate matching.
With refresh rate matching enabled, profile 4 often stays in SDR mode.
Profile 5, 7 FEL and 8.1 trigger Dolby Vision consistently.
Profile 7 MEL triggers HDR10 only.
