[blog] About rackspaces and variations

General discussion about Gig Performer
1

Link: Questions about rackspaces and variations - Gig Performer®

–

Other useful posts:

[1] You could have thousands of rackspaces - LINK

[2] Creating rackspaces along with Rig Manager aliases without a MIDI controller attached - LINK

[3] How to use GPScript to set explicit widget values in different variations - LINK

[4] A plugin in a non active rackspace might consume a certain amount of RAM but shouldn’t use much CPU power. Same as a bypassed plugin - LINK

[5] Is it better to use variations or rackspaces for your patch? → Solid tip to help you decide - LINK

[6] Putting the same plugin in multiple rackspaces does not significantly increase physical RAM because the DLLs are shared – only the instance data is duplicated. - Mute vs. BlockNoteOn for CPU Usage - #8 by dhj ; LINK2

[7] How to change the underlying MIDI Input device for all MIDI In Blocks in all Rackspaces → LINK

[8] Every time you leave a variation, Gig Performer captures the current widget values so that it can reset them back when you return to that variation. → LINK

[9] About the use of the Global rackspace → LINK

[10] The SongParts are using an internal unique identifier that’s tied to a rackspace. If you are curious you can look in the underlying gig file and you will see that there is an attribute associated with each rackspace and that’s used for the association. Moving the order of rackspaces or deleting other rackspaces has no impact on this. → LINK

[11] If a rackspace takes much time to load – it’s mostly the plugins! → LINK

[12] Program Change 0 passing on to plugins → LINK

–

How to set up a keytar to change rackspaces - link

5 Likes
Program changes Rackspace VS Variations? Help!
How does Gig Performer manage DSP
2

Useful post: Newbie to Gig Performer - #36 by Frank1119

3

Q: Is it possible that the CPU spikes occur in rackspaces that don’t have an instance of a faulty plugin in them?

A: It is possible that the plugin implementation has some other non-audio threads running, possibly running erroneously at high priority. Those would be running all the time, regardless of whether the plugin was in the active rackspace.

(source)

[blog] Tips to troubleshoot your computer based setup
4

Q: I’m looking at gig and rackspace files; do I need all these widgets in my rackspaces?

A: LINK

–

1 Like
5

I opted not to use the Neural DSP Gojira Preset function due to a slight delay when changing presets through the plugin, which results in noticeable audio cuts.

In my experience, saving parameters within Gig Performer rackspace variations offers a faster and smoother transition.

(link)

–

Program Change number in rackspaces / setlists – There are several use cases for this.

  1. The performer is using a workstation such as a Kronos along with Gig Performer and when they select a patch or combi on the Kronos, the Kronos can send a program change to Gig Performer to select the appropriate song or rackspace.
  2. The performer is using a sheet music app on an iPad (say) such as MobileSheets or forScore. They have buttons on their keyboard (or on a MIDI pedal controller, or even via automation) that turns the page of the sheet music. The sheet music app can be configured to send program change messages to Gig Performer automatically so that when you reach certain pages, or you touch a “button” on the sheet music app, or when you select a new song, the app will cause Gig Performer to switch to the desired song or song part or variation, etc.
6

Hmm… changing a plugin’s preset (here: NDSP Gojira) means, that everything within the plugin is most probably re-initialized and adjusted (amp model type, effects, EQ settings, microphone settings,…) while using rackspace variations only affect those parameters which are mirrored by a widget on the panel… this might obviously happen much faster, depending on what specific parameters are actually to be changed.
So, i’m not entirely sure if those two approaches can be compared with each other.

7

Hi everybody, I have an additional question about variations: Is there a possibility to save variations in a way, that when returning to a variation, it remembers a specific setting and not the “last used” one?

8

Did you try SetList Mode?

9

not familiar with that, I ll check it out !

10

just to clarify, when, for instance, I have a variation Rhodes with chorus, but while playing I decide to change some parameters of that chorus, later in the set I come back to that variation and need the parameters to be reseted to the original variation value, how do I do that?

11

Use SetList Mode
Create a Song with Song Parts
Each Song Part reference a variation.
As long as you do not ignore variations in Widget properties every time you switch to a song part (which references a variation) the widget values are recalled how they are defined in the variation.

12

Thanks ! This is a nice workaround ! Funny thing that even in the Rackspace selection of the setlist Window the values keep returning to their original state when fiddling around with one variation and then switch to next and back…

13

Gig Performer MSB LSB PC , how to change Songs, Rackspaces via Midi (Tutorial)