> However, I am not sure if SysEx events are (correctly) implemented for all midi drivers. alsa_seq should work though. Which driver are you using?
This turned out to be the key. I had been using JACK MIDI (with a2jmidid for Fluidsynth, and native drivers for sysexxer-ng). When I changed my qjackctl settings to use the alsa seq MIDI drivers, my sysex was recognized. Thanks for help! On Mon, Feb 4, 2019 at 1:12 PM Tom M. <tom.m...@googlemail.com> wrote: > A few thoughts from my side: > > fluid_midi_router_handle_midi_event() is the correct place to look for > SysEx events. Specifically the "case MIDI_SYSEX:" line should trigger a > breakpoint. Alternatively you can break in fluid_synth_sysex(). > > However, I am not sure if SysEx events are (correctly) implemented for all > midi drivers. alsa_seq should work though. Which driver are you using? > > Make sure your SysEx events use the correct device ID, otherwise > fluidsynth will ignore it in fluid_synth_sysex(). Either use 0x7F for all > devices or set the device ID with the "synth.device-id" setting. > > > Tom > > > > > _______________________________________________ > fluid-dev mailing list > fluid-dev@nongnu.org > https://lists.nongnu.org/mailman/listinfo/fluid-dev >
_______________________________________________ fluid-dev mailing list fluid-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/fluid-dev
