mirror of
https://github.com/librespot-org/librespot.git
synced 2026-04-27 16:25:52 +03:00
[GH-ISSUE #1174] Spotify for Artist doesn’t count streaming with new LIBRESPOT #544
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#544
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 @enricobuja on GitHub (Jun 7, 2023).
Original GitHub issue: https://github.com/librespot-org/librespot/issues/1174
Hi, there is an important problem in the new librespot! Volumio software installed on raspberry pi zero w using this new library for his Spotify connect plug-in and the problem is that Spotify for artist doesn’t count the streaming made from this plug in that use your library for connect to Spotify library. The old plug in was perfect because used the old version of librespot and the streaming count was every time regular, but now ZERO! this is important because is like a pirate protocol streaming now, because Spotify doesn’t pay the royalty to the artists in this case because this library doesn’t permit the count of it! So please check what is change from old to new library and correct otherwise is against the law! Let me know updates so I can try if the problem is correct thanks.
@michaelherger commented on GitHub (Jun 7, 2023):
See also https://github.com/librespot-org/librespot/discussions/626
@kingosticks commented on GitHub (Jun 7, 2023):
No need for the hyperbole, thanks.
As per the linked issue above, reporting has not worked since at least 2019 - I'm pretty sure reporting has never worked. But you appear to be saying it used to work and now doesn't. So can you please clarify how #626 differs from what you are describing and also provide the revision where it used to work.
@roderickvd commented on GitHub (Jun 28, 2023):
Indeed seems like a duplicate to me.