If I limit the number of tracks or albums in the restriction section, it doesn't return 'whole albums' like you described.
You need to post the rules you're using.
That said, I don't think musicbee is programmed to do what you want. There is often a discrepancy between human 'logic' and cold, hard programmed logic. If you post your rules, it will help to explain any misunderstanding you have about what musicbee is programmed to do.
For example, take the restriction rule:
limit to 10 albums selected by 'most often played', grouped by album
In English that sounds exactly what you want.
But under the hood, programmatically, it means something like:
· Look for the highest track playcount. Add it to the list. Look at the album name and count it as one.
· Repeat step 1 continuously. Keep looking at the album name and stop when there are ten different album names in the list.
· Finally, instead of applying the 'playlist order #' by highest to lowest playcount and then displaying the list alphabetically by
album -> track#, group the tracks alphabetically by album -> track#, *then* apply the 'playlist order #', then display
alphabetically by album -> track#.
This returns partial albums, and not in playcount order: not what you thought you were going to get at all!! If you then try to sort by playcount -> album (by ctrl-clicking on columns), you'll find that it doesn't sort and group 'by most played album' because the logic for that kind of operation simply hasn't been programmed.
Anyway, post your auotplaylist rules, and we can pick holes in your logical fallacies and see if Steven will come up with something to help.