What is the reason that you don't think it's easy to maintain the
genres in SQL Playlist ?
Is it because you are going to want to exclude the same genres in
several playlists ?
Yes, probably. Quite often I want to use dynamic playlists without any
built-in genre filtering, and then depending on
An additional change you can try if you use this in a new 7.1 release,
is that you could replace track_statistics with tracks_persistent
and join using tracks_persistent.track instead. This would be something
like:
I just tried this and it returned a track that had a rating.
select tracks.url,
I created a SQLPlaylist to play random songs that haven't yet been rated. I
did this instead of using the standard Not Rated Songs trackstat dynamic
playlist, because that one includes ordering by playcount, which totally biases
the randomness.
I also wanted to exclude certain genres. I
Custom Skip isn't very effective if you like the skip many tracks.
When Dynamic Playlist needs more tracks, the following happens:
1.
It retrieves additional tracks from the plugin that supplies the
playlist. In the case of a SQL Playlist playlist this means that it
executes the SQL statement
