Questions & Answers

S1 doesn't 'pass on' Sysex strings?

+3 votes
79 views
asked May 26 in Studio One 4 by tomslowcat (1,440 points)

Hello,

I have a MIDI controller (Bistream 3X) programmed to send Sysex strings to control a couple vintage pieces of analogue synths. The B3X was added as a external device (tried Keyboard, Instrument and Control Surface), with its usb port as input and a MIDI din port of my MOTU Express 128 as output to my synths.

I know S1 Sysex implementation is very basic but I was hoping it would just pass any Sysex string along without interfering. However this is not the case apparently. Indeed, moving knobs on my B3X doesn't trigger parameter changes on my synths as expected. When bringing up the MIDI monitor it display weird looking Sysex strings:

I know everything is set up properly because if I setup a direct link using MIDI-OX it works and the Sysex are displayed correctly on OX's MIDI monitor:

So it seems that S1 somehow intercepts the Sysex string and messes it up. Is that a bug or am I missing something here? Any help appreciated, thanks.

Thomas

3 Answers

0 votes
answered May 27 by robertgray3 (26,250 points)
There's an old Feature Request involving Sysex you can vote on here, please vote it up and comment in the comments section about your individual situation where you also want it to "record and pass on" Sysex data properly. A lot of the support for that FR comes from wanting to saved send Sysex messages in terms of patches or banks but it's important to note there are more spots where sysex is useful, like yours

https://answers.presonus.com/7444/sysex-implementation-ability-save-and-send-sysex-dumps-song?show=7444#q7444
0 votes
answered May 28 by tomslowcat (1,440 points)
Thanks robertgray3. I'd already voted for this one actually. Though in my case I would call that more a bug than a feature request. And thhere isn't the option to open bug reports is there? Can't see one anywhere.
0 votes
answered May 28 by robertgray3 (26,250 points)
to report a bug send it to Presonus Support through the Presonus Knowledge base, keep it short and simple (the pictures here help) and hopefully they can forward it to the software side
...