Hi Element,
OK, I've just tried the aseqdump idea. There are no unexpected note events.
But there are control change events sent when I change channel on the
keyboard, which of course I am doing during my test. When I change midi
channel from 1 to 2, I see :
Control change 0, controller 1, valu
Hello Mark,
I wouldn't trust the Anjuta project file, it may be outdated. The cmake
build is the recommended method of building FluidSynth currently.
In regards to MIDI events being possibly the source of the problem, what
about running something like aseqdump and connecting your keyboard up to
Hello Jean-Jacques,
OK, I agree completely that this behaviour is strange :). I expected that
the noteon command would be enough show the problem. I was very surprised
when it didn't and I needed to hit a key on the midi keyboard.
But if my midi keyboard was sending on two channels or alsa was
Hi, Mark
Hope thiss should help to localize the issue:
A)Inside Fluidsynth,
1)The 'noteOn command' plays a note using the function API
fluid_synth_noteon(channel,key,velocity).
2) When receiving a MIDI noteOn message, the MIDI driver puts this
message to the input Router and than the Router use
