Hi,

What exactly do the outlets of sysexin output?

I'm trying to debug the sysex learning of my MIDI controller. I've made the controller learn a couple of sysex controls of the format f0 10 06 06 xx yy f7. When I send control changes using any of these to pd, sysexin always prints 247 in the first outlet and 2 in the second. What am I to make of that? Is there a more verbose way to read midi input? Do you have any tips to using pd for things like this?

FWIW, the controller and synth are the Behringer BCR2000 and Oberheim Matrix 6.

here's the thread that i found useful:

http://puredata.hurleur.com/sujet-417-sysex

the main bit was:

"its working here gnu/linux with jack alsamidi.

[midiin] [midiout]

comma separated integer messages.

eg [240, 34, 26, 43, 253, 247(

on windows youll get messages the some midiobjects are not working.
But do your own testing some seems to work anyway."

i think i adapted that and got sysex to control my mks-50

i just got a matrix1000, and don't have any controller for it, so i might have to have a look at the sysex for that too. it should be the same as the matrix 6, i hope.

by the way, when i did sysex with the mks50, it did work to program sounds, but was completely useless for realtime modulation or anything like that. the midi/sysex format is far too slow

looks like a LOT of work though:

http://www.youngmonkey.ca/nose/audio_tech/synth/Oberheim-Matrix1000.html

Thanks! I eventually found the problem — the synth has to be in 'patch edit' mode to accept parameter changes from outside, and both the knob board and now pd are sending working sysex strings. The original question of what [sysexin] is good for does remain, in case anyone has the straight dope on it.

JSynthLib fortunately has an ostensibly complete patch editing support for the Matrix 6 and 1000 so there's no immediately apparent reason to have to do it all over.

Busnoise -

I used the sysexin object to get information from a yamaha DX synth. A request message has to be made first to the synthesizer (finding out what it is in the manual can be a headache but it is possible).

Once you get to this point it's a simple step of creating messages like $23, $124, $79 to get specific numbers out of the string. In this example the numbers represent the values for every parameter in the current preset.