Redrum wrote: > I'm Not sure I understand this response. Are you referring specifically > to playlists? Because I described in excruciating detail how to cause > disruption by adding to the queue in this thread, in the attached > document. > > If you are referring specifically to playlists, then, sure. I can > document steps to disrupt (and be concise, I promise :)). My original > journey down this rabbit hole started with adding multiple streams to > the queue and creating a playlist. With the contents moved to the queue, > there was allot of unexpected behavior when selecting position 1, then > 3, then 2, etc. That ended up with my "I broke LMS" thread.
"a playlist of radio streams" can be interpreted in a few ways. LSM has an active playlist for each audioplayer. * A user can use a UI, adding one item one at a time to the playlist. This is the sort of playlist that is being described in 1st post. * A user can create with a text editor or some other tools a playlist file. There are a number of formats for these files such as m3u, pls, asx, ram etc. In this case, the user via UI requests to play a playlist file. Each item in the playlist file is usually processed by the specific playlist parser which in turn adds to the queue each item the parser finds & checks. * With some plugins such as my iHeart, when a user selects to play a station, whilst iHeart has a radio playlist for each station, it is the plugin which adds each streaming URL separately to queue. Usually up to 4 playable items will be added to the queue - each item is a single playable URL. * With some other "radio" plugins, playing an item may add a radio playlist URL so although only one item appears in the queue, there are multiple URLs in the radio playlist and it may be a protocolhandler which selects next item to be played. With the various possibilities and interpretations of "radio playlist" - more details are needed to determine if the two problems described are symptoms of the same issues, even if the symptoms are similar. If the problem is readily reproducible such as with a copy of the playlist file and a specific system setup, then identifying the problem should not take time - solving it may take time. But as you have suggested, and I, and I am sure others would agree, is it worth even thinking about for the 0.01% that might want to have this work predictably? I think time has convinced me that it isn't. ------------------------------------------------------------------------ bpa's Profile: http://forums.slimdevices.com/member.php?userid=1806 View this thread: http://forums.slimdevices.com/showthread.php?t=116205 _______________________________________________ Squeezecenter mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/squeezecenter
