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
There is an ongoing MIDI 2.0 implementation in FluidsynthMidiReceiver. At this state, it can successfully switches to MIDI 2.0 protocol if it received MIDI-CI "Set New Protocol" message (ignoring destination specification etc.), parses UMPs and invokes fluidsynth functions.
It stops there because fluidsynth itself does not support MIDI 2.0 yet; its functions API is changed to accept 32-bit values etc., but the internal processing, including argument value range check, is still based on 7-bit. It needs the actual implementation.
The text was updated successfully, but these errors were encountered:
noteon2: there is room for enhancing MIDI 2 note on feature (16-bit velocity, pitch 7.9 etc.). No room for SF2 generator per velocity (fixed to 0..127).
cc: it seemed simple, but not really. There are many relevant public functions that return 7-bit values, and especially when they are tied to internals such as omni mode, and modulators that are tied to SF2 format 2.0, things get quite complicated. It is probably better to leave it 7-bit only.
There is an ongoing MIDI 2.0 implementation in FluidsynthMidiReceiver. At this state, it can successfully switches to MIDI 2.0 protocol if it received MIDI-CI "Set New Protocol" message (ignoring destination specification etc.), parses UMPs and invokes fluidsynth functions.
It stops there because fluidsynth itself does not support MIDI 2.0 yet; its functions API is changed to accept 32-bit values etc., but the internal processing, including argument value range check, is still based on 7-bit. It needs the actual implementation.
The text was updated successfully, but these errors were encountered: