Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No audio with stock docker-compose.yaml | Host audio works fine #22

Open
Rastafabisch opened this issue Mar 22, 2024 · 1 comment
Open

Comments

@Rastafabisch
Copy link

Rastafabisch commented Mar 22, 2024

Hello Community, hello @mikebrady!

First off: Thank you for the great work being done!

Now to my issue:
I got a somewhat rare problem. I think.
After experimenting with my SBC (Rock 5B) for the past month I finally settled for a kernel (6.1.43-rockchip).

Sometime early on I already had shairport-sync running perfectly fine with the stock shairport-sync docker-compose.yaml.
However now I do not get any AirPlayed audio anymore. Searching for a solution I realised that with my current kernel defaults to HDMI-audio. I fixed this with an /etc/asound.conf file configuring the headphone jack as the default output device. This apparently works fine as I can just play something on the (headless) host using aplay ./test.wav.

However I still do not get any output via AirPlay. I already checked the docker containers shairport-sync.conf, but it looks good to me, not specifying anything, and thus defaulting to alsa, and whatever the host does (at least this is how I think it works).

Now I hit a dead end as to what else to try.
Any help is appreciated.

Best Rastafabisch


EDIT: I also tried restarting the SBC and the docker container - no dice.

@Rastafabisch Rastafabisch changed the title No audio with stock docker-compose.yaml No audio with stock docker-compose.yaml | Host audio works fine Mar 22, 2024
@Rastafabisch
Copy link
Author

Rastafabisch commented Mar 22, 2024

I fixed it, even though I do not like the fix…

What makes it work is passing through said /etc/asound.conf file as a volume in the docker-compose.yaml file.
This means however, that the container does not respect the hosts set audio device (if overwritten using alsamixer, etc.). I would prefer that the audio outputs wherever I tell the host to route it to. This however appears to be a docker issue, rather than a shairport-sync one.
Nonetheless, if anyone has any suggestions as to how achieve my desired behaviour I'd be glad to hear about it.

That said I think it might be good idea to incorporate my findings into the official yaml file.

    #volumes:
    #  - /etc/asound.conf:/etc/asound.conf # Respect the hosts configured default audio device

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant