Hi, I've done a little more testing. I booted up into windows xp 

to see how JSynthLib behaves, which, from the looks of it, is the

same as on Linux. In both cases I startup the program, open the 

midi monitor window, and I can get a patch from the synth and load

it into the program. The midi monitor window seems to reflect the

messages coming and going, it looks like it's working.

JSynthLib sends six bytes, f0 10 06 0a 00 f7, (not sure what this is)

then a program change which is reflected on the synth, then 7 bytes,

f0 10 06 04 01 00 f7, which must be the request to send patch, 

then the program receives 275 bytes, f0....f7.

I can paste the sound into the library and open the edit window now.

If I move controls in the JSynthLib editing window, the messages appear

in the midi monitor, but the the synth sound does not change, nor

does the synth show any signs of changes on its blue LED display.

If send a note on from the JSynthLib, the note does play, so the 

midi connection is working. Also, midi system exclusive is "ON"

in the Matrix 6 module. The synth is running software version 2.13.

I checked the program outputs byte by byte with the young monkey

webpage (description of M6 sysex implementation) and everything

looks to be as expected. I can't explain why MidiQuest on Windows

works (partially) but JSynthLib on windows and on linux does not 

work... Does anyone out there have their Matrix 6 working with 

the JSynthLib editor

thx.

JC.