Playback of surround audio has not worked correctly since updating the app from version 14.x to 15.1. Prefer hardware-accelerated codecs is enabled.
E-AC-3 JOC in an M4A container works now, as it did before the update. Opus 5.1 plays only in stereo, and E-AC-3 in an MKA container also plays only in stereo. Opus previously played correctly in 5.1. E-AC-3 in an MKA container previously played in 5.1, but without passthrough of JOC/Atmos data.
Device type
Android TV
Media provider
Jellyfin
Steps to reproduce
Enable hardware-accelerated codecs. (probably only for eac3 or other commercial codecs)
2.Start Playback of Audio file.
.M4A works (Multichannel Output + Atmos), .opus and .mka doesnt work (Stereo Output)
Thank you, I found your 15.1.0 TV logs. For the captured MKA track, Jellyfin converts the audio to six-channel Opus, and Symfonium creates a 5.1 PCM output. This confirms the app’s output configuration, but it doesn’t tell me what reaches your receiver. That transcoded stream also cannot pass through the original Atmos data.
Could you please make one fresh debug capture covering a native Opus 5.1 file, the affected MKA and the working M4A? Enable debug mode before starting playback, keep the hardware-codec preference unchanged, then disable debug mode and upload promptly. Include your app version, upload description, reproduction time and the receiver’s input format for each file.
Please also tell me how the box connects to your TV/receiver, whether ARC/eARC is involved, and your Android surround-output setting. I need those comparisons to distinguish a playback regression from how multichannel PCM is handled along the output route.
My box is connected to my AVR via HDMI. The AVR handles the audio and passes the video through to my projector. Passthrough is enabled in my Android TV settings.
With the official Jellyfin Android TV app, multichannel Opus works, and Atmos works with both MKA and M4A files.
Log Name M4A: yumyum m4a
Log Name MKA: yumyum mka
Log Name Opus: yumyum opus
Thank you, I found all three captures. They show a clear difference: the working M4A sends encoded Dolby Atmos audio, while both native Opus and the MKA converted by Jellyfin use 5.1 floating-point PCM. Since native Opus plays directly, Jellyfin transcoding cannot explain the shared stereo result.
The logs still show a six-channel output configuration for both affected cases. This points me toward the decoded PCM path, but I haven’t confirmed where the channels are lost.
Could you give me your AVR model and its incoming signal information while playing the Opus file—does it report PCM 2.0 or PCM 5.1? I have the requested playback captures and your direct-HDMI setup details already.
The E-AC-3 audio in the MKA file is transcoded to “Opus, 48000 Hz, 5.1, flt, 192 kb/s.” I couldn’t find the reason for this. The only relevant information I could find is:
The three Supports flags you found are from the general item information. In the playback response, Jellyfin rejects direct playback for the MKA and selects Opus. I found a possible explanation: Jellyfin identifies its container as mkv, while my audio playback profile lists mka but omits mkv. I still need to confirm whether that mismatch is the reason for its decision.
Please look for PlaybackInfo and TranscodeReasons, including ContainerNotSupported, AudioCodecNotSupported or VideoCodecNotSupported. Could you share the complete reasons and the Jellyfin playback-decision log around the MKA attempt, with the occurrence time and any tokens or private URLs removed? The FFmpeg output line too.
Which log do you need? I found this playback information on the dashboard:
Transcoding
The media is being converted into a format that is compatible with the device that is playing the media. 192 Kbps OGG OPUS Reason for transcoding The container is not supported The video codec is not supported The audio codec is not supported
Thank you, I found both new logs. Jellyfin converts the MKA from Dolby Digital Plus/Atmos to six-channel Opus at 48 kHz. It preserves 5.1 channels, but that conversion loses the Atmos data.
Jellyfin reports the MKA container as mkv, which my 15.1.0 audio profile omits. That declaration is corrected in my current code, but I haven’t verified the result with your files. It also doesn’t explain why native Opus reaches your AVR as PCM 2.0: your app captures show a 5.1 floating-point PCM output in both affected cases.
Could you upload one affected native Opus file and one MKA file to https://upload.symfonium.app and tell me the descriptions? I have the logs already; I need the audio files themselves for the next comparison.
My roommate has similar issues on his TV box (Xiaomi TV Box S (3rd Gen)). Are you sure it’s specific to my Homatics box? He has even bigger playback issues: Opus or MKA surround audio can’t even be played in stereo (there’s no audio output at all), the player progress either jumps from 10 to 20 seconds or advances unevenly. These issues have occurred since the update from 14.x. Before the update Opus Playback worked fine on both of our boxes. Do we have to just accept that Symfonium doesn’t work anymore?
That’s not what you reported … You reported that it played in stereo … If he have a different issue then I need logs. And I need proper logs from you with the proper description of the actual issue occurring in the log .
No MKA for now as it trigger a bug on Jellyfin side, but the other case.