[Fork] Metadata

[frafall]

I'm looking into supporting metadata in Snapcast, first commit done. Basically I maintain a per stream struct containing (Artist, Album, Track) and push it to the listening clients, this should be possible to use for album art as well.
For testing I included track pattern search in the Libreelec stderr pattern matching to update the stream metadata. To support more I tags would need a modified Librespot. Simular could be implemented for Shairport-sync (Airplay) streams.
For generic named pipes I'm planning to add a generic json interface to set stream tags and client side some kind of hooks to push stream tags (a callable script, a pipe? ideas?)

I would so wish that ppl who implemented audio interfaces pushed the metadata to the interface implementation, Pulseaudio has a relatively standard property interface for metadata, why haven't Shairport-sync and Libreelec implemented this in their pulseaudio interface? Or to stdout/stderr interface?

-frafall

[palitu]

that is great! keep it up!

…

On Nov 21, 2017 7:58 AM, "frafall" ***@***.***> wrote: I'm looking into supporting metadata in Snapcast, first commit done <https://github.com/frafall/snapcast/tree/develop>. Basically I maintain a per stream struct containing (Artist, Album, Track) and push it to the listening clients, this should be possible to use for album art as well. For testing I included track pattern search in the Libreelec stderr pattern matching to update the stream metadata. To support more I tags would need a modified Librespot <plietar/librespot#154>. Simular could be implemented for Shairport-sync (Airplay) streams. For generic named pipes I'm planning to add a generic json interface to set stream tags and client side some kind of hooks to push stream tags (a callable script, a pipe? ideas?) -frafall — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#310>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AGU9IJynRWGthwgDza6nD6i3lEHRlTQQks5s4dnQgaJpZM4Qkz5j> .

[frafall]

Any ideas on where snapclient should send metadata?
Looking around there are solutions with named pipes, udp packets, scripts 'on_metadata_update.sh'.

To avoid complexity I', thinking about adding a command line '-m <script>' triggered on metadata update with metadata in environment.

Ideas?