i guess those problem are overcome switching to the ALSA MIDI programming interface. what system does pd uses to send midi (with midiout)? does it uses a rawmidi device? (http://www.alsa-project.org/alsa-doc/alsa-lib/rawmidi.html) does it uses the sequencer interface? (http://www.alsa-project.org/alsa-doc/alsa-lib/seq.html)
time ago, i coded a small app (a multi-function (midi)message translator) and the only way to send sysex is to use specific sysex functions. here is a piece of code from this app (that sends a system exclusive message):
case Item::T_SYSEX: snd_seq_ev_clear(ev); snd_seq_ev_set_sysex(ev, out.sys_n->length(), out.sys_n->render(out.ch,out.d1,out.d2)); snd_seq_ev_set_subs(ev); snd_seq_ev_set_direct(ev); snd_seq_ev_set_source(ev, out_port[0]); break;
so, it is possible that to send system exclusive messages, midiout should parse its input (mean: check for its input, when a sequence of bytes starts with 0xf0 and ends with 0xf7)
you can find the full source code of this app here: http://xaero.ath.cx/cms
it is called mTransformer
cheers federico
Miller Puckette ha scritto:
Something is apparently wrong wit sysex output... I don't know what!
cheers Miller
On Thu, Oct 13, 2005 at 11:32:26PM +0200, federico wrote:
i noticed today that my patches based on [midiout] object, actually
don't work anymore.
does jack (or alsa) not allow sysex data to pass thru? (i connect pure_data_0 to my UM1SX_midi_out)
or something has changed in new release?
btw, here are the patches: http://xaero.ath.cx/cms/34.html
some time ago they worked ;) note that it is not a midi problem, notes came out of my midi box, but not sysex sent with midiout
some infos:
$ uname -r 2.6.12-gentoo-r10
$ pd -version Pd version 0.39-0 compiled 00:48:58 Sep 4 2005
$ cat /proc/asound/version Advanced Linux Sound Architecture Driver Version 1.0.9b. Compiled on Sep 25 2005 for kernel 2.6.12-gentoo-r10.
$ jackd --version jackd version 0.99.0 tmpdir /var/run/jack protocol 13
PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev