My rackspace for jam with s gear v3

I made a rackspace where I can use my preferred software pedals (Including the new S Gear drive Thru) in front of up to 2 instances of S Gear

You can adapt to your needs.

Have fun

Jacques


JB S GEAR JAM RACKSPACE F.gig (2.4 MB)

8 Likes

@Fatherjacques

This is also a nice candidate for “Gig and Rackspace files”.

Aside from a scripting error that I see upon opening this file, I also see that you used AudioUnits. To maintain cross-platform functionality of gig/rackspace files, all plugins in gig and rackspace files include VST(3) plugins.

If you create a version with VSTs, I’ll create a new entry in Gig and Rackspace files.

I tried to correct the scripting error but do not know how to do it. It comes from a previous rackspace that was using script for Helix Native, I do not know nothing about scripting unfortunately.

Can someone post the full error message?

I get this message

Plugin ‘NATIVE’ not found in rackspace ‘S GEAR JAM RACK’
Scripting has been disabled for this rackspace
S GEAR JAM RACK (Rackspace) - Plugin ‘NATIVE’ not found in rackspace ‘S GEAR JAM RACK’
Scripting has been disabled for this rackspace
Uh oh - GP Script runtime error

This is the script

//$<AutoDeclare>
// DO NOT EDIT THIS SECTION MANUALLY
Var
   NATIVE : PluginBlock
   SNAPSHOT1 : Widget
   SNAPSHOT2 : Widget
   SNAPSHOT3 : Widget
   SNAPSHOT4 : Widget
   SNAPSHOT5 : Widget
   SNAPSHOT6 : Widget
   SNAPSHOT7 : Widget
   SNAPSHOT8 : Widget
//$</AutoDeclare>
   BUTTONS : Widget Array = [SNAPSHOT1, SNAPSHOT2, SNAPSHOT3, SNAPSHOT4, SNAPSHOT5, SNAPSHOT6, SNAPSHOT7, SNAPSHOT8]
PreviousTime : Double
DetectionTime : Integer
SnapshotParam : Integer = 36


// Called automatically after script is loaded
Initialization
DetectionTime = 700 // Change this to the number of milliseconds that the wah is at position 0 (heel down) before it’s bypassed.
End

// Deselect other buttons
Function UpdateButtons(index : integer)
    Var i : integer
    for i = 0; i < Size(BUTTONS); i = i + 1 do
        if i <> index then SetWidgetValue(BUTTONS[i],0.0) end
    end    
End

// Called when any of several widgets changed
On WidgetValueChanged(w : Widget, index: integer, newValue : double) from SNAPSHOT1, SNAPSHOT2, SNAPSHOT3, SNAPSHOT4, SNAPSHOT5, SNAPSHOT6, SNAPSHOT7, SNAPSHOT8
    var i : integer
    if newValue == 1.0 then
        SetParameter(NATIVE, SnapshotParam, GetWidgetCurveValue(BUTTONS[index], 1.0))
        //SetWidgetValue(SNAPSHOT, GetWidgetCurveValue(BUTTONS[index], 1.0))
        UpdateButtons(index)
    end
End

// Called when a plugin block parameter value has changed
On ParameterValueChanged(parameterNumber : integer, parameterValue : double) from NATIVE
    var index : integer = StringToInt(GetParameterText(NATIVE,SnapshotParam))-1
    if GetWidgetValue(BUTTONS[index]) <> 1.0 then
        SetWidgetValue(BUTTONS[index],1.0)
        UpdateButtons(index)
    end
End

Oh, well it means what it says. There’s a plugin missing or the plugin is there but it hasn’t been assigned the script name.

1 Like

I think the AudioFilePlayer is missing the GPScript name and also the 8 Button widgets miss it.

The plug-in HELIX NATIVE (For snapshots) is missing but I do not need it. The sript is still there and I cannot cancel it.

Just delete it.

I tried. I do not know how. Will try again later.:slight_smile:

Open the rackspace script window and delete all lines.
Then press compile and close the window.
And the save the gig.

1 Like

I worked! I did not know I had to compile and save again. Thanks a lot.

@Fatherjacques
Now just replace AU with VST(3) versions :slight_smile:

I tried to make a VST version of the rackspace but I get some bizare behaviour in the post effects section of S Gear 1. I do not get this in the Audio Unit version. I am not enough acquainted with Gig Performer to know if it comes from the S Gear VST version or from Gig Performer.

In the Audio Unit version I assigned widgets to put on or off the post effects for both S Gear instances. It works. When I open the editor and change the preset it still works.

In the VST Version it works for the initial preset but if I change the preset in the editor the widget call the type of effects instead the ones I assigned!
S GEAR JAM RACK. VST.rackspace (1.9 MB)

May be somebody could take a look at the rackspace and find what is wrong ?

S GEAR JAM RACK VST.rackspace (1.9 MB)

Well for me it seems that S-Gear doesn’t properly initialize its parameter list…
If you import the rackspace into an empty gig (ignoring the missing mp3) and enter the “panel edit mode”, then inspect the widgets that would switch the after-effects, you will see that they all point to “nameless” parameters! After you simply have opened the regarding S-Gear plugin window and closed it again, the same parameters suddenly have names… but many of the rest still don’t.
You could check if this also happens if you use the VST2 instead of the VST3 (diffrent format, probably diffrent behaviour!).
Oh and maybe you should remove the MIDI assignments of the pedal bypass switches, just for completeness. :beers:

1 Like

This has always been the case with S-Gear. It dynamically assigns the parameters. So “Delay 1 Bypass” in one preset may not be the same parameter number in another preset (and the name will be blank).

I’m sure the dev thought it would make things easier for the user - that only the parameters used in the preset appear in host automation lists. But the reality is that it makes it more difficult.

3 Likes

If not rather “impossible” to ever have a reliable parameter assignment… total bummer for the use in DAWs like Gig Performer. :-1:

That’s something i was assuming too when i tried to get a grasp of what’s going on there…

1 Like

Here’s the answer from Mike:

The S-Gear parameter list changes on each Preset because the rack is re-configurable. This has always been a problematic area because generally, plug-ins don’t do this and it is not always expected by the host. There could be some handshake issue between S-Gear and GP which results in the parameter list not getting updated after a program change. I will investigate.

Hopefully, this will be addressed in future! :slight_smile:

1 Like