starred/librespot

Fork 0

mirror of https://github.com/librespot-org/librespot.git synced 2026-04-27 08:15:50 +03:00

[GH-ISSUE #398] librespot does not release the device #253

New issue

Closed

opened 2026-02-27 19:29:40 +03:00 by kerem · 3 comments

kerem commented

2026-02-27 19:29:40 +03:00

Owner

Originally created by @dubo-dubon-duponey on GitHub (Nov 9, 2019).
Original GitHub issue: https://github.com/librespot-org/librespot/issues/398

I'm running different receivers for different protocols on a single node:

RAAT (using Roon Bridge) (best for Roon)
Airport (using shairport-sync) (best when using a mac for random stuff)

And I would love to be able to run librespot as well (best for Spotify with portability in mind).

Both RAAT and Airport will acquire/release the device when they need to play sound, and play nice with each other.

Librespot on the other hand tries to lock the device at startup, and will NOT release it unless stopped.
Unfortunately, this makes it not practical to run librespot alongside other stacks sharing /dev/snd.

I'm not familiar with the low level details here, neither with librespot implementation. Is the problem I'm describing specific to rodio?

Or am I missing something?

Thanks for librespot either way!

Originally created by @dubo-dubon-duponey on GitHub (Nov 9, 2019). Original GitHub issue: https://github.com/librespot-org/librespot/issues/398 I'm running different receivers for different protocols on a single node: * RAAT (using [Roon Bridge](https://kb.roonlabs.com/RoonBridge)) (best for Roon) * Airport (using [shairport-sync](https://github.com/mikebrady/shairport-sync)) (best when using a mac for random stuff) And I would love to be able to run librespot as well (best for Spotify with portability in mind). Both RAAT and Airport will acquire/release the device *when they need to play sound*, and play nice with each other. Librespot on the other hand tries to lock the device at startup, and will NOT release it unless stopped. Unfortunately, this makes it not practical to run librespot alongside other stacks sharing /dev/snd. I'm not familiar with the low level details here, neither with librespot implementation. Is the problem I'm describing specific to rodio? Or am I missing something? Thanks for librespot either way!

kerem closed this issue

2026-02-27 19:29:40 +03:00

kerem commented

2026-02-27 19:29:40 +03:00

Author

Owner

@kingosticks commented on GitHub (Nov 9, 2019):

Yes, it is specific to rodio. The ALSA backend does not behave this way (see #68).

@kingosticks commented on GitHub (Nov 9, 2019): Yes, it is specific to rodio. The ALSA backend does not behave this way (see #68).

kerem commented

2026-02-27 19:29:40 +03:00

Author

Owner

@dubo-dubon-duponey commented on GitHub (Nov 9, 2019):

\o/

Compiling now.

THANKS!

@dubo-dubon-duponey commented on GitHub (Nov 9, 2019): \o/ Compiling now. THANKS!

kerem commented

2026-02-27 19:29:41 +03:00

Author

Owner

@dubo-dubon-duponey commented on GitHub (Nov 9, 2019):

Confirmed working ok with alsa backend.
Thanks again!

@dubo-dubon-duponey commented on GitHub (Nov 9, 2019): Confirmed working ok with alsa backend. Thanks again!

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/librespot#253

No description provided.

Rows
Columns