What does it take to get for LMS to put an entry in its library?
LMS' schema is based on tracks. Tracks belong to an album, and tracks can have contributors. So... if you could store all the tracks from your streaming service in the tracks table, that would be a great start. Eg. spotify://track:abcd1234 could be stored in the table. BUT the problem is, that many places in the code base assume this file to be a local file, nothing remote or virtual. We'd not only have to have some routine to get all those URLs in the tracks table, but we'd also have to modify LMS to deal with them correctly... and I guess that would be the large bulk of work.
Presumably at least one recognizable sound file (MP3, FLAC, etc.). Could I fool it with (1) an "album" comprising album art (from the album I'm interested in), one "dummy" track (from anywhere?) and (2) a link to a Spotify album entry maybe via album art or the track name? The first bit is easy but I'm not sure about the second . . .
I was playing with this idea, too, as it would be much easier to get the album list, rather than all tracks. But then again, the LMS code would assume tracks to be there for the albums. If you wanted to break that schema, you'd have to rewrite a whole lot of code around the database handling...
Let us know about your findings :-) -- Michael _______________________________________________ Squeezecenter mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/squeezecenter
