For interactive use, find keyswitches with the given attributes.

Write matrices to a file for visual reference.

Transform elements but retain the matrix's shape.

Add various note calls, depending on the attributes that the patch understands.

If +harm+nat (and optionally a string) attributes are present, try to play this pitch as a natural harmonic. That means replacing the pitch and reapplying the default note call.

Order attributes by priority. This should correspond to specificity, or to perceptual importance, as documented in Patch.AttributeMap.

Since the VSL matrix is only 12x12, a row of articulations greater than that overflows to the next row. Given that I'm definitely going to overflow 12 rows, I wind up overflowing to the next matrix, and when counting tha AB switch, each articulation has 3 or 4 keyswitches.

I could probably cram most instruments into 144 cells and only require 2-3 keyswitches, but it would be hard to read and easy to mess up, wouldn't let me disable and enable cells by row, and with custom patches I'll probably wind up with more than 144 anyway.

Remove attrs which can be assumed as a default. The idea is to make it easier to address an articulation while still remaining non-ambiguous.

Attrs are removed in order unless removal would create a conflict with another articulation. The result is that the attrs early in the strip list are removed first, so if you have both VslInst.med and Attrs.short, VslInst.med will become the default, while Attrs.short retains its attribute.

Strip the given attr, but only if it wouldn't cause clashes.