Good catch. Added -drop table if exists- to those a couple of playlists where it was still missing. You'd probably only run into this problem if the sql query errors out before the end where the temp. table is dropped. But having it in the beginning is quicker than a LMS restart.
> Also, it looks like the results of our own custom queries are still > always randomized. It would be nice to have that become optional. Works already for *album* playlists (incl. custom) that include the PlaylistParameter *-- PlaylistContentType:album* (see built-in dyn. playlists for ref.). Still trying to think of other use cases (besides album), dynamic playlists that don't benefit from shuffling? Even if you choose artist, genre, year, decade, or playlist as a starting point, what's actually added are either tracks or albums. For albums it makes sense (that's why I added the option) and random tracks shouldn't mind additional shuffling I guess. ------------------------------------------------------------------------ afriend's Profile: http://forums.slimdevices.com/member.php?userid=39306 View this thread: http://forums.slimdevices.com/showthread.php?t=115073 _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/plugins
