This bug was introduced when the track.midiChannel approach was changed:
Track.midiChannel values are now always in increasing order from top to bottom of a system, with the top voice having midiChannel 0. The only exception to this rule is that midiChannel 9 (the percussion channel) can be at any position on the system.
The Track order can no longer be changed using the AssistantComposer's main dialog.
In scores having InputVoices, TrkRefs now point at Trks using their index (from top to bottom of the system).
This is all correct, except that attempting to write two voices on a staff (done using the Assistant Composer's main dialog) now throws an exception deep in the code.
I once spent a day attempting to fix this bug, but have now decided to put it on one side for the moment.
notator
commented
6 years ago
This bug was introduced when the track.midiChannel approach was changed: Track.midiChannel values are now always in increasing order from top to bottom of a system, with the top voice having midiChannel 0. The only exception to this rule is that midiChannel 9 (the percussion channel) can be at any position on the system. The Track order can no longer be changed using the AssistantComposer's main dialog. In scores having InputVoices, TrkRefs now point at Trks using their index (from top to bottom of the system). This is all correct, except that attempting to write two voices on a staff (done using the Assistant Composer's main dialog) now throws an exception deep in the code. I once spent a day attempting to fix this bug, but have now decided to put it on one side for the moment.