SY-1000 Controller Rackspace - Scriptlet Error/Crash

Scripting with Gig Performer
1

Hi GP people.

I’m currently trialling GP5 with serious consideration to adopting it as the backbone of my guitar rig.

This SY-1000 Controller rackspace really caught my attention. If I could use it to control the BOSS SY-1000 via a number of different MIDI controllers, it could greatly simplify my daily workings. And it does work pretty well, based on my testing today.

But, I found one small problem and, unfortunately, the script author is no longer supporting this scriptlet as he’s moved on from the SY. So I’m seeking assistance here.

The TUNER ON/OFF SysEx parameter (triggered at the GP side or the SY side) typically results in a scriptlet error which breaks SysEx communication. In a few cases, it completely crashed GP5.

It may have something to do with bidirectional SysEx. When testing/observing the SY-1000 port in SysexLibrarian (macOS) I see a thick stream of data begin when the BOSS Tone Studio editor is connected and the SY-1000 enters TUNER ON mode. The stream stops when the tuner is turned off. FWIW, it seems to be the only parameter listed that has an address starting with “7F” while all other parameters follow a different sequence.

I managed to capture the following message in the GPScript debug window and I have bolded the bytes that I believe relate to the problem. I think the tuner should only have OFF (00) or ON (01) states. Also, the 3rd byte has my attention but more on that later:

“F0 41 00 00 00 00 69 12 7F 00 00 02 02 7D F7 Incoming Sysex
Address=7F000002 DataBytes=1 Value=2
SY-1000 SYSEX Scriplet (Script Entity: Scriplet) - owned by rackspace: SY-1000 Connector - GPScript System Function Exception: Parameter item offset range error
No source information available - check GSPScript options”

So after turning on all the scripting options and reloading the rackspace I also got a message in debug mode that indicated a problem around line 6116 of the scriptlet. It is mammoth in size as the SY-1000 has over 3000 controllable parameters!

RE: the 3rd byte – In the past, I have programmed a FAMC Liquid Foot MIDI controller to turn on/off the SY-1000 tuner via SysEx so I’m slightly confused why the 3rd byte is 00 and not 10. This controller didn’t allow bidirectional sync though. The commands were:

SY-1000 TUNER ON = F0 41 10 00 00 00 69 12 7F 00 00 02 01 7E F7
w/ PRE-LINK COMMAND for EDITOR MODE ON = F0 41 10 00 00 00 69 12 7F 00 00 01 01 7F F7

SY-1000 TUNER OFF = F0 41 10 00 00 00 69 12 7F 00 00 02 00 7F F7
w/ POST-LINK COMMAND for EDITOR MODE OFF = F0 41 10 00 00 00 69 12 7F 00 00 01 00 00 F7

If anybody has any ideas on how to modify the script, please reply! Thank you.

2

I was wondering why it was taking so long to load the rackspace but there’s a 15,000 line scriptlet in it — totally wild.

I don’t know who will be able to look at that – specially without access to an SY-1000

3

Thanks for responding!

Yes, indeed. Without an SY-1000 to test, its virtually impossible to replicate. I was really looking for more general guidance since I think I’ve narrowed the problem down quite a bit.

I did figure out that if I removed all references to the problem SysEx parameter that the “megascript” seems to run fine. Scriptlet seems a little understated :smile:

It also turns out the tuner can be controlled via CC anyway, so maybe it’s not really a critical issue once the problematic parameters have been removed.