Alexandre Ratchov wrote: > On Tue, Apr 02, 2013 at 08:47:34AM +0200, Jan Stary wrote: >> On Apr 02 00:17:16, a...@caoua.org wrote: >> > On Mon, Apr 01, 2013 at 07:16:20PM +0200, 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? >> > >> > Maybe fluidsynth uses the "default" MIDI port; if sndiod is running >> > this corresponds to "midithru/0", else to "rmidi/0". >> > >> > Does it work if you force fluidsynth to use rmidi/0 ? >> >> Is there a way to do that? >> >> There is midi.portname in fluidsynth's settings, >> but setting it to whatever doesn't seem to have any effect. >>
When I reroute audio in fluidsynth I'm using 'fluidsynth -o audio.sndio.device=...', so for MIDI 'fluidsynth -o midi.sndio.device=...' might work. > > don't have a box to test it right now, but iirc the -p option used > to work, you could also try: > > export MIDIDEVICE=rmidi/0 > > in case fluidsynth uses the "default" device. > > -- Alexandre
