Tweet
Hello,
Looking at the Door Controller block gave me a weird idea: would it be possible to use this as a media controller block that shows album art? The functionality of the three buttons can be chosen, so they could be e.g. play / previous / next. For squeezeboxes, the album art can be fetched via http:
-
AlbumID and TrackID are SqueezeCenter's database identifiers. They can be used to call back into SqueezeCenter's HTTP and CLI interfaces (eg, to retreive artwork). For example, the thumbnail image for a track can be retrieved using the track id from:
http://<slimserver>:<port>/music/<trackid>/thumb.jpg
The thumbnail for the currently playing track on a player can be retieved using the playerid from:
http://<slimserver>:<port>/music/current/cover.jpg?player=<playerid>
The playerid (which can be found in a Transport.Info block) will have to be 'url escaped' in this case since it contains ':' characters that are not allowed in their raw form in a URL (the playerID is the player's ethernet MAC address).
-
The second format shows the album art for the current playing one, so the url can even be hardcoded and it does not seem to need any data from the server.
Not sure if this would work, but just throwing it here as an idea... Any takers?
Jörg
Looking at the Door Controller block gave me a weird idea: would it be possible to use this as a media controller block that shows album art? The functionality of the three buttons can be chosen, so they could be e.g. play / previous / next. For squeezeboxes, the album art can be fetched via http:
-
AlbumID and TrackID are SqueezeCenter's database identifiers. They can be used to call back into SqueezeCenter's HTTP and CLI interfaces (eg, to retreive artwork). For example, the thumbnail image for a track can be retrieved using the track id from:
http://<slimserver>:<port>/music/<trackid>/thumb.jpg
The thumbnail for the currently playing track on a player can be retieved using the playerid from:
http://<slimserver>:<port>/music/current/cover.jpg?player=<playerid>
The playerid (which can be found in a Transport.Info block) will have to be 'url escaped' in this case since it contains ':' characters that are not allowed in their raw form in a URL (the playerID is the player's ethernet MAC address).
-
The second format shows the album art for the current playing one, so the url can even be hardcoded and it does not seem to need any data from the server.
Not sure if this would work, but just throwing it here as an idea... Any takers?
Jörg