Android application cannot playback audiostream (DTS-HD MA Stereo in *.mkv)

[voodoo5_6k 29]

I wanted to start watching a movie but then wondered why it wouldn't start. The TV switched to DV mode, but the picture stayed black. Using the remote, it looked like playback was paused, but it wouldn't resume on unpausing. Switching the audiostream however worked.

I went to a computer and logged into the emby server and started playback from there (browser). The audiostream worked fine.

Back to the TV, and switching around between the audiostreams. On rare occasions the not working audiostream would start playing, but I cannot reproduce this. All others worked for the Android application (at least one of them is using the same codec).

Emby server is latest stable, Android application is latest beta (public IP removed- why is that in there?), logs attached.

Thanks

embyserver.txt emby_android_1780081182146.txt

[Luke 42580]

[voodoo5_6k 29]

Thanks Luke.

But I'm not sure why it would need to transcode. This is a DTS-HD MA track. The other DTS-HD MA track is working fine.

In the log, it says:

Fri May 29 21:00:32.621 GMT+02:00 2026 DecoderAudioRenderer: Audio sink error
  androidx.media3.exoplayer.audio.AudioSink$InitializationException: AudioTrack init failed 0 Config(48000, 252, 8, 4500000) Format(4, Surround 5.1, video/x-matroska, audio/vnd.dts.hd, null, -1, en, [-1, -1, -1.0, null], [6, 48000])

This is a stereo track however, not Surround 5.1. Is it trying to initialize the audio sink for 5.1?

Looking at the track in e.g. Audacity also shows it as stereo.

[Luke 42580]

@voodoo5_6kif the player signals some kind of error with the file, then the app can automatically recover and continue playback using server transcoding. As you've taken that away, this makes that not possible.

[voodoo5_6k 29]

OK, that's understood. But transcoding in that case would've only hidden the error. That's not what I'm looking for. Everything on my server should work with direct-play, there shouldn't be any transcoding. The audio sink is DTS-HD MA capable, as it plays all other DTS-HD MA tracks. That sort of points to a) the file and/or b) the player. I'll re-do the file to exclude that.