seems to be fixed in stable release? I had an update today and everything is working
As stated, the seamless branching issue is not what this thread was originally about nor does it appear to have been addressed.
I have an NVIDIA shield and Plex server on a PC and an ATMOS capable system. I play ATMOS successfully most of the time but several movies end up being in D+ instead of ATMOS. I think I have everything up to date and I know Iām using proper ATMOS movies (in this case The Batman DDP5.1). Can anyone help?
Have you checked the server during playback to see if audio transcoding is happening?
Itās also possibile there are versions out there with both the Atmos DD+ and non-Atmos DD+ track.
As I understand it, Atmos data (ie. height channels) can be presented in either TrueHD (lossless) or Dolby Digital+ (lossy) streams. The latter is typically present on streaming services with the higher bitrate TrueHD reserved for physical media. Some AV equipment will distinguish between the two while others will not. My Samsung soundbar, for instance, simply reports āDolby Atmosā for TrueHD or Dolby Digital+ streams, with Atmos data.
But thatās not to say that Dolby Digital+ and TrueHD always have Atmos, they donāt, theyāre just streams that are capable of carrying the additional Atmos data.
Agreed. Using Nvidia SHIELD Pro 2019 and TrueHD now works fine without almost any buffering even when switching Chapters, and even on Wifi connection with large HEVC files. For reference, SHIELD is direct playing and passing TrueHD 7.1 to my Denon AVR-S650H (2019). Letās celebrate when the devs fix something! Thank you kindly. ![]()
Stupid question maybe but what do I look for? My server is in a separate room so Iāve never looked at it while a movie is playing in the home theatre.
This is certainly an atmos track, which is why Iām curious whatās going on.
Team of Plex Users,
I can report that I have played DTS-X and Dolby Atmos from the NVIDIA SHIELD PRO.
The content does work. Update to the 9.1 which has a new demuxer. Perhaps this was the problem the whole time.
Any ongoing issues must be the file.
If your movie has subtitles, turn the subtitles OFF in your settings and try again.
I thought DTS-X would not work, but it did when I did and also with Dolby Atmos (TrueHD w/Atmos).
Thank you.
Log into your server from a web browser and check the Activity tab during playback. Where the file playing is listed you can expand the details to see whether audio and video are being direct played or transcoded.
I was sure it was going to be transcoding but it actually says āEnglish (EAC3 5.1)
Direct Playā and my receiver is reading it as D+ only.
EAC3 == Dolby Digital+.
Yes but it also has ATMOS and Iām not getting it.
I think you had better start a separate thread as it would seems as though your issue is not related to the bugs that have been reported in this thread.
I canāt believe Iām saying this, but Iām now back to the good old 8.29.0.30300 beta. After a half dozen playback tests with different resolution movies and audio formats, I had multiple crashes during playback and seeking. No longer having those with the old reliable beta. My Plex client as always is set to passthrough audio, match resolution and frame rate. This is on a 2019 Shield Pro w/ Dolby Vision enabled.
there should be no need to have āmatch resolutionā turned one, as the shields AI upscaling will be upscaling the content to 4k before it reaches the TV anyway.
Iām still on the ārolled backā 8.29.1 because I havenāt exactly seen a flood of posts stating that the public 9.1.0 is good.
So⦠Is it good ??
Is your plex working perfectly as expected on the roll back? Mine is. I see no reason to risk breaking it for a slew of bloatware and āfeaturesā nobody asked for. My personal opinion.
Beta version 9.1 and the current 9.2 are working perfectly for me from the point of view of the original bug that I reported. Iām not seeing issues with fast forwarding or rewinding either.
I canāt comment on the seamless branching issue but that is really outside the scope of this thread.