mirror of
https://github.com/librespot-org/librespot.git
synced 2026-04-27 08:15:50 +03:00
[GH-ISSUE #1127] No visual indication of played trackin the Spotify desktop app when playing through Spotify Connect. #528
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#528
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 @eldar on GitHub (Mar 6, 2023).
Original GitHub issue: https://github.com/librespot-org/librespot/issues/1127
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.
Log
A bit difficult
Host (what you are running
librespoton):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 commented on GitHub (Dec 20, 2024):
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^^