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

No visual indication of played trackin the Spotify desktop app when playing through Spotify Connect. #1127

Open
eldar opened this issue Mar 6, 2023 · 1 comment
Labels

Comments

@eldar
Copy link

eldar commented Mar 6, 2023

Describe the bug
I am using librespot indirectly as a Spotify Connect renderer in the moOde player. I control the playback via the official Spotify desktop app on Linux. The problem is that there is no visual indication in the desktop app of which track is currently playing, that is highlighting in green and the dancing bars. Here is the screnshot demonstrating the problem. When playing music on my Android phone, the desktop app correctly renders highlighting as shown here.

To reproduce
As I'm using librespot as a part of another app, it's a bit difficult to get the logs.

  1. Launch moOde player on Raspberry Pi 4
  2. Launch the official desktop Spotify app, connect to the moOde player via Spotify Connect.
  3. Start playing any track.
  4. The track isn't highlighted in the album list view.

Log
A bit difficult

Host (what you are running librespot on):

  • OS server: moOde audio, Debian 11
  • Platform: Raspberry Pi 4b
  • OS client: both Linux and Windows.

Additional context
I suspect that librespot does not communicate everything that is to communicate the currently playing track. This could also be that I'm running an older version of librespot: 0.4.1.

@photovoltex
Copy link
Member

Hey @eldar,

with the dealer now implemented, this should be fixed for the most parts. I'm only aware that for albums started via the api, desktop or web-player this is still an issue. Any item started from mobile should show correctly.

We probably can keep the issue open because it isn't fully resolved, but could you verify that your issue is mostly resolved with the latest changes?

thanks in advance^^

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants