On Apr 01 21:03:43, s...@spacehopper.org wrote: > On 2013/04/01 19:16, Jan Stary wrote: > > On this fresh install of current/amd64, > > using the new audio/fluidsynth 1.1.6 (thank you sthen), > > I can only use it with sndiod _not_ running. > > > > When sndiod runs, my MIDI keyboard still works fine, > > as tested with 'aucat -Mq rmidi/0 -o -' (suggested by the FAQ), > > but fluidsynth never seems to get any of the MIDI messages. > > > > The keyboard is a CME UF-6 connected by an M-Audio USB-to-MIDI, > > reports itself as > > > > umidi0 at uhub2 port 2 configuration 1 interface 1 "M-Audio USB Uno MIDI > > Interface" rev 1.00/1.25 addr 2 > > umidi0: (genuine USB-MIDI) > > umidi0: out=1, in=1 > > midi0 at umidi0: <USB MIDI I/F> > > ugen0 at uhub2 port 2 configuration 1 "M-Audio USB Uno MIDI Interface" > > rev 1.00/1.25 addr 2 > > > > and works OK in many other situations. > > > > If I shut sndiod down, fluidsynth works OK. > > Can some shed some light on why is that? > > > > Can this a problem of fluidsynth's sndio backend? > > Hmm... does this work with 1.0.9 with -current sndio?
No. I am having the same problem with 1.0.9 on current/amd64 and current/i386 > Unfortunately I > have no usb-to-midi here so I can't test with an external controller, > only from programs on the machine itself generating the midi messages > (midiplay, scummvm, etc) which are all working fine. Yes, I can also do 'noteon' from within fluidsynth and it plays the note fine. THe only problem seems to be to actually get the midi messages to fluidsynth ...
