Ran into this, I use Claude to help manage my server and this is a report it generated to add to this thread:
Server Version#: 1.43.2.10687-563d026ea
Player Version#: 2026.13.0
Confirming this is still present on player 2026.13.0 (one version newer than the 2026.12.0 reports above), on the same server build others here are running.
I did some digging on the server side and turned up two things I haven’t seen mentioned in this thread yet: the failing playback is being delivered over HLS, and the same file direct-plays with working audio in a different client on the same hardware. Details below, plus the server logs that were asked for.
Environment
|
|
| Plex Media Server |
1.43.2.10687-563d026ea (Linux, Debian 12) |
| Plex for Fire TV |
2026.13.0 |
| Device |
Fire TV Stick, Fire OS 8.1.8.0 (build RS8180/3729), Android 11 |
| Comparison client |
Jellyfin Android TV 0.19.9, same device |
| Audio chain |
Fire TV → AVR with channel indicator → speakers |
Test file: single audio track, DTS-HD MA 5.1 (dca), no fallback track. HEVC 2160p in MKV.
Symptom: video plays perfectly, no audio, and the receiver shows zero active channels — nothing is arriving at all, as opposed to the wrong format arriving.
1. The failing stream is direct-played over HLS
Every failing playback logs this decision:
Streaming Resource: Reached Decision id=2870 codes=(MDE=1000,Direct play OK.)
media=(id=15328 part=(id=15328 decision=direct play protocol=hls
streams=(Video=(id=75844 decision= width=3840 height=2160)
Audio=(id=75845 decision= channels=0 rate=0)
Subtitle=(id=75846 decision=ignore languageCode=eng location=embedded))))
Note protocol=hls, an empty audio decision, and Audio=(... channels=0 rate=0).
This looks like the actual mechanism: the video track extracts from the HLS stream fine while the audio track silently fails to initialize. It would explain why the receiver sees nothing rather than receiving something malformed.
2. Same file, same device, works in Jellyfin
Run minutes apart on the identical Fire TV:
| Client |
Method |
Delivery |
Audio |
| Plex for Fire TV 2026.13.0 |
direct play |
HLS |
Silent |
| Jellyfin Android TV 0.19.9 |
DirectPlay |
raw MKV over HTTP |
Works |
Both direct-play the same DTS-HD MA track with no transcoding. The only difference is the delivery wrapper.
This rules out the device, the receiver, the HDMI chain, and DTS support itself — the hardware bitstreams DTS to the AVR correctly. Whatever is failing is on the Plex side.
3. Direct Play and Passthrough settings do not change the decision
This may be the more serious problem, because it removes any user-side workaround.
Six consecutive playback attempts of the same item, spanning Passthrough enabled, Passthrough disabled, and Direct Play switched OFF (Direct Stream left ON), each after a force-stop of the app:
21:08:12 | part=direct play proto=hls audioDecision=(empty) | MDE=1000,Direct play OK.
21:10:19 | part=direct play proto=hls audioDecision=(empty) | MDE=1000,Direct play OK.
21:13:31 | part=direct play proto=hls audioDecision=(empty) | MDE=1000,Direct play OK.
21:15:13 | part=direct play proto=hls audioDecision=(empty) | MDE=1000,Direct play OK.
21:18:22 | part=direct play proto=hls audioDecision=(empty) | MDE=1000,Direct play OK.
21:21:55 | part=direct play proto=hls audioDecision=(empty) | MDE=1000,Direct play OK.
The decision never changes. The client also continues advertising dca support with Passthrough set to Disabled:
TranscodeUniversalRequest: adapting profile with augmentation data:
add-transcode-target(type=videoProfile&context=all&protocol=hls&container=mkv
&videoCodec=h264,hevc,vp8,vp9
&audioCodec=aac,pcm,mp3,ac3,dca,eac3,truehd&...)
WARN - ClientProfileExtra: ignoring directive:
add-transcode-target-codec(scope=videoTranscodeTarget&scopeName=dca
&scopeType=audioCodec&context=all&protocol=http)
So the server keeps being told the client can handle DTS, and keeps choosing direct play, regardless of what the app’s settings say.
4. This may not be DTS-specific
There is a parallel report — [Android TV/Amlogic] Plex 2026.11.0: Direct Play ON causes no audio (EAC3/AC3) — describing the same shape with EAC3 and AC3 on Amlogic Android TV, and it mentions similar EAC3 Direct Play failures on Windows clients.
Different codecs, different platforms, same behaviour: Direct Play produces silence, forcing a transcode fixes it. If the fault is in the direct-play/HLS path in the New Experience app rather than in DTS handling specifically, that would account for all of these reports together.
That reporter also found Direct Play OFF + Direct Stream OFF → audio works. That is consistent with what I saw: I tried Direct Play OFF with Direct Stream ON, which still routes through HLS, and it stayed silent.
Workarounds
- Reduce streaming quality below Original to force a transcode — works, but needlessly re-encodes 4K HEVC and costs picture quality.
- Turn off Direct Play and Direct Stream (per the Amlogic thread).
- Use a different client. Jellyfin plays the same file at full quality with working audio on the same hardware.
Logs
The excerpts above are from default logging, not verbose. Happy to supply the full Plex Media Server.log window around any of those six attempts, client logs, or a sample file — just say which would be most useful.