Roku 4 (Ultra/Premiere+) - Atmos/DTS 7.1 downmixed to AAC stereo, not AC3 5.1 with Sonos [SOLVED]

Server Version#: 1.20.3.3483
Player Version#: 6.6.12.6662
Sonos Playbar 5.1 Setup. (AC3 5.1 is the only format supported.)

It’s been reported here before, but it’s still a problem. Emby downmixs the same files to AC3 5.1 correctly with the same Roku audio settings.

I tested a few files and these are the results.

AAC 5.1 > AC3 5.1 (works)
DTS 5.1 > AC3 5.1 (works)
Atmos/TrueHD 7.1 > AAC Stereo (broken)
DTS-MA 7.1 > AAC Stereo (broken)

The issue is common to all 7.1 formats. I expected them to be transcoded to AC3 5.1, but they are always transcoded to AAC stereo.


1 Like

Hi. Checking in to see if there has been an update on this. I’m happy to provide logs if needed.

I found another recent thread that has the same issue.

Anyone know how to fix this? DTS ES 6.1 and Atmos tracks are being transcoded to 2.0 instead of AC3 5.1. DTS HD MA 5.1 and TrueHD is being correctly transcoded to AC3 5.1.

Can Plex not transcode these formats to AC3 5.1?

Looking at the webpages linked below I came up with a solution that works for me:
Copy the “Roku-7.x.xml” file from your system profile folder (in Windows: C:\Program Files (x86)\Plex\Plex Media Server\Resources\Profiles) to your local Profiles folder (in Windows at “%LOCALAPPDATA%\Plex Media Server\Profiles” - the “Profiles” subfolder will probably not exist. Look at the links below to find your local folder if it is not there) to avoid the system overwriting changes with a server upgrade.
Edit this copied file by changing the two lines that start with “<VideoProfile " by replacing the existing audioCodec=”…???.." with audioCodec=“ac3” for DD5.1 systems. Then save the file and restart Plex.
For E-AC7.1 capable systems replace it with “eac3” instead of “ac3” and also copy the whole <VideoAudioCodec name="ac3"> <Limitations> <LowerBound name="audio.channels" value="2" /> </Limitations> </VideoAudioCodec>
XML section and replace “ac3” with “eac3” in one of them.
Then restart Plex.

References:
Roku 4 - DTS 7.1 downmixed to stereo, not 5.1? AAC vs AC3? [domura’s post]
https://support.plex.tv/articles/202915258-where-is-the-plex-media-server-data-directory-located/
https://support.plex.tv/articles/201105343-advanced-hidden-server-settings/ [I needed this because I had moved my default folder and couldn’t remember it - setting “LocalAppDataPath”]
https://developer.roku.com/en-ca/docs/specs/media/streaming-specifications.md#supported-audio-codecs

My solution for this became “buy one of those new Chromecast with Google TV things”.

Could this be related to what you’re seeing? Roku transcoding AAC 7.1 to Stereo MP3? - #27 by ljunkie

A bug with transcoding to mp3 stereo on roku/chromecast for 7.1 files is being fixed for 5.1 transcoding but wasn’t fixed for 7.1 but it sounds like they’re looking at it now? A few comments on that thread from Plex employee about it.

Yep, this should be the same bug we just identified. Essentially any surround sound having more than 6 channels that isn’t compatible would be converted to 2ch audio, unless your device supports EAC3 (DD+). We should have a fix coming to the preview channel to fix the issue.

1 Like

Interesting, so it’ll transcode to EAC3 if your device supports it? I believe up until now it would transcode to AAC so that would be new, right?

EAC3 supports > 6ch where AC3 does not. If the selected stream had more than 6ch, then the Roku was not indicating AC3 as an available transcode target when it should (the bug). It has always worked if DD+ support was detected.

There are other nuances that still come into play like HDMI handshake/capabilities, setting Roku volume modes, plugging in headphones, etc.

1 Like

What about Dolby Atmos support for Roku? DTS is still an issue with Roku TV as well.
Roku, probably the most popular client for Plex, cannot support Dolby Atmos and struggles with DTS audio.
Also, no Dolby Vision support. Is an update coming? What prevents support right now? Is there a limitation?

Roku support DD+ Atmos, not TrueHD Atmos. That is a Roku limitation.

We are not aware of DTS issues other than the newer Roku Ultra 4800, which causes a stutter during Direct Play (roku firmware issue). This model seems to have a few quirks. We are notifying Roku about the various issue, but those will need to be fixed at the firmware level.

DV is supported on Roku TVs with DV, as well as the new Ultra 4800. Also note that not all DV is the same, so you may need to handle cf. [FEATURE REQUEST] Dolby Vision support for MKV (ROKU TV) - #11 by Theridges

1 Like

I know the difference with Dolby Atmos. DD+Atmos is more a streaming audio, but lossless with TrueHD Atmos which comes with 4K Blu Rays. I have several of DD+Atmos to test the feature and I can report it is not working on Roku TV which is essentially the same as having a Roku because it is running Roku OS.

DTS is completely useless if you try to rewind or fast forward playing the format. I am playing a Blu Ray movie and the DTS will come in, but if I rewind or fast forward a scene, I cannot get any audio on less I stop the video and play it again.

Will do. It seems weird that the handle is different.

I have no problem with DTS audio tracks on my RokuTV or on my older Roku 3 - but if the bitrate is a bit too high the Roku 3 will choke sometimes. I’m playing back mostly mid quality MKVs.

Maybe if you detail out how your files are setup when you say you’re “playing a Bluray movie” (codec, bitrate, media info maybe), and include the hardware you’re using, it’ll be easier to figure out where you might be hitting limitations. Could be worth starting in a new thread as it sound like separate issue from this one and that way you’ll get a more specific help thread from the community.

I would also please suggest to create a new thread(s) for the specific issues so we don’t loose focus of the OP.

We have released another Preview update, v6.7.10, to fix the issue in the OP.

1 Like

I can confirm build 6.7.10 fixes the issue in the OP.

Thank you!

1 Like

I can confirm version 6.7.15 that was published to the official channel on 02-Mar-21 fixes this issue. Thanks to all that contributed to the fix. I consider this issue SOLVED. :grinning:

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.