Hi Clemens --

I really appreciate your help. I've made some progress, although I do
find it a bit strange. Basically, as I understand it, I've got
aconnect transferring MIDI controller (20:0) events to /dev/midi02
(24:0), and have csound listening on 24:0.

So, after reading your message, I shrugged and tried this:

    cat /dev/midi02 > /dev/midi02

While this command is running, I can hear my Keystation events in
csound! For that matter, (and more importantly) I can use Rosegarden
to record to MIDI tracks, and play them back via Csound (setting
Rosegarden's output to 24:0).

Anyway, it works, but that "cat" command above is one of the strangest
I've ever typed. Is this the way I'm supposed to get MIDI events to
"go in" one ALSA MIDI port and "come out" the other? It appears that
the tools I'm using don't want to use the MIDI devices in /dev, but
the ALSA port numbers.

Thanks for your patience. Obviously I'm pretty new to this MIDI stuff.

-- psj



On 25/07/06, Clemens Ladisch <[EMAIL PROTECTED]> wrote:
> Paul Jensen wrote:
> > I'm having difficulty using ALSA's virtual MIDI ports to route MIDI
> > events from my M-Audio Radium 61 MIDI controller (USB interface --
> > works fine) to my Csound softsynth.
> >
> > ~$ aseqdump -l
> >  Port    Client name                      Port name
> >   0:0    System                           Timer
> >   0:1    System                           Announce
> >  16:0    ICEnsemble ICE1712 MIDI          ICEnsemble ICE1712 MIDI
> >  16:32   ICEnsemble ICE1712 MIDI          ICEnsemble ICE1712 MIDI
> >  20:0    Keystation                       Keystation MIDI 1
> >  24:0    Virtual Raw MIDI 2-0             VirMIDI 2-0
> >  25:0    Virtual Raw MIDI 2-1             VirMIDI 2-1
> >  26:0    Virtual Raw MIDI 2-2             VirMIDI 2-2
> >  27:0    Virtual Raw MIDI 2-3             VirMIDI 2-3
> >
> > The Keystation works fine -- "aseqdump 20:0" shows appropriate
> > Keystation MIDI events.
> >
> > I can "aconnect 20:0 24:0" fine, and the connection appears to "take"
> > when I "aconnect (-li | -lo)", and I can see the connection in
> > Qjackctl's connection window. However, after making the connection, a
> > "aseqdump -p 24:0" returns no MIDI action at all when I hit the
> > Keystation keyboard.
> >
> > Isn't it the case that incoming MIDI events from 20:0 (the Keystation)
> > should be sent to the virtual 24:0 MIDI device, where I can ask Csound
> > take its MIDI input from?
>
> The Virtual Raw MIDI driver converts between sequencer ports (x:y) and
> the old OSS raw MIDI ports (/dev/midixx).  Any data sent to port 24:0
> can be read from /dev/midi02, and any data sent to /dev/midi02 can be
> read from 24:0.
>
> Your "aseqdump -p 24:0" command would display data sent by Csound (if
> Csound is connected to /dev/midi02).
>
> To see data sent to port 24:0, use a command like
> "hexdump < /dev/midi02".
>
>
> HTH
> Clemens
>

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Alsa-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/alsa-user

Reply via email to