Same concept, but different criteria, yes. If within the cluster all artists match.
I actually wouldn’t want all the albums to be in the same cluster, though if they were, they still can be separated during saving by
%album%. The intent is to be able to work through a “big ol’e festering mess” of totally disorganized in a process of elimination like way.
Say, sorting sole artist releases vs. compilation releases.
Those compilations that get broken up tagged/scanned and matched to artist’s albums instead of the group they were already in. To be able to quickly go down the cluster list and pick each one of whatever you’re looking for, and presumably have the path to save to set different at that time, so you can get all the sole artist stuff into one place, all the multiple artist stuff into another place during separate passes when saving from the left.
…and anything that uses artist credits wouldn’t get an indicator, but all the ones that absolutely do, would.
It’s somewhat easy to tell by the release name if it’s a multi-artist, or single artist compilation. By segregating out the stuff that most definitely will not be a typical single artist, single album release out of there from the start.
The target of such a feature is beneficial on the left side, the right side already takes care of that … this just would make moving releases over, loading to an album, less work.
Picard is an excellent tagger. But getting to that point can be a lot of work sometimes, so why not use some interactive fuzzy logic along the way to make that last phase go smoother.