I have implemented it as per your screenshot. Works great. I'm wondering though why limiting it is necessary? If I uncheck the limit then the results look pretty much random or at least not related to what I'm trying to do. It works even better if I change it from limiting tracks to albums.
I definitely would have been stumped by the Play Count > 0 bit
Thanks for your feedback. There's more than one way to do it.As for the limit:
it is just there to prevent information overload. But IMO, it is not strictly necessary, and I don't see why unticking the option is sort of leading astray. When testing on with my library, I don't notice anything strange.As for select by:
when choosing by album
instead of by track
, you include in the selection the non-played tracks of albums where at least one track has been played. The difference is tangible when selecting view Album and Tracks
, instead of Album Covers
.As for the condition: Play Count > 0
is the most general one.
You could replace it by Last Played - is in the last - # - hours/days/weeks/months
, but it is more restrictive intrinsically.
Anyway, Last Played - has a value
doesn't work, since tracks with Last Played = Unknown
are included in the selection.