Hi!
You don't know me, but I've had a Nu-Evi for a couple months and I've always thought that, as a monophonic electronic instrument, it is uniquely positioned for supporting microtonal fingerings.
For example, it has 8 easily reachable touch sensors + independent octave control over 7 octaves. This means that it has potentially 256 unique fingerings per octave, for a grand total of 1792 unique fingerings across the entire range of the instrument. Even accounting for enharmonic equivalents, this blows even dedicated microtonal keyboard instruments like the Lumatone out of the water in terms of the number of unique notes that it can reference at any given time.
Combined with the expressive breath, bite, and lip control, it's difficult to match in terms of pure expressiveness.
However, currently, the firmware doesn't support this, and that's okay! This is a fairly fringe use case, and, until recently, the restrictions of there only being 127 unique MIDI notes have made communicating more than 127 unique notes to a tone generator fairly difficult.
Luckily, I am currently working on several MIDI 2.0 projects that could potentially help make this a reality with very little work on the firmware side of things.
For now, if I could even just get regular updates about the current state of the different hardware controllers, I could probably write a translation layer on the receiving side to translate this into microtonal midi data using MIDI 2.0 or MIDI 1.0 MTS. I imagine that the state of the main 8 keys (K1-7 + pinky) + the current octave via 1 or 2 custom Sysex7 messages would likely be enough when combined with the normal MIDI 1.0 note on, note off, and breath control CV to really take the instrument to the next level in terms of microtonality.
I would potentially be willing to help out with such an effort on the firmware side, but my C coding skills could likely use a bit of work, and I do want to make sure that any changes I make are unlikely to damage my Nu-EVI, as I'm not currently in a position where I could easily afford to replace it.
Anyway, I would appreciate any thoughts, questions, or concerns that you have on the matter, and would love to hear back from you soon!
Thank you for your time!
Rahzael
Hi!
You don't know me, but I've had a Nu-Evi for a couple months and I've always thought that, as a monophonic electronic instrument, it is uniquely positioned for supporting microtonal fingerings.
For example, it has 8 easily reachable touch sensors + independent octave control over 7 octaves. This means that it has potentially 256 unique fingerings per octave, for a grand total of 1792 unique fingerings across the entire range of the instrument. Even accounting for enharmonic equivalents, this blows even dedicated microtonal keyboard instruments like the Lumatone out of the water in terms of the number of unique notes that it can reference at any given time.
Combined with the expressive breath, bite, and lip control, it's difficult to match in terms of pure expressiveness.
However, currently, the firmware doesn't support this, and that's okay! This is a fairly fringe use case, and, until recently, the restrictions of there only being 127 unique MIDI notes have made communicating more than 127 unique notes to a tone generator fairly difficult.
Luckily, I am currently working on several MIDI 2.0 projects that could potentially help make this a reality with very little work on the firmware side of things.
For now, if I could even just get regular updates about the current state of the different hardware controllers, I could probably write a translation layer on the receiving side to translate this into microtonal midi data using MIDI 2.0 or MIDI 1.0 MTS. I imagine that the state of the main 8 keys (K1-7 + pinky) + the current octave via 1 or 2 custom Sysex7 messages would likely be enough when combined with the normal MIDI 1.0 note on, note off, and breath control CV to really take the instrument to the next level in terms of microtonality.
I would potentially be willing to help out with such an effort on the firmware side, but my C coding skills could likely use a bit of work, and I do want to make sure that any changes I make are unlikely to damage my Nu-EVI, as I'm not currently in a position where I could easily afford to replace it.
Anyway, I would appreciate any thoughts, questions, or concerns that you have on the matter, and would love to hear back from you soon!
Thank you for your time!
Rahzael