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

Server doesn't respect changes in "default output device" on macOS #745

Open
kubukoz opened this issue Dec 28, 2020 · 8 comments
Open

Server doesn't respect changes in "default output device" on macOS #745

kubukoz opened this issue Dec 28, 2020 · 8 comments
Labels
blocked by: librespot Issues that are blocked by librespot's upstream

Comments

@kubukoz
Copy link

kubukoz commented Dec 28, 2020

Description

The server doesn't change the device playing when the default changes.

To Reproduce

  1. Play music on built-in speakers
  2. Connect headphones or some other extra output
  3. Make sure it's now the device in this menu:

image

  1. Sound still plays on speakers

The same happens if you change the default device yourself.

Expected behavior
Sound switches to the newly "defaulted" device

Logs

Click to show logs

Versions (please complete the following information):

  • OS: macOS Catalina 10.15.6 (19G2021)
  • Spotifyd: 0.2.24
@kubukoz kubukoz added the bug A functionality or parts of a program that do not work as intended label Dec 28, 2020
@nkezhaya
Copy link

nkezhaya commented Jan 2, 2021

+1

@shatteringlass
Copy link

I guess it's a rodio backend bug, rather than related spotifyd. Librespot and ncspot have similar bugs as well. It's worth trying a newer rodio build, including the latest commits.

@stale
Copy link

stale bot commented Apr 5, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix Issues that will not be fixed under any circumstances label Apr 5, 2021
@stale stale bot closed this as completed Apr 15, 2021
@chazzox
Copy link

chazzox commented Mar 17, 2023

Hi! Anyone manage to fix this issue? Currently looking around for a fix. @shatteringlass you said to try a more recent rodio build. How would I go about accomplishing this?

@shatteringlass
Copy link

The issue within rodio was identified to be upstream (RustAudio/rodio#327) and fixed in cpal v.0.14.1, that was merged into rodio only with v0.16.0.
Currently, spotifyd is still using rodio v0.13.1, so the bug could be solved with a simple PR (#1191).

@slondr slondr added blocked by: librespot Issues that are blocked by librespot's upstream and removed bug A functionality or parts of a program that do not work as intended wontfix Issues that will not be fixed under any circumstances labels Mar 18, 2023
@slondr slondr reopened this Mar 18, 2023
@j-code-1

This comment was marked as spam.

@myInstagramAlternative
Copy link

Could this issue be revisited, please? I checked librespot, and rodio is now at version 19.0. Is there anything preventing us from using librespot v0.6.0?

@eladyn
Copy link
Member

eladyn commented Dec 30, 2024

@myInstagramAlternative It has taken some time, but #1317 does exactly this, if you'd be willing to test the changes. (If you're using user+password auth, maybe rather try #1321, since that implements the "new" OAuth flow.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocked by: librespot Issues that are blocked by librespot's upstream
Projects
None yet
Development

No branches or pull requests

8 participants