mirror of
https://github.com/librespot-org/librespot.git
synced 2026-04-27 00:05:55 +03:00
[GH-ISSUE #592] Extra metadata beyond title/URI #374
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#374
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 @micronova-jb on GitHub (Feb 1, 2021).
Original GitHub issue: https://github.com/librespot-org/librespot/issues/592
Hello! First, I'd like to say thanks creating and maintaining such a great project. I am using librespot as part of a different project I'm working on, and we're trying to get metadata from the songs played on Spotify. The typical console output is the song title, URI, and its length in milliseconds. Does Librespot itself gather more data than this? I'm having a difficult time figuring this out. I have found plenty of other projects that accomplish this goal, but they tend to be outside of the scope of what I'm working on.
The metadata that would be great to have would be:
Is it possible to accomplish this with just Librespot? Does Spotify keep that information hidden? I appreciate any help/answers you can provide!
@Johannesd3 commented on GitHub (Feb 1, 2021):
Are you using librespot as library in other Rust code, or are you just invoking the application?
@micronova-jb commented on GitHub (Feb 2, 2021):
I'm calling it via something like "librespot -n 'test audio' --verbose".
I'm not integrating it into other rust code
On Mon, Feb 1, 2021, 6:11 PM Johannesd3 notifications@github.com wrote:
@Johannesd3 commented on GitHub (Feb 2, 2021):
The simplest solution is probably to use the official Web API.
@ashthespy commented on GitHub (Feb 2, 2021):
Yeah it is (with
librespotthe library), but won't be added to Librespot the binary for reasons - #7I wrapped Librespot into a little daemon a while back that exposes metadata on a udp socket. Currently all you seek should be included. There are some prebuilt releases, if you want to give it a whirl..
@micronova-jb commented on GitHub (Feb 2, 2021):
Thank you both for the responses! I can try both of these out to see which works better for my team's project.
@ashthespy I think I will look into your project first :) I'm basically just using a Raspberry Pi as a Spotify Connect device - is it possible to use your daemon without installing Volumio?
@ashthespy commented on GitHub (Feb 2, 2021):
Sure, you don't need Volumio. Pick the right release version based on which Pi your using (
armhfvsarmv6).Have a look at this snippet on how you can read the metadata with NodeJs
@micronova-jb commented on GitHub (Jul 14, 2021):
@ashthespy Sorry for the complete radio silence over the past few months! Things got really crazy at work, and I was working on a lot of the other features for our AmpliPi system (neglecting Spotify). I initially couldn't figure out the vollibrespot integration, but after more digging this week, it's working quite well for me! Your daemon does everything I wanted and more - full metadata (including album art), as well as play/pause/seek integration. Just wanted to come back to this issue to properly thank you for your awesome work :)
@kingosticks commented on GitHub (Jul 14, 2021):
@micronova-jb are you distributing librespot with your system? Any sort of integration should include the librespot disclaimer so users know the risks and understand that what they are using is a reverse-engineered solution which may violate Spotfy's ToS. Everything built on librespot should do this but I think it's particuarly important if you are selling something. I assume you are supposed to pay Spotify a heap of cash to officially use their service in a product and then do so using their (non-public) software.
@micronova-jb commented on GitHub (Jul 14, 2021):
@kingosticks Yes, we are planning on distributing Librespot as part of our open-source project AmpliPi. Our business model is to sell the hardware that the open-source software runs on. It is a hobbyist project, and our users understand the limitations; we have recently updated some of our documentation to make it clear that Spotify support is provided by Librespot, including a link to the project and disclaimer in our README. The only units that currently exist in the field belong to AmpliPi developers.
@ashthespy commented on GitHub (Jul 15, 2021):
@micronova-jb That is good to hear, I have a few more things to sort out regarding sharing of the sink, will happen when I find time ;-)