I'm working on a debian unstable machine, trying to construct valid MIDI tuning sysexes and test them by sending them to fluidsynth.
I've been using the program sysexxer-ng ( https://github.com/linuxmao-org/sysexxer-ng) to send these. Both sysexxer-ng and fluidsynth show up in my qjackctl connections, where I connect the sysexxer output to fluidsynth's input. When I send my sysex, though, fluidsynth doesn't seem to receive it. This is true for both the debian packaged version of fluidsynth and one I built recently from the latest github sources. I inserted midisnoop (from the debian package https://packages.debian.org/sid/midisnoop) in between the sysexxer output and fluidsynth input and confirmed that the sysexxer is indeed sending my data, but fluidsynth doesn't seem to receive it (nothing dumped when invoked with -d, and no tunings set). I built a debug version of fluidsynth and put a breakpoint just inside fluid_midi_router_handle_midi_event, which looks to me like it is where all incoming MIDI events are first handled. My breakpoint was activated sending note on events from a controller keyboard, but sending my sysex did not activate it -- it's truly like what I'm sending is lost in the aether. Am I doing something wrong? There's always the possibility that I'm not, in fact, successfully sending the data, but since I saw it in midisnoop I think that's unlikely. Can anyone give me a hint as to how I can get this to work, or what my next step debugging the issue might be? Any help would be greatly appreciated. Forrest
_______________________________________________ fluid-dev mailing list fluid-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/fluid-dev
