hi miller,
i really appreciate you taking the time to lend me a hand. (un)fortunately i already found the problem, there was a bug in the alsa midi patch. in sys_putmidimess the output port was hard coded to zero, and replacing the 0 with the appropriate port variable did the trick. i've been holding out on posting an update because i also plan on fixing the sys_putmidibyte function in the alsa midi patch if i can. that might take some time, as i'm new to the alsa api and still pretty green with linux in general, but i'm shooting for early july. i'll let you know how it goes.
-steve
-----Original Message----- From: Miller Puckette To: steve.long@camp.org Cc: pd-list@iem.at Sent: 5/29/05 5:31 PM Subject: Re: [PD] notein and noteout operation discrepancy
Hi Steve,
I can't reproduce this (but I only have one MIDI output, just tried to output to channel 17 and got nothing.) I'ts possible to open the same MIDI device twice in Linux, although I don't see how your arguments could really have done that... just as a guess, try outputs 1,3,4,5,6,7,8,9 and see if that helps?
cheers Miller
On Sat, Apr 30, 2005 at 03:54:15PM -0700, steve.long@camp.org wrote:
hello everyone! i'm new to the mailing list and relatively new to pd.
i
just got pd setup on an old computer for use as a dedicated midi processor to sit between my drumset and a rack of synths, and i'm
seeing
some strange behavior:
i have a simple patch consisting of a [notein 49] connected to a [noteout], plus a bang and a number box triggered from the notein that allows me to select different output channels. this allows me to take
a
note from my drum module and route it to an arbitraty synth, or at
least
that's what i thought. what's happening is output channels 1-16 work
as
expected, but 17-32 are sending to port 1 instead of 2, and 33-48 go
to
ports 1 instead of 3, etc. sadness.
i was wondering if anyone has seen this sort of problem before, or if anyone has an idea on how i can remedy it or find a workaround. a
search
of the list archives and pd documentation was futile, so here i am asking for help, please, and thank you!
my system details: i'm running AGNULA's DEMUDI 1.2.1, which comes with PD 0.38.4. there is no sound card installed, but i have an m-audio midisport 8x8 usb midi interface, and i can do simple routing between its ports with aconnect, so i believe it's working properly. i'm launching PD with 'pd -noaudio -rt -audiobuf 1 -midiindev 1,2,3,4,5,6,7,8 -midioutdev 1,2,3,4,5,6,7,8', then i'm manually connecting the 8 'PureData' midi io ports to the 8 'MidiSport 8x8' hardware ports with aconnect.
-steve steve.long@camp.org
PD-list@iem.at mailing list UNSUBSCRIBE and account-management ->
Long, Steve wrote:
hi miller,
i really appreciate you taking the time to lend me a hand. (un)fortunately i already found the problem, there was a bug in the alsa midi patch. in sys_putmidimess the output port was hard coded to zero, and replacing the 0 with the appropriate port variable did the trick. i've been holding out on posting an update because i also plan on fixing the sys_putmidibyte function in the alsa midi patch if i can. that might take some time, as i'm new to the alsa api and still pretty green with linux in general, but i'm shooting for early july. i'll let you know how it goes.
hi
yesterday i ran into the very same problem (that connecting 4 MIDI devices will give me 64 midi-IN channels but only 16 midi-OUT channels) a quick look at the code revealed, that somebody is doing channel &= 0xF; which explains a lot.
before i try to start fixing this code, i wanted to ask whether you have already done so and what the current status of this is.
i am using pd-0.38-4 with the alsamidi-patches, but the problem should be the very same with any MIDI-OUT.
mf,asdr, IOhannes
IOhannes m zmoelnig wrote:
yesterday i ran into the very same problem (that connecting 4 MIDI devices will give me 64 midi-IN channels but only 16 midi-OUT channels) a quick look at the code revealed, that somebody is doing channel &= 0xF; which explains a lot.
actually it explains nothing; it was just a misunderstanding of the code on my side.
before i try to start fixing this code, i wanted to ask whether you have already done so and what the current status of this is.
i am using pd-0.38-4 with the alsamidi-patches, but the problem should be the very same with any MIDI-OUT.
to get multiple midi-outputs work with ALSA, you have to change one line in s_midi_alsa.c in the sys_putmidimess() function: change snd_seq_ev_set_source(&ev,alsa_midioutfd[0]); to snd_seq_ev_set_source(&ev,alsa_midioutfd[portno]);
OR apply the attached patch.
note: of course this only applies if you have alsa-midi enabled (as can be done with the patches at sf.net/projects/pure-data)
mfg.adsr IOhannes