>This is planned, I just have to figure out how to do it. > Perhaps you should add a note to the readme?
BTW, I thought it would be nice to have a Browse Mode for SQL playlists, or add the automatic playlists to the Browse Playlists mode, if that's possible (player UI and web UI). >But I am also thinking it might be usefull to be able to enter the SQL >directly in the web UI instead of putting it in a SQL file. > Yes, that would be a nice easy starting point. List the SQL Playlists - can add/edit/delete the text and provide a "Save/Save As". >Do you see any more useful functionallity that would be nice to have in a web >UI? > How about an option to take it in/out of automatic playlist mode (so the user is able to stop more tracks being added to the end of the current playlist). >The main reason I wrote it was that "exclude genres" does not work in >the Random playlist plugin if you have multiple genres in a track. > I realised that too - I don't like the Random playlist including instead of excluding. I was kind of hoping that the Random mix interface might change to have some kind of tri-state genre state, and perhaps genre groups for easier selection. >However, a possible to extension might be to make a >web UI that makes it easy to generate a SQL playlist sql-files even >though the user does not know SQL. > That would be really nice. There must be loads of other software applications that provide nice ways of generating SQL queries. >Maybe implement a web UI similar to >Random playlist that generates the *.sql file or something. Is it >something like this you had in mind, or were you just looking for a way >to get Random playlist plugin playlists and SQL playlist plugin >playlists below the same main menu ? > The latter really. I guess it is possible to duplicate the Random Mix modes in the SQL playlist plugin, but without the GUI to select genres and playlist length, etc. >I am not sure that there is an easy way to catch the search SQL without >patching the original slimserver. But I also think most of the search >criterias in advanced search are not interesting to use to make a >playlist. > I was thinking along the lines of having a "Save as automatic playlist" button on the Search and Advanced Search pages. It could prompt for whether the user wants tracks in order or random. At least it would be quick and easy to generate automatic playlists to do things like "Random Progressive Rock Tracks from 1974". This would provide a starting block for the SQL - the user could enhance the SQL Playlist manually for more complicated stuff. Other useful search criteria for me would be: "Comment": Find tracks that contain various category info that I sometimes add in comment tags. "track length": So I could exclude short tracks, etc. "track number": Could have a playlist to play only the first track of each album. >If you want to create playlists for a single >artist or a single album it is better to do this as a normal playlist. It's nice to save them as auto playlists with the order by random() feature and a rolling playlist though. If I were to try to queue up all of my Pink Floyd tracks, I'd have a huge playlist and might get bored after a few days. Phil _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/plugins
