Thanks Michael, This worked!! I've been struggling over this one for a while. Now if only my Midisport wouldn't close down on me when I receive the odd scrambled data from my wireless midi receivers I'd be totally up and running. It seems the windows Midiman firmware is much more robust. Thanks again for the help. Jim
>On Sat, 21 Sep 2002 12:42:42 -0400 >Jim Ruxton <[EMAIL PROTECTED]> wrote: > > > >>Still can't seem to be able to use both ports with this particular >>program , Pd. I'll try another midi program and see if that works. >> >> > >I had, again, the same problem (it turns out now, because i have only 1 midi device >so I didn't need know...). pd uses oss midi, it's not yet alsa compatible. so, in >my setup (and it looks like yours, too) I have /dev/midi02 which is the same as >/proc/asound/dev/midiC2D0. However, my /dev/midi03 did not act as >/proc/asound/dev/midiC2D1 which, logocally, it should. So I did ln -s -f >/proc/asound/dev/midiC2D1 /dev/midi03 and now I can use both MIDI ports on the >midisport. I guess this is not a nice hack but it works for me :) > >Now, concerning pd. >[guess this should go on the pd-list :)] > >in pd you have to explicitly specify the midi ports you use. SO with the above setup >I run 'pd -mididev 3 4' . This way, when sending out midi messages channels 1-16 >send out on port 1, channels 17-32 send on port 2. > >The same with the objects that receive midi. > >HTH. > > > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Alsa-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-user
