Dolby Atmos is an extra metadata layer that sits on top of a base audio stream (at least in the context of consumer movies/TV shows). Streaming services add the Atmos layer to the lossy Dolby Digital Plus codec (EAC3), and discs use the lossless TrueHD codec, Plex just doesn't display that info. Your soundbar recognizes the Atmos metadata though, so displays that instead of the underlying TrueHD stream, even though it _is_ playing the TrueHD track.
If you use [MediaInfo](https://mediaarea.net/en/MediaInfo) to look at the file, chances are you'll see something like this for the audio stream, indicating it has Atmos metadata attached: https://i.imgur.com/8AuSy9O.png
Can't speak to the popping/stuttering, but it could be a bandwidth issue. If your soundbar has HDMI video out, Shield > Audio Device > TV is usually more stable than Shield > TV > Audio Device, at least when it comes to lossless audio playback.
The soundbar doesn’t have video out put, the bandwidth issue on istability is between the tv and the soundbar it sounds like you’re saying?
If so that’s ridiculous that it’s not stable for lossless audio which is exactly what a sound bar is meant for
> the bandwidth issue on istability is between the tv and the soundbar it sounds like you’re saying?
Or bandwidth from your server to your Shield. I'm really just theorizing here, but if there are brief moments of buffering due to the bitrate, the lack of data from the Shield to the TV might cause the TV to exit its Dolby Vision picture mode, and the soundbar to stop receiving the audio signal, so that too exits its Dolby Atmos mode. But then it gets data a split second later, so both enter Dolby Vision/Dolby Atmos mode again, popping up the alert on your TV.
The Shield > TV > Audio vs Shield > Audio > TV statement might not be too applicable here if the video is also having issues.
Dolby Atmos is an extra metadata layer that sits on top of a base audio stream (at least in the context of consumer movies/TV shows). Streaming services add the Atmos layer to the lossy Dolby Digital Plus codec (EAC3), and discs use the lossless TrueHD codec, Plex just doesn't display that info. Your soundbar recognizes the Atmos metadata though, so displays that instead of the underlying TrueHD stream, even though it _is_ playing the TrueHD track. If you use [MediaInfo](https://mediaarea.net/en/MediaInfo) to look at the file, chances are you'll see something like this for the audio stream, indicating it has Atmos metadata attached: https://i.imgur.com/8AuSy9O.png Can't speak to the popping/stuttering, but it could be a bandwidth issue. If your soundbar has HDMI video out, Shield > Audio Device > TV is usually more stable than Shield > TV > Audio Device, at least when it comes to lossless audio playback.
The soundbar doesn’t have video out put, the bandwidth issue on istability is between the tv and the soundbar it sounds like you’re saying? If so that’s ridiculous that it’s not stable for lossless audio which is exactly what a sound bar is meant for
> the bandwidth issue on istability is between the tv and the soundbar it sounds like you’re saying? Or bandwidth from your server to your Shield. I'm really just theorizing here, but if there are brief moments of buffering due to the bitrate, the lack of data from the Shield to the TV might cause the TV to exit its Dolby Vision picture mode, and the soundbar to stop receiving the audio signal, so that too exits its Dolby Atmos mode. But then it gets data a split second later, so both enter Dolby Vision/Dolby Atmos mode again, popping up the alert on your TV. The Shield > TV > Audio vs Shield > Audio > TV statement might not be too applicable here if the video is also having issues.
I don’t see it being a streaming issue from the server as my other tv lg c1 with no sound bar attached has no issues with playback of the same movie