Hex to make play widget

[simusix2]

My old Yamaha keyboard only outputs hexadecimal strings when pressing various buttons.
I want to use some buttons to operate some features in global midi such as play, prev and next rack space etc, do I need a script for this?

[SteveC-Bome]

Perhaps, I assume you mean SysEX (System Exclusive messages). MIDI devices actually only send binary (ones and zero) and it is up to the monitoring program to determine how they are displayed to the user. I think Gig Performer converts these for display purposes for standard MIDI messages and just leaves them as hex representation for SysEX.

F0 . … … … F7

I believe that a script can be written to interpret these messages in Gig Performer and possibility convert them. I’m a new user so have not yet done it in Gig Performer as of yet but I do it all the time in Bome MIDI Translator Pro which I also support. Let’s see if there is another user that has already done something similar in Gig Performer that you can leverage. Note that all manufacturers define their own SysEx message structure with exception of the leading F0 and trailing F7 so the odds of having something for your specific keyboard pre-built would be rare and some script modification may be necessary. Most people would need to see a log of the SysEx messages to be able to interpret them and convert them to standard MIDI messages for the results you desire.

There is, however a specific SysEX structure for MIDI Machine Control (MMC) that your keyboard may be using.

Steve

[simusix2]

I’ll get a copy of messages I need to use cheers

[simusix2]

hi, these are the messages I need to use for
next variation
prev variation
play/stop
panic

TIMESTAMP IN PORT STATUS DATA1 DATA2 CHAN NOTE EVENT
00031703 1 – F0 Buffer: 8 Bytes System Exclusive
SYSX: F0 43 70 78 41 53 01 F7
00031D88 1 – F0 Buffer: 8 Bytes System Exclusive
SYSX: F0 43 70 78 41 53 02 F7
0003224C 1 – F0 Buffer: 8 Bytes System Exclusive
SYSX: F0 43 70 78 41 53 03 F7
000326B3 1 – F0 Buffer: 8 Bytes System Exclusive
SYSX: F0 43 70 78 41 54 01 F7

[SteveC-Bome]

Try this

You may need to define you “MyOut” Output block to the device you want.

Make-Play-Widget-with-Sysex.gig (62.1 KB)

Steve

[pianopaul]

I think he wants that his keyboard - which only sends sysex messages - can be used to switch variations etc.

Your script sends out sysex messages.

But maybe I miss something?

[SteveC-Bome]

Yes, I’m working on an alternate script that should do the job. Stay tuned.

[SteveC-Bome]

This one should work or be pretty close. The only thing I haven’t figure out is how to simply blink the LED indicator with the SysEx message.on the momentary buttons, I think I would need a timer function for that. It turns all values to 0 except PlayStop and then turns on only the button you press.
For PlayStop it toggles the value.

Maybe not as elegant as the seasoned coders would do but at least it looks like it works.

It also contains code that sends SysEx to a device when you push a widget, but PlayStop Push only sends on Play as if I tried to toggle it it created an infinite loop. Anyone care to clean it up more from here?
SysExTo-Widget.gig (71.7 KB)

Steve

[simusix2]

Will try that tomz Steve, many thanks

[simusix2]

HI in gig script live come up with this (i fully understand script)
Gig (GigScript) - - Syntax Error in “Main”: Line 5, Col 1: Unexpected or unrecognized token: ‘On’
Mismatched input ‘On’ expecting Identifier

[simusix2]

my input port is “Focusrite” in rig manager
cheers

[dhj]

@simusix2

HI in gig script live come up with this (i fully understand script)
Gig (GigScript) - - Syntax Error in “Main”: Line 5, Col 1: Unexpected or unrecognized token: ‘On’
Mismatched input ‘On’ expecting Identifier

Yes, you have a syntax error on Line 5!

Without seeing your script, it’s rather difficult to say what’s actually wrong with it🤨

[SteveC-Bome]

@dhj, the script is in the gig file. I’ll take a look at it in a few hours.

Steve

[dhj]

I just looked — this script could never have worked

1. there’s an extra empty ‘var’
2. there is no type defined for the ‘mesg’ arg in the call back
3. The device name “MyInput” is not defined anywhere

[SteveC-Bome]

You can remove the Rig Script and just use the Rackspace Script

[SteveC-Bome]

Try this version, I renamed the Input Port Handle to Focusrite.

I’m not sure if Panic is working correctly though. We are capturing the message OK but I’m not sure it is executing the widget. There may be something more we need to do after sending a Panic.

SysExTo-Widget-2021-08-31.gig (141.6 KB)

Steve Caldwell
Bome Customer Care

[simusix2]

Thanks will try out

[SteveC-Bome]

I removed these lines from the script which were causing a MIDI loop and it fixed the Panic Problem

// Called when a widget value has changed
/*
On WidgetValueChanged(newValue : double) from Panic1
    
   if newValue > 0.5
      then
         SendSysexExternal ( MyOut, smPanic)
         SetWidgetValue(Panic1, 1.0)
   end     

    
End
*/

Here is the updated rig file

SysExTo-Widget-2021-08-31.gig (143.3 KB)

[David-san]

If the old Yamaha controller of @simusix2 would generate CC messages you wouldn’t write a rackspace script to control widgets, right?

So here is what you have to add to the gig script he already has to make the Yamaha controller generate CC messages:

@David-san

Thinking about it, I should probably only convert your sysex into CC by adding the following code into your gig script editor:

On SysexEvent(sysex: SysexMessage) From Focusrite 
 Select
   sysex == "F0 43 70 78 41 53 01 F7" Do InjectMidiEventViaRigManager(Focusrite , MakeControlChangeMessageEx(20, 127, 1));
   sysex == "F0 43 70 78 41 53 02 F7" Do InjectMidiEventViaRigManager(Focusrite , MakeControlChangeMessageEx(21, 127, 1));
   sysex == "F0 43 70 78 41 53 03 F7" Do InjectMidiEventViaRigManager(Focusrite , MakeControlChangeMessageEx(22, 127, 1));
   sysex == "F0 43 70 78 41 54 01 F7" Do InjectMidiEventViaRigManager(Focusrite , MakeControlChangeMessageEx(23, 127, 1));
 End
End

Hence you will be able to MIDI learn the button of your old Yamaha controller to any GP widget. Set your widgets to “momentary to lacthing” in the widget properties, as with a single state SysEx message the only thing you can do is to toggle widgets.

Tell me if it works for you?

It is an 8 lines only GPScript. No need to duplicate it in each rackspace, in the gig script it is available for each rackspace of the whole gig. Why would you do something more complicated?

EDIT: Using this kind of gig script it is even possible to simulate a press on a momentary button by “injecting” an additionnal CC# 0 just after the initial CC# 127.

[SteveC-Bome]

Yes, this looks like a cleaner solution. I haven’t tested it but I’m sure it will work.

Of course, then in Rig Manager you will need to MIDI learn the CC#s that you programmed and give give them names that your Widgets can use.

Steve