Why do we even need a part name matrix?

Large ensemble scores have lots of parts. When you are working across multiple scores, sometimes the parts arent named exactly the same thing. Take for example these two scores:

Score 1

Flute Clarinet Trumpet Piano Bass

Score 2

Flute Clarinet Trumpet Keyboard Bass

Notice the difference? The Piano part is labeled as keyboard in the second score. We know that the same musician will be playing both of these parts in either song, so it makes sense to consider them the same “Part Name”.

In this scenario, we can use the part name matrix to map these part names together. This means that for all versions (including future versions), Divisi will map these parts to use the same “name”, and when generating part books, they will be considered the same part and included in the same part book.

Using the Part Name Matrix

While it can look a little daunting, I promise you it makes sense!

On the Y axis we have each score (called an Arranement in Divisi), and on the X axis we have every “Part Name” in the ensemble. The table cells have a green dot if that part name has a “part” in the latest version of that arrangement. This makes it easy to see which “Part names” are potentially mislabeled in certain arranements. (Ideally, you would have a table of all green cells). To “merge part names” (ie, resolve duplicates), simply drag one column onto another to combine them. At this point, you can also rename the part name (the name of the part book) if you choose.