rules that sometimes work and sometimes gives errors (cant fit criteria etc.) without any rational reason (to us)
When it builds a playlist, it adds tracks one by one. Each next track has to fit all the defined criteria: priority rules, filters, repeat protection rules. If you see the error messages, that means your rules are too strict. To fix this problem you should:
- make the rules less strict: less filters and decrease the repeat protection periods, review the priority rules
- add more tracks to categories so that it has more tracks to choose from
You have to make sure there are no error messages when the playlist is created.
The error message provides you with information on what went wrong.
> ERROR: Unable to find track that fits criteria (rule: norepeat-artist). Category: "abc"
Means that your artist repeat protection ("Do not repeat artist for") rule is too strict.
This is about the "Do not repeat track for" rule.
I dont see a real balance inside each generation, is like things are more done casually than with an exact logic;
It's random track selection and it simply makes sure that:
A. The tracks are carefully shuffled (internally it uses a high quality random number generator)
B. The created playlist fits the defined criteria: repeat protection rules, filters, category order etc.
You should use the priority rules to further refine the track selection:
- use priorities to increase probability for tracks that were not played recently (your rules "decrease priority by 10 for tracks where last played is less than..." will take care of that).
“decrease priority by 10 for tracks where last played is less than 1 day ago”
“decrease priority by 10 for tracks where last played is less than 3 day ago”
“decrease priority by 10 for tracks where last played is less than 5 day ago”
Please note that rules add up, and for a track that was played 12 hours ago, all those rules will apply and in total its priority will be decreased by 30.
another big problem is that also with all the rules reported “never play and categories balance” lets say today are generated few playlists without any problem/error, tomorrow generating exactly that playlist at same time I see the following errors
This is because the conditions are different each time. The "Last played" tag is updated as songs are played - it affects the priorities assigned and repeat protection. The tracks that were played recently also affect playlist creation as it checks what was played recently and it has to follow repeat protection rules.
we are really in trouble as often few songs categories are skipped and the playlist generated is totally unreliable with some categories played also 2/3 times in a row
The solution is to lessen the repeat periods for all repeat protection rules. From the error messages you get, it is clear that the rules are the problem. Change the rules and then try to create playlist e.g. 10 times in a row. You need to be sure there are never error messages. If they are, the rules need to be reviewed further.