22 May
2003
22 May
'03
7:54 p.m.
Hallo,
Adrian Prantl hat gesagt: // Adrian Prantl wrote:
Hello!
Today I tried to use fluidsynth as a software synthesizer to Rosegarden4.
I followed the tutorial at
http://linux-sound.org/quick-toots/4-sequencers_and_softsynths/quick-toot-m…
.
But when I try something like
Maybe "81:0"?
Now I get serious. Fluidsynth creates a new port, when started like this:
$ fluidsynth -m alsa_seq /usr/lib/awe/sfbank/8mbgmsfx.sf2
You see it here:
$ aconnect -lo
client 64: 'Rawmidi 0 - M Audio Audiophile 24/96 MPU-401' [type=kernel]
0 'M Audio Audiophile 24/96 MPU-401'
[...]
client 128: 'FLUID Synth (10195)' [type=user]
0 'Synth input port (10195)'
Then you can aconnect this port to the one you like:
$ aconnect 64:0 128:0
$ aconnect -lo
client 64: 'Rawmidi 0 - M Audio Audiophile 24/96 MPU-401' [type=kernel]
0 'M Audio Audiophile 24/96 MPU-401'
Connecting To: 128:0
[...]
client 128: 'FLUID Synth (10195)' [type=user]
0 'Synth input port (10195)'
Connected From: 64:0
Now I can play fluid from my keyboard.
ciao
--
Frank Barknecht _ ______footils.org__
fluidsynth -m alsa_seq -a alsa -o
"midi.alsa_seq.device=VirMIDI 2-1"
midi/gs.sf2
fluidsynth reports:
ALSA lib seq.c:181:(snd_seq_open_noupdate)
Unknown SEQ VirMIDI 2-1
So my question: What is the correct name for ALSA sequencer port 81:0?