You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Adding another export MidiOutMTS which would give an alternative to multichannel PB using single-note real-time Midi Tuning Standard messages over sysex (opt in popup for browser users): The logic of retuning in Midi 2.0 is almost identical so the code will be re-useable when sw adds Midi 2.0 compatibility (roadmap 4.0???) Concept is to use the note numbers as slots in which the "actual" neareast MIDInote and needed PB (up to 14 bit resolution across 1 semitone upward) are stored. Then one can simply cycle through the MIDI note slots and recover info from them for per-note stuff (NoteOff Velocity, Poly AT etc.)
The text was updated successfully, but these errors were encountered:
a similar implementation in hexatone.plainsound.org works well, unless the software does not respond to all MIDI notes (i.e. Pianoteq). They are apparently addressing this issue, though.
Adding another export MidiOutMTS which would give an alternative to multichannel PB using single-note real-time Midi Tuning Standard messages over sysex (opt in popup for browser users): The logic of retuning in Midi 2.0 is almost identical so the code will be re-useable when sw adds Midi 2.0 compatibility (roadmap 4.0???) Concept is to use the note numbers as slots in which the "actual" neareast MIDInote and needed PB (up to 14 bit resolution across 1 semitone upward) are stored. Then one can simply cycle through the MIDI note slots and recover info from them for per-note stuff (NoteOff Velocity, Poly AT etc.)
The text was updated successfully, but these errors were encountered: