Hi, q,
q wrote:(If I understand correctly Encore ignores the note's MIDI channel property . . .
I'm not sure I know what you mean. Do you mean that in recording an incoming MIDI stream, or reading a MIDI file, Encore does not keep track of (that is, record as a property of the stored notes) the MIDI channel of the note messages/events?
I believe that is so. We see no evidence of a MIDI channel being stored as a property of a note, regardless of how it arrived.
and goes entirely by the track/staff MIDI channel.
Until Encore emits a MIDI stream in real-time play, or emits a MIDI file, there are no MIDI channels involved.
The MIDI channel for a note in a MIDI file, or a note in a MIDI stream for real-time play, is of course based on the staff (and If we have chosen to make separate channel assignments for voices, on the the voice).
There is no concept of a track "inside" Encore, either. When a MIDI file is read in, Encore basically takes the notes from each track (a track is really just an "administrative container" for notes and related events) and directs them to an arbitrary staff. (I am ignoring for the moment the splitting of a track by pitch.) Once that has happened, the "track" origin of a note is lost.
When Encore emits a MIDI file, it places all the notes (and related events) from a staff into a single track. The channel tags are determined as mentioned above.
There is no concept of "track" in a MIDI stream.
I'm sure that's probably what you meant, but I just wanted to paint out the details for whatever value that might have.
Best regards,
Doug