29 Dec
2003
29 Dec
'03
3:27 a.m.
1. Are alsa drivers multi-client? (Two applications can read/write
simultaneously to the in or out--i.e. a patch controller and a sequencer
doing notes).
2. Can dummy MIDI devices be installed (virmidi?) to be used for pipelining
midi-out from one program to midi-in to another or for overcoming
single-client problems (Windows examples MidiYoke, MidiMatrix, Hubi's).
3. Seeing as wine sessions successfully enumerate the MIDI devices and
actually played to one! but no native program such as Rosegarden has--KDE has
a MIDI-mapper dialog similar to windows. Must they be set up there from /dev/
mid0 .... references?
4. Jack has been recommended. What precisely is this and how does this work?
5. Can the recommended Ardour/Jack rpm for Madrake be used on Debian?
29 Dec
29 Dec
7:06 a.m.
On Mon, Dec 29, 2003 at 09:24:38 +0100, David Baron wrote:
1. Are alsa drivers multi-client? (Two applications
can read/write
simultaneously to the in or out--i.e. a patch controller and a sequencer
doing notes).
Some are, some aren't - it depends on the hardware, but theres a system
called dmix than can be used to share i/os between apps.
2. Can dummy MIDI devices be installed (virmidi?) to
be used for pipelining
midi-out from one program to midi-in to another or for overcoming
single-client problems (Windows examples MidiYoke, MidiMatrix, Hubi's).
You dont need that - the alsa-sequencer system can route midi between
apps. The apps with inputs should appear as possible MIDI outputs in the
app, but if not you can use a patchbay like qjackctl to make alsa-sequencer
connections.
4. Jack has been recommended. What precisely is this
and how does this work?
It allows routing audio between applications, synchronisation and
transport control. Its pretty much essential.
5. Can the recommended Ardour/Jack rpm for Madrake be
used on Debian?
Probably not, but check out demudi: http://demudi.org/
- Steve
7:51 a.m.
Hallo,
Steve Harris hat gesagt: // Steve Harris wrote:
This works only for ALSA-sequencer-aware applications. Applications,
that use rawmidi devices like /dev/midiXX need a workaround to be able
to talk to the sequencer system and that workaround is the snd-virmidi
module. You'll need to use something like this in the modules
configuration:
alias snd-card-2 snd-virmidi midi_devs=8 index=3 id="virmidi01"
This will create a lot of rawmidi devices:
$ ls /dev/snd/midiC2D*
/dev/snd/midiC2D0 /dev/snd/midiC2D2 /dev/snd/midiC2D4 /dev/snd/midiC2D6
/dev/snd/midiC2D1 /dev/snd/midiC2D3 /dev/snd/midiC2D5 /dev/snd/midiC2D7
and all of these now are also part of the sequencer system so they can
be routed with aconnect or the newer qjackctl's ALSA connection GUI:
$ aconnect -i
...
client 80: 'Virtual Raw MIDI 2-0' [type=kernel]
0 'VirMIDI 2-0 '
client 81: 'Virtual Raw MIDI 2-1' [type=kernel]
0 'VirMIDI 2-1
...
Debian unstable/experimental has Ardour packages: "apt-get install
ardour-gtk" will install Jack as well.
ciao
--
Frank Barknecht _ ______footils.org__
On Mon, Dec 29, 2003 at 09:24:38 +0100, David Baron
wrote:
Yes, this is for audio data, but there's no "dmix" for midi devices.
Of course many applications can use ALSA's sequencer device at the
same time, that's what it's designed for. But you might run into
problems when several apps try to open the same /dev/midiXX devices. I
don't know if this would work, I guess not, but there's a solution.
See below.
1. Are alsa drivers multi-client? (Two
applications can read/write
simultaneously to the in or out--i.e. a patch controller and a sequencer
doing notes).
Some are, some aren't - it depends on the hardware, but theres a system
called dmix than can be used to share i/os between apps. 2. Can dummy
MIDI devices be installed (virmidi?) to be used for pipelining
midi-out from one program to midi-in to another or for overcoming
single-client problems (Windows examples MidiYoke, MidiMatrix, Hubi's).
You dont need that - the alsa-sequencer system can route midi between
apps. The apps with inputs should appear as possible MIDI outputs in the
app, but if not you can use a patchbay like qjackctl to make alsa-sequencer
connections. 5. Can the
recommended Ardour/Jack rpm for Madrake be used on Debian?
Probably not, but check out demudi: http://demudi.org/ 
10:47 a.m.
Hi, first off, you'll be able to find answers to all of these questions
by visiting their respective Webpages.
Yes. There are dummy devices which can be defined in ALSA, as well as
some third-party projects which do a similar thing. Finally, perhaps the
best option is aconnect (please someone correct me if I am wrong here)
which enables you to route MIDI data from any port to any or multiple
apps.
-----Original Message-----
From: linux-audio-user-bounces(a)music.columbia.edu [mailto:linux-audio-
user-bounces(a)music.columbia.edu] On Behalf Of David Baron
Sent: Monday, December 29, 2003 3:25 AM
To: Linux Audio Users
Subject: [linux-audio-user] Some questions
1. Are alsa drivers multi-client? (Two applications can read/write
simultaneously to the in or out--i.e. a patch controller and a
sequencer
doing notes).
This depends on audio hardware not on drivers. However, from your
question I am assuming you are referring to MIDI, not audio. In that
case you can have multi-client setting as long as you have a MIDI
interface with multiple inputs/outputs.
2. Can dummy MIDI devices be installed (virmidi?) to
be used for
pipelining
midi-out from one program to midi-in to another or for overcoming
single-client problems (Windows examples MidiYoke, MidiMatrix,
Hubi's).
3. Seeing as wine sessions successfully enumerate the
MIDI devices and
actually played to one! but no native program such as Rosegarden
has--KDE
has
a MIDI-mapper dialog similar to windows. Must they be set up there
from
/dev/
mid0 .... references?
Not sure what you are referring to here. Most apps will offer you the
option of connecting to one of the MIDI ports in the case you happen to
have multiple MIDI devices. If you happen to have only one device, then
there is no point of having to select a preferred device. It is
important to note that this is usually on the app-level, rather than
OS-level.
4. Jack has been recommended. What precisely is this and how does this
work?
This is a software-based REWIRE equivalent, but on steroids. Audio can
be shared and routed between multiple apps, it is very low latency, and
it is sample accurate.
5. Can the recommended Ardour/Jack rpm for Madrake be used on Debian?
No. There are most likely Debian-packaged versions of the aforementioned
software, so try looking into the apt-get.
In addition to this I would strongly suggest you read more about these
features by visiting projects' respective Webpages.
Hope this helps!
Ivica Ico Bukvic, composer & multimedia sculptor
http://meowing.ccm.uc.edu/~ico
7701
days inactive
7701
days old
linux-audio-user@lists.linuxaudio.org
3 comments
4 participants
participants (4)
-
David Baron -
Frank Barknecht -
Ivica Bukvic -
Steve Harris