mherger wrote:
> The command adding that URL to a playlist then is responsible of
> grabbing the track information it wants to show. That's why I keep
> asking for the command used in this action.
As stated earlier, it is Material that is invoking JSONRPC to add a
track to a -stored- playlist via:
Code:
--------------------
["playlists", "edit", "playlist_id:<playlist id>", "cmd:add", "url:<track
url>"]
--------------------
Note no metadata is sent, simply the track's URL. I've looked at the LMS
code (playlistsEditCommand in Slim/Control/Commands.pm) and can see that
I could also pass 'title' - but, in my experience, this does not seem to
be required. However, I fail to see why there would be a difference
between a track added via DSTM or manually, both -should- have the same
URL. Perhaps as its added manually LMS cache's the meta-data so knows
what to write to the M3U file?
I could update my call to pass "title:XXXX" - but not sure what should
be in the title. Just title? Artist? Album? If so what format? "Title -
Artist, Album" ???
-----
The above is assuming you mean "stored playlist" by "playlist" and not
the current play -queue-. (This is the reason I call the play queue
"play queue" and not "play list" - to make the difference obvious).
*Material debug:* 1. Launch via http: //SERVER:9000/material/?debug=json
(Use http: //SERVER:9000/material/?debug=json,cometd to also see update
messages, e.g. play queue) 2. Open browser's developer tools 3. Open
console tab in developer tools 4. REQ/RESP messages sent to/from LMS
will be logged here.
------------------------------------------------------------------------
cpd73's Profile: http://forums.slimdevices.com/member.php?userid=66686
View this thread: http://forums.slimdevices.com/showthread.php?t=105757
_______________________________________________
beta mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/beta
