>If I am moving around to different >players a lot, it tends to rack up a bunch of extra tracks at the end >of the playlist, but this isn't a bit deal. > I haven't noticed many problems like that myself; can you provide an example for when it adds extra tracks?
I think mostly, it's likely to be the way that DynamicPlaylist works. I just return the next track to play, when I handle a request from Dynamic Playlist to queue another track. I can probably make this work better - check the position of the currently playing track, and only queue a new track when it's at the end of the playlist. In fact, I meant to make this honour the other DynamicPlaylist settings. "Now Playing will show <n> upcoming songs and <n> recently played songs", rather than just add a single future track each time a new track is played. So I'll probably implement that next. >One thing that would be cool is if it could be enabled all the time, >like Sugarcube is, instead of having to kick it off and then having it >stop when something new is played. With Sugarcube, there was a setting, >"Only Queue a New Track if Playing the last Track on the Playlist" and >with this checked, I could get endless music without having to think >much about it as long as a local file was the last thing in the >playlist. > I didn't like that mode of operation much; I was specifically concentrating on DynamicPlaylist integration, rather than copy SugarCube. Dynamic Playlist works by automatically turning off when something else is played. i.e. the user doesn't have to remember to turn it off when queueing up other music to play. I don't think I can stop that behaviour, if I want to use Dynamic Playlist to handle the playlist size/history. Best to use SugarCube if you want to add songs into a mix and evolve from that. _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/plugins
