[GH-ISSUE #98] Metadata again.. #85

Closed
opened 2026-02-27 19:28:45 +03:00 by kerem · 8 comments
Owner

Originally created by @sashahilton00 on GitHub (Jan 29, 2018).
Original GitHub issue: https://github.com/librespot-org/librespot/issues/98

Issue by frafall
Saturday Nov 25, 2017 at 04:03 GMT
Originally opened as https://github.com/plietar/librespot/issues/266


Metadata/tags has been sadly overlooked, as it is now every integration patches its own.

I suggest we address this by making metadata available in the audio_backend.

Ex. Pulseaudio has a more or less well defined API where it uses properties, Airplay supports its own tags, for the stdout backend we can continue to use stderr as the simple "Track loading" stuff does today but should be expanded with more tags. Currently metadata is not a part of the audio backend API at all as far as I can tell.

Also, all the basic tags should be available without having to lookup in Spotify again as that would push complexity into audio distribution (Pulseaudio, Snapcast). Adding a tag for Spotify reference would be nice to enable elaborate UI's (ex Kodi with a lot of track info) but basic info should be available without complexity.

Any ideas?

Originally created by @sashahilton00 on GitHub (Jan 29, 2018). Original GitHub issue: https://github.com/librespot-org/librespot/issues/98 <a href="https://github.com/frafall"><img src="https://avatars1.githubusercontent.com/u/8217925?v=4" align="left" width="96" height="96" hspace="10"></img></a> **Issue by [frafall](https://github.com/frafall)** _Saturday Nov 25, 2017 at 04:03 GMT_ _Originally opened as https://github.com/plietar/librespot/issues/266_ ---- Metadata/tags has been sadly overlooked, as it is now every integration patches its own. I suggest we address this by making metadata available in the audio_backend. Ex. Pulseaudio has a more or less well defined API where it uses [properties](https://freedesktop.org/software/pulseaudio/doxygen/proplist_8h.html), Airplay supports its own tags, for the stdout backend we can continue to use stderr as the simple "Track loading" stuff does today but should be expanded with more tags. Currently metadata is not a part of the audio backend API at all as far as I can tell. Also, all the basic tags should be available without having to lookup in Spotify again as that would push complexity into audio distribution (Pulseaudio, Snapcast). Adding a tag for Spotify reference would be nice to enable elaborate UI's (ex Kodi with a lot of track info) but basic info should be available without complexity. Any ideas?
kerem 2026-02-27 19:28:45 +03:00
Author
Owner

@sashahilton00 commented on GitHub (Jan 29, 2018):

Comment by frafall
Thursday Nov 30, 2017 at 07:16 GMT


Hmm, is this maintained at all anymore? Or moved somewhere else?

Anyone?

<!-- gh-comment-id:361278143 --> @sashahilton00 commented on GitHub (Jan 29, 2018): <a href="https://github.com/frafall"><img src="https://avatars1.githubusercontent.com/u/8217925?v=4" align="left" width="48" height="48" hspace="10"></img></a> **Comment by [frafall](https://github.com/frafall)** _Thursday Nov 30, 2017 at 07:16 GMT_ ---- Hmm, is this maintained at all anymore? Or moved somewhere else? Anyone?
Author
Owner

@sashahilton00 commented on GitHub (Jan 29, 2018):

Comment by herrwusel
Thursday Nov 30, 2017 at 07:37 GMT


See the readme here:
https://github.com/plietar/librespot#unmaintained

<!-- gh-comment-id:361278163 --> @sashahilton00 commented on GitHub (Jan 29, 2018): <a href="https://github.com/herrwusel"><img src="https://avatars1.githubusercontent.com/u/8242787?v=4" align="left" width="48" height="48" hspace="10"></img></a> **Comment by [herrwusel](https://github.com/herrwusel)** _Thursday Nov 30, 2017 at 07:37 GMT_ ---- See the readme here: https://github.com/plietar/librespot#unmaintained
Author
Owner

@sashahilton00 commented on GitHub (Jan 29, 2018):

Comment by frafall
Friday Dec 01, 2017 at 10:37 GMT


Ye, have any1 come forward to take ownership or do we all fragment it into our own special versions?
It's a brilliant piece of code and I'd hate to see it fragment :(

<!-- gh-comment-id:361278190 --> @sashahilton00 commented on GitHub (Jan 29, 2018): <a href="https://github.com/frafall"><img src="https://avatars1.githubusercontent.com/u/8217925?v=4" align="left" width="48" height="48" hspace="10"></img></a> **Comment by [frafall](https://github.com/frafall)** _Friday Dec 01, 2017 at 10:37 GMT_ ---- Ye, have any1 come forward to take ownership or do we all fragment it into our own special versions? It's a brilliant piece of code and I'd hate to see it fragment :(
Author
Owner

@sashahilton00 commented on GitHub (Jan 29, 2018):

Comment by herrwusel
Friday Dec 01, 2017 at 10:52 GMT


Sorry but another url again:
https://github.com/plietar/librespot/issues/263#issuecomment-348066472

Maybe you step forward? :)

<!-- gh-comment-id:361278217 --> @sashahilton00 commented on GitHub (Jan 29, 2018): <a href="https://github.com/herrwusel"><img src="https://avatars1.githubusercontent.com/u/8242787?v=4" align="left" width="48" height="48" hspace="10"></img></a> **Comment by [herrwusel](https://github.com/herrwusel)** _Friday Dec 01, 2017 at 10:52 GMT_ ---- Sorry but another url again: https://github.com/plietar/librespot/issues/263#issuecomment-348066472 Maybe you step forward? :)
Author
Owner

@sashahilton00 commented on GitHub (Jan 29, 2018):

Comment by frafall
Saturday Dec 02, 2017 at 13:42 GMT


Tempting but my rust skills are more than rusty S
We are probably better off with someone who can evaluate pulls...

<!-- gh-comment-id:361278245 --> @sashahilton00 commented on GitHub (Jan 29, 2018): <a href="https://github.com/frafall"><img src="https://avatars1.githubusercontent.com/u/8217925?v=4" align="left" width="48" height="48" hspace="10"></img></a> **Comment by [frafall](https://github.com/frafall)** _Saturday Dec 02, 2017 at 13:42 GMT_ ---- Tempting but my rust skills are more than rusty *S* We are probably better off with someone who can evaluate pulls...
Author
Owner

@sashahilton00 commented on GitHub (Jan 29, 2018):

Comment by sashahilton00
Sunday Jan 28, 2018 at 23:58 GMT


@frafall see https://github.com/librespot-org/librespot the recent successor.

<!-- gh-comment-id:361278267 --> @sashahilton00 commented on GitHub (Jan 29, 2018): <a href="https://github.com/sashahilton00"><img src="https://avatars3.githubusercontent.com/u/4185362?v=4" align="left" width="48" height="48" hspace="10"></img></a> **Comment by [sashahilton00](https://github.com/sashahilton00)** _Sunday Jan 28, 2018 at 23:58 GMT_ ---- @frafall see https://github.com/librespot-org/librespot the recent successor.
Author
Owner

@sashahilton00 commented on GitHub (Jan 29, 2018):

Comment by frafall
Monday Jan 29, 2018 at 07:54 GMT


This is good new indeed!

👍

<!-- gh-comment-id:361278286 --> @sashahilton00 commented on GitHub (Jan 29, 2018): <a href="https://github.com/frafall"><img src="https://avatars1.githubusercontent.com/u/8217925?v=4" align="left" width="48" height="48" hspace="10"></img></a> **Comment by [frafall](https://github.com/frafall)** _Monday Jan 29, 2018 at 07:54 GMT_ ---- This is good new indeed! :+1:
Author
Owner

@ComlOnline commented on GitHub (Jan 29, 2018):

Please see #7 for continued discussion.

<!-- gh-comment-id:361318455 --> @ComlOnline commented on GitHub (Jan 29, 2018): Please see #7 for continued discussion.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/librespot#85
No description provided.