mirror of
https://github.com/devgianlu/go-librespot.git
synced 2026-04-27 05:45:49 +03:00
[GH-ISSUE #128] Don't try play while ALSA device is using by other player #77
Labels
No labels
bug
enhancement
pull-request
spotify-side
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/go-librespot#77
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @szygmunt on GitHub (Oct 21, 2024).
Original GitHub issue: https://github.com/devgianlu/go-librespot/issues/128
DEBU[3699] handling pause player command from [UID - edited]
DEBU[3699] pause track at 139981ms
DEBU[3699] put connect state because PLAYER_STATE_CHANGED
DEBU[3699] sending successful reply for dealer request
DEBU[3699] put connect state because PLAYER_STATE_CHANGED
DEBU[3954] handling resume player command from [UID - edited]
ERRO[3954] failed resuming playback error="ALSA error at snd_pcm_open: Device or resource busy"
DEBU[3954] resume track at 139739ms
DEBU[3954] put connect state because PLAYER_STATE_CHANGED
DEBU[3954] sending successful reply for dealer request
DEBU[3954] put connect state because PLAYER_STATE_CHANGED
After that mpd is still playing (as expected) and progress bar in spotify android app goes forward without sound.
Can we handle this scenario in go-librespot (dont resume track while ALSA Device is using by other player)?
@devgianlu commented on GitHub (Oct 22, 2024):
We definitely should not fake being able to play, but instead return an error. I don't think there's any easy way to communicate this specific problem (audio device busy) to the client in a nice way.
@devgianlu commented on GitHub (Oct 22, 2024):
I have implemented a fix, feel free to re-open if this is not fixed.