No Audio on Android TV

[Misato_Enjoyer]

As the title says, I have no audio when watching on my TV using the JellyfinApp.  I had an issue where video suddenly stopped working with a player error, but I fixed that by turning off direct stream.

I do not have this issue, or any other issues while watching in a browser on my phone, laptop or PC.

I have attached a log and an FFMPEG log.

Some extra info:
I have uninstalled and reinstalled the JellyFin app on the TV.
I have restarted the server.
I have updated the server.

It is running on a Ubuntu pc.  Media libraries are stored on a NAS.  NAS is mounted correctly as media playback is just fine outside of the app on the TV. 

Any help is appreciated.

[TheDreadPirate]

Try changing the audio output setting in the ATV app to "downmix to stereo".

Unrelated, I noticed that you are software transcoding to AV1. What are the specs of your server? Does it have a GPU or iGPU?

[Curler1]

I have the same problem and it works again when I change the audio-setting in the ATV app to "downmix to stereo". Thank you for your help, TheDreadPirate.

Is there any way to force this setting on the server side so I do not have to tell my family to change it on every device?

And do you have any idea why the problem came all of a sudden?

[TheDreadPirate]

No. That setting is client side and can't be changed on the server.

I'm not an expert in the inner workings of Android nor our app, so I can't comment on why this is a problem.

[theguymadmax]

I have the same problem and it works again when I change the audio-setting in the ATV app to "downmix to stereo". Thank you for your help, TheDreadPirate.

Is there any way to force this setting on the server side so I do not have to tell my family to change it on every device?

And do you have any idea why the problem came all of a sudden?

What device are you using? Does it attempt to play but fail with error messages? Or does it transcode, producing FFmpeg logs but no audio? When you switch to downmix to stereo, it might be requesting a different codec, which would generate new FFmpeg logs. Clearly labeled logs are needed to see what is happening.

[slip]

I think I have this same issue. I have narrowed it down to specifically server version 10.10.4, Android TV and Dolby Atmos being transcoded. If any of those differ, it works. Downgrading to server version 10.10.3, or playback on other devices like web or pc media player or different audio profiles all work.

If someone here could test this on their end as well, it would help. Be on server version 10.10.4 and playing media that has Dolby Atmos audio using Android TV. It should play back just fine while direct. Force it to transcode by lowering the bitrate manually through the playback controls and see if the audio stops playing.

[theguymadmax]

I think I have this same issue. I have narrowed it down to specifically server version 10.10.4, Android TV and Dolby Atmos being transcoded. If any of those differ, it works. Downgrading to server version 10.10.3, or playback on other devices like web or pc media player or different audio profiles all work.

If someone here could test this on their end as well, it would help. Be on server version 10.10.4 and playing media that has Dolby Atmos audio using Android TV. It should play back just fine while direct. Force it to transcode by lowering the bitrate manually through the playback controls and see if the audio stops playing.

Thank you for clearly outlining the issue. I was able to replicate it and will investigate further.

[theguymadmax]

After a lengthy discussion with the developers yesterday, they came up with a fix for this issue, which is also being tracked here. It should be included in the next 10.10.5 bug release, though there’s no specific timeline for when it will be released.

[Curler1]

After a lengthy discussion with the developers yesterday, they came up with a fix for this issue, which is also being tracked here. It should be included in the next 10.10.5 bug release, though there’s no specific timeline for when it will be released.

Wow, this is great news! Amazing work! Thank you!

[theguymadmax]

10.10.5 was just released. This should fix the issue.