18 Oct
2003
18 Oct
'03
11:26 a.m.
Greetings:
I've been working with Tim Thompson's KeyKit, trying to get it to send
its output to a softsynth. I can set a variable for KeyKit that will
select the ALSA rawmidi device with this syntax :
export ALSA_RAWMIDI_DEVICE=hw:1,0
where hw:1,0 refers to my card1 (the ALSA virmidi module) and its first
device (0). Now when I start KK (and set the Port Enabler to ALSA) I can
route its output to whatever connections are available via aconnect (or
the kaconnect GUI).
I just wanted to say "Thanks!" to the ALSA developers for the virmidi
module. I've used it with MIDI sequencers running under emulation
systems such as DOSemu and Xsteem, I've used it for the TK707 virtual
drum machine, and now I'm using it with KeyKit. The combination of
TiMidity-as-softsynth (with the Fluid soundfont) and the virmidi module
is a very powerful and flexible system for me, and I just wanted to pass
on a note of appreciation for the ALSA team's work.
Okay, that's all. We now return to our regularly scheduled programming...
Best regards,
== dp
18 Oct
18 Oct
12:02 p.m.
Hallo,
Dave Phillips hat gesagt: // Dave Phillips wrote:
I've been working with Tim Thompson's KeyKit,
trying to get it to send
its output to a softsynth. I can set a variable for KeyKit that will
select the ALSA rawmidi device with this syntax :
export ALSA_RAWMIDI_DEVICE=hw:1,0
where hw:1,0 refers to my card1 (the ALSA virmidi module) and its first
device (0). Now when I start KK (and set the Port Enabler to ALSA) I can
route its output to whatever connections are available via aconnect (or
the kaconnect GUI).
Cool. But I find it a bit strange, that Keyit uses the PCM definition
for midi access. Well, but virmidi card hasn't a PCM so who cares. ;)
ciao
--
Frank Barknecht _ ______footils.org__
20 Oct
20 Oct
7:59 a.m.
Frank Barknecht wrote:
Dave Phillips hat gesagt: // Dave Phillips wrote:
This isn't a PCM definition, it's a RawMIDI definition (which happens
to have the same name). All ALSA devices implemented in the kernel are
accessed by a plugin named "hw". See /usr/share/alsa/conf/alsa.conf
for the various definitions (pcm, ctl, rawmidi, seq, hwdep, timer).
It's possible to give some rawmidi port its own name, just like pcms:
rawmidi.my_virtual {
type hw
card 1
device 0
}
then you could use my_virtual instead of hw:1,0.
Another useful plugin (the only other currently available
rawmidi plugin) is the virtual rawmidi device, which is implemented in
user space and doesn't need the snd-virmidi kernel driver.
If you use "virtual" instead of "hw:1,0", each application using this
will create a virtual sequencer port on the fly. (This may not be what
you want, because each application instance will create a seperate
virtual device, and the port exists only as long as the application is
running).
HTH
Clemens
export ALSA_RAWMIDI_DEVICE=hw:1,0
Cool. But I find it a bit strange, that Keyit uses the PCM definition
for midi access.
8:17 a.m.
Hallo,
Clemens Ladisch hat gesagt: // Clemens Ladisch wrote:
Frank Barknecht wrote:
Oh, cool, I didn't know that (obviously...) ^_^
Thanks for explaining.
ciao
--
Frank Barknecht _ ______footils.org__
Dave Phillips hat gesagt: // Dave Phillips
wrote:
This isn't a PCM definition, it's a RawMIDI definition (which happens
to have the same name). All ALSA devices implemented in the kernel are
accessed by a plugin named "hw". See /usr/share/alsa/conf/alsa.conf
for the various definitions (pcm, ctl, rawmidi, seq, hwdep, timer).
It's possible to give some rawmidi port its own name, just like pcms:
rawmidi.my_virtual {
type hw
card 1
device 0
}
then you could use my_virtual instead of hw:1,0. export ALSA_RAWMIDI_DEVICE=hw:1,0
Cool. But I find it a bit strange, that Keyit uses the PCM definition
for midi access.
7707
days inactive
7709
days old
linux-audio-user@lists.linuxaudio.org
3 comments
3 participants
participants (3)
-
Clemens Ladisch -
Dave Phillips -
Frank Barknecht