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

Delayed interactions since librespot 0.4 #1310

Open
honza opened this issue Oct 31, 2024 · 9 comments
Open

Delayed interactions since librespot 0.4 #1310

honza opened this issue Oct 31, 2024 · 9 comments
Labels
bug A functionality or parts of a program that do not work as intended

Comments

@honza
Copy link

honza commented Oct 31, 2024

I'm using Fedora 41. Stable rust to compile myself.

My config is simple:

[global]
device_name = "..."
device = "front:CARD=Generic_1,DEV=0"
zeroconf_port = 1234

Since f53deb9, starting/stopping playback, changing songs, and changing volume takes a long time. Volume especially (I change the volume on my phone and it takes 10s to react on the server where before it's instant).

I tried updating librespot to 0.4.2 and even trying @davidgauch librespot 0.5 PR #1309 and those are unchanged.

What can I do to debug this?

@honza honza added the bug A functionality or parts of a program that do not work as intended label Oct 31, 2024
@eladyn
Copy link
Member

eladyn commented Dec 29, 2024

Maybe you can retry with the branch in #1317? I assume you're talking about controlling playback via one of the official apps?

@honza
Copy link
Author

honza commented Dec 30, 2024

Unfortunately, it doesn't resolve my problem.

@eladyn
Copy link
Member

eladyn commented Dec 30, 2024

That's unfortunate. Just to make sure, you're controlling spotifyd from an official app?
If you run spotifyd with the --verbose flag, it's probably going to dump out a lot of things, but maybe you can try that and see, when the command to play/pause arrives on the device by waiting for new logs after pressing the button?

@honza
Copy link
Author

honza commented Dec 30, 2024

That's unfortunate. Just to make sure, you're controlling spotifyd from an official app?

Yes, iOS client.

I'll have another look at the logs.

@honza
Copy link
Author

honza commented Jan 6, 2025

There don't seem to be any errors in the logs that I can see. :(

@eladyn
Copy link
Member

eladyn commented Jan 6, 2025

I didn't expect errors to appear but just general log messages. So when spotifyd receives the command it will print things to the console and you can maybe examine how long it takes from pressing the button to new logs appearing.

@honza
Copy link
Author

honza commented Jan 7, 2025

The output is extremely busy so it's impossible to correlate. I'll have to hack around and decrease the amount of stuff logged.

@honza
Copy link
Author

honza commented Jan 7, 2025

Removing the --verbose flag, I see that tracks are found and loaded immediately but take several seconds to actually start playing:

Jan 07 15:34:16 yoda spotifyd[8139]: Loading <All These People> with Spotify URI <spotify:track:5gKEJxGeBpyztwPAWp3mRd>
Jan 07 15:34:17 yoda spotifyd[8139]: <All These People> (232466 ms) loaded

Volume changes aren't logged.

@eladyn
Copy link
Member

eladyn commented Jan 18, 2025

Thank you for looking into this. That behaviour indeed sounds strange. My next guess would be that it might be related to playback things? I'm assuming you're using the alsa backend and softvol as volume control?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug A functionality or parts of a program that do not work as intended
Projects
None yet
Development

No branches or pull requests

2 participants