B3-X in GP not receiving buttons from SKPro

Plugins
1

I have B-3X in a rackspace and I’m controlling it from a Hammond SKPro 73. None of the buttons for percussion, vibrato, leslie on/off, or stop are getting through to the software instrument. (These all work perfectly with the B-3X in stand alone mode.)

MacBookPro OS 10.15.7
I have the latest version of B3-X, 1.3.5 Build (24L19) and am running GP 5.0.9.
I have no midi filters.
I can see the buttons sending info in the midi monitor.

Seems that GP is blocking something from getting through but can’t tell what.

2

Here is a screen shot of midi monitor as I pressed percussion on, then soft, then fast, then third.

Screen Shot 2025-01-08 at 3.49.24 PM
Screen Shot 2025-01-08 at 3.49.24 PM598×461 65.7 KB

3

I recall other threads on the topic. My recollection is B3X has a idiosyncratic way of allowing control if it’s parameters.

Maybe do a search in the forum something like: B3x widgets

Good luck!

Jeff

4

Thanks Jeff, I’ll take a look.

5

If I remember well there is a way to tell B3X to use SK commands. Since the plugin is Hammond authorized they already made some midi commands ready. I cannot check until tonight but I am quite sure

6

Hi Greg, please excuse that I cannot tell you directly why this is happening.

Instead let me show you how to solve the problem the way GP was designed for:

Instead of sending MIDI messages directly to the plugin, you should create widgets on your rackspace panel that respond to MIDI messages (either directly or better via Rig Manager).
Then you connect these widgets to the parameters of B-3X. You can easily “learn” these parameters or select them in a list.

This is the GP way and will be very beneficial for advanced use that you might advance to sooner than you think (drawbar widgets, variations, song parts, scripting etc.)

1 Like
7

Did you try this in Setup of the B3-X in the Section Hammond Profile?

Bildschirmfoto 2025-01-09 um 10.11.54 AM
Bildschirmfoto 2025-01-09 um 10.11.54 AM1452×920 106 KB

8

I guess, the root issue doesn’t lie in the plugin… i rather think it’s the controller!
As shown in the screenshot of the midi monitor, showing the incoming midi messages, the percussion setting is done by using a pair of CC# (99 & 98), where the coarse value of CC#99 is always 38 (maybe representing “percussion” - just a wild guess) and then followed by a fine value of CC#98 (0,1,2,3 - most probably the diffrent settings).

I guess, these messages would have to be “translated” into a format that Gig Performer (and/or the plugin) can use - i.e. via a GigScript which converts those “combi-messages” into proper CC# with values between 0-127.

9

My Guess is that when you activate the Hammond Profile the plugin is controlled directly by the Hammond controller.
But when you want to use widgets then it will not work with the messages sent by the Hammond Controller.

1 Like
10

Absolutely worth a try! :+1:

11

That controller is sending non-registered parameter numbers and GP does not directly support those (yet). The solution in the past has been to use a GigScript that recognizes those sequences and converts them into single value CC messages that can then be recognized by widgets.

I know some examples of this exist on the forums somewhere.

2 Likes