6 Strings. 6 different algorithms? and MPE channeling.

[Susorl]

In MPE, each note is assigned its own MIDI Channel so that those messages can be applied to each note individually. That is the main concept that we need to stick with, I think.

That means, that we can assign some MIDI CC messages to the individual Actions/Notes that are played. It's needed to define one for Pitch, another fo r Envelope , and Gate?.

I like the continuous channel assignment concept of MPE. It works very well with the idea of One Action-One Event-One Channel-One Set of Metadat.

From other side, we know about the Time issue with Frequency detection with Bass Notes, in the case of Guitar we have E2 (82 Hertz) for the 6th string and E4 (330 Hz) for the 1st String.

The Algorithm works in real Time, and it's needed to make a decision when to create Note On Messages (and avoid Ghosts).
Of course, the result will be different in the case of E2 and E4, and that is my question:

It would be smart to make independent algorithms depending on the Tuning?

The thing is that, in order to be sure that the Note-Pitch is a real Action, it's needed more Time after OnSet and Pitch Detect.

Joel claims that in case of E4 we can have a result in 3 ms, and in case of E2 12 ms I guess, but that it's too early for a MIDI message I would say. What do you think, Joel, about these timings? Which Time we need to add in every case?

Because , the precision of all the system has a strong relation with that, no?

[Susorl]

This is a some information related with MPE, (but I think that MIDI 2.0 offers great opportunities in a broader sense):

MPE Summary

• MPE uses the MIDI standard.
• All the messages from an MPE controller are regular pitch bend, note, aftertouch, and Control Change (CC) messages.
• Wherever possible, every sounding note is assigned its own MIDI Channel for the lifetime of that note.
• Channel-wide expression messages can be applied to each note individually.
• Channel 1 is reserved for global parameters: parameters that will affect all notes.
• This leaves 15 channels available.
• That means that you could play 15 notes at once, all with their own string of data.
• By default, Pitch Bend is set to of ±48 semitones for per-note bend and ±2 semitones for Master bend.
• Either range may be changed to a number of semitones between 0 and ±96 using RPN 0.
• Aftertouch is sent using the Channel Pressure message.
• To preserve compatibility with existing MIDI devices, Polyphonic Key Pressure may be used with notes on the Master Channel, but not on other Channels.
• A third dimension of per-note control may be expressed using MIDI CC #74.
• A Registered Parameter Number (RPN) is used to set the range of Channels over which notes are sent and received.
• The MIDI Channel space can be divided into sub-spaces called Zones, so that multi-timbral playing is still possible using only one MIDI cable.
• Each Zone has a dedicated extra Channel, called the Master Channel, which conveys information common to all notes in that Zone, including pedal data and overall Pitch Bend.

Channel rotation

The clever secret is in channel rotation. For example, when you play a chord, every new note with its unique bend, timbre, pressure, and (eventual) release is sent on its own MIDI channel. So instead of pitch bend affecting all notes, MPE assigns a unique pitch bend, timbre, and pressure value to each note.

[djowel]

@Susorl I have no comment for now, but I'll leave it here and get back to this as soon as I know more.