Matt,
I know I'm not going to win the battle on how sorting applies globally to a view scheme in MC13 whereas each field view in a scheme in MC12 has its own.
But, please consider how semi-colon delimited fields are treated by MC13 sorting algorithm. The effect, on albums, is that they are treated much like Multiple Artist albums in Views sorted by Artist Album (auto): they are listed first, and essentially out of place of the intended sorting.
What happens is that the whole point of using such a tag is lost when sorting with the semi-colon delimited field in another view.
For example, if I create a Custom Artist field (in order to keep all files under the correct tile and not tucked away in Multiple Artist tiles), and I want to then view Albums but sort according to this Custom Artist field so I can see album tiles sorted by artist, MC puts any albums which have the semi-colon delimited field propagated with more than when entry first.
As opposed to placing the the album in the view according to the first letter, which makes sense, we end up with a field which is essentially not scalable i.e. it is only useful for one type of sorting.
I feel this is one of the minor drawbacks, that 13 so globally applies sorting, the user's only recourse is to create multiple new and unique view schemes to accommodate their various sorting needs.
Please consider this change if is reasonable. I'm not the only using this type of field in a custom tag, and I hope others can comment on this.
DC