Hi Everyone,

I'm attempting to make a TouchOSC/iPad control surface for Adobe Audition in OSX. The basics are running well: Audition accepts only Mackie Control, so I'm routing signals into audition via midi using the Mackie-specific midi notes/channels to control basic transport controls and faders. I then made a 'bridge' with PD, to translate and communicate messages back to Audition via OSC for visual feedback on the iPad.

However, I've hit a brick wall trying to grab the 'track names' from Audition's Mackie Control sysex feed. I've reversed-engineered the messages and made a patch to pick out the relevant bits of data and translate them into words, but the sysex stream that PD is receiving seems to be truncated, and not received in full... It cuts out mid-flow (eg. "240 0 0 102 20 18 77 32 48 48 52 32" - without the terminating 247) and seems to completely omit a good few sysex messages entirely. To test, I've just been using the standard [sysexin] - [add2 $1( - [ (

FWIW, I know Audition's spitting all the data out, as MIDI Monitor, and other iPad apps (AC-7 core) receive the track names in full, but am confused about what's going on in PD.

Any ideas, anyone?

Cheers in advance.

On Windows, I haven't been able to receive sysex at all.

I've had success with everything else I've tried, though, including notes, CCs, PCs, other realtime messages such as CLOCK, START, STOP, etc. I'm able to send sysex perfectly as well, just not receive it.

Researching this a while back, I ran across a couple old threads that state sysex gets truncated at ~100 bytes or so for any users. I don't recall a solution.

I'd be interested in learning more about the standard you referenced:
[sysexin] - [add2 $1( - [ (

if you could point me to an example or writeup, I'd appreciate it. Maybe I've been "listening" incorrectly myself...

Thanks for the reply.

Sounds like PD may not be the way forward with this.

In short bursts, sysex is definitely working for me on OSX - one or two 14 byte messages work fine. It's just when big chunks of data are chucked out of Audition I'm having problems - the cutoff point seems to be around 300 bytes, though it's bizarrely not fixed to a certain number.

Thanks again.

Sure - to look and see what sysex data PD's receiving I've literally just made a very simple patch:

[sysexin]
!
[add2 $1 (
!
[ (

and triggered something in audition that'll make it spew out its data (eg. opening a session file, or changing a channel name), which just throws all of the sysex data into a message box. I've connected PD to Audition and vice versa with an IAC driver.

The actual bridge patch I was making is a little more complex, but basically picks out the start of each sysex message by selecting 240, before translating each of the relevant numbers in the following stream into its corresponding letter in the form of a list; and finally, sending this list out when a 247 is received.

Thanks. Basically use the message box like a buffer.

ive read somewhere else that you have to seperate the sysex words by 1 ms before sending them out ... im on linux so it should work all right. does somebody have a working patch for sysex out messages?

Basically you need to build a message & comma separate the elements. The patch at the end of this thread works perfectly for me. You pass it a list of numbers & it will properly format a message box & send it.
http://puredata.hurleur.com/message-28890.html#p28890

Some have reported you need to add a 1ms delay, but I haven't seen that. But it should be easy to enhance that patch to do so.

Still no solution for *receiving* sysex on Windows that I know of...