mirror of
https://github.com/librespot-org/librespot.git
synced 2026-04-27 00:05:55 +03:00
[GH-ISSUE #1047] librespot failing with rodio #493
Labels
No labels
A-Alsa
SpotifyAPI
Tokio 1.0
audio
bug
can't reproduce
compilation
dependencies
duplicate
enhancement
good first issue
help wanted
high priority
imported
imported
invalid
new api
pull-request
question
reverse engineering
wiki
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/librespot#493
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 @ghost on GitHub (Aug 18, 2022).
Original GitHub issue: https://github.com/librespot-org/librespot/issues/1047
Describe the bug
librespotfails to output audio when using the defaultrodiobackendTo reproduce
Install
librespoteither via snap (librespot-dev) or by compiling.The Spotify "sink" is detected by Spotify clients on the network. Clients can select the Spotify sink.
When trying to play music, a bunch of errors are spat out on the server side.
However if I enable the
alsabackend when compiling and use that backend, things work just fine.I have tried to run as root and the same happens.
Log
Host (what you are running
librespoton):Tried on Debian Bullseye (snap and compiled) and KDE Neon (snap only)
Thank you.
@roderickvd commented on GitHub (Aug 18, 2022):
Are you sure your playback device is OK? What happens when you open this output device with the Alsa backend?
Can’t hurt not blowing up with that
unwrapthough.@ghost commented on GitHub (Aug 18, 2022):
Things work like a charm with
$ ./target/release/librespot -n nas --backend alsa. Do you need a log with the alsa backend?@roderickvd commented on GitHub (Aug 18, 2022):
Yes please.
@ghost commented on GitHub (Aug 18, 2022):
Here you go, I hope this helps:
@roderickvd commented on GitHub (Aug 18, 2022):
Could you make it a verbose log so I can see the Alsa details?
@ghost commented on GitHub (Aug 18, 2022):
Apologies. Here you go:
@roderickvd commented on GitHub (Aug 20, 2022):
I think that you should report this to Rodio. It seems that your playback device is finicky with setting buffers and Rodio bails out on that. Our own Alsa implementation works around such peculiarities, some great work by @JasonLG1979.
@JasonLG1979 commented on GitHub (Aug 20, 2022):
You flatter me. The code more resembles a drunken stumble than anything,lol!!!
In this particular case when configuring
HwParamsif you get any errors thatHwParamsobject becomes garbage. It should not be used.All I did was clone the
HwParamsbefore I start to configure the buffer, if at any point I get an error after that I cut and run and use the clonedHwParamsand it's default buffer settings whatever they might be instead of theHwParamsthat's in an error state.