Common VSTs in Global Rackspace

General discussion about Gig Performer
1

I just searched the Community articles as well as the GP manual and couldn’t find any detailed instructions on how to us the Global Rackspace for common VSTs. I found one article that states, “Best would be you get MIDI In in the local rackspace where you define your key splits and filter note on messages for plugins which should not produce sound. And then route this MIDI via the OSC MIDI to the global rackspace.” How, exactly, is this set up? How is the routing from the local rackspace connected to the VST in the global rackspace? Could someone please detail what the setup looks like in both the local and global rackspaces?

Much appreciated.

2

I found this about routing MIDI to the global rackspace:

And this about the global rackspace in general:

Hope this helps.

3

Global Rackspace?

Check out the resources here → Global rackspace resources

3 Likes
4

My impression is a lot of the Global Rackpsace videos seems to emphasize using it for effects, often for guitarists. I think that was the original emphasis of the developers.

There seems to be less material on using the Global Rackspaces for plugin instruments (within Kontakt, etc.)

I agree with the sentence in your first post. It is preferable to keep the Midi In Block in a local rackspace and put the plugin generating the audio in the Global Rackpsace. Then return it to the local rackspace for individualized effects, etc. for any processing. This give maximum flexibility, while getting the ram efficiency benefits of putting the plugin in the Global Rackspace.

The ability to simply route midi from a local rackspace to the Global Rackspace is not currently build into GP. [Edit: I believe in GP 5.xx, this function was added]. I am not sure if there are technical reasons or the Global Rackpspace was not originally conceived for this purpose (it was more viewed as a place to put effects?).

But, OSC works well for this purpose. It took me a bit of time (I am not too strong technically), but I think I am getting it (although I am still trying to perfect my understanding of this).

So, with this as I backdrop, in terms of plug-in instruments (via Kontakt or otherwise), I tend to think the Global Rackspace is a great place to put sample-heavy instruments that you use (without changing the samples, themselves) repeatedly. This is because I believe you save substantial ram as compared to duplicating those instruments in different local rackspaces.

The method of using the MIDI In block in the local rackspace and only using the sample-based plugin in the Global Rackspace gives you full flexibility for splits, layers and using these plugins the same rackspace with other instruments (in local rackspaces).

There are other techniques that are similar, like re-using the same rackspace by use of variations.

Also, within Kontakt, you can purge non-used samples. But, I think this would conflict with the idea of reusing the plugin in different variations or using it in the Global Rackspace. So, I think the purging technique is best used if you are just using that Kontakt “sound” in a single rackspace and not reusing it in multiple songs.

Okay, I’ve taken up enough space… Hah!

Jeff

2 Likes
5

Hi Jeff,

So the MIDI routing between global and local Rackspace already works… I can only say something about GP 5 here - and routing between global and locale rackspaces makes from my point of view absolutely sense for keyboarders.

I (want) to use this in the future to be able to exchange equipment quickly. This is enormously helpful if you want to quickly switch between different hardware setups. The only problem is that my current solution with local GP ports only works if you don’t need the transpose function in the set list (it is currently buggy)

I have the “real” HW sources in the Global Rackspace. They are then connected to local GP ports, which are then routed to the synths in the local rackspace.

I do this because I have defined keysplits and transpose in the local GP ports in the rackspace. They are again controlled by widget in the panel, so that I can also change the splitpoint and the transpose with a variation change.

Of course, this is also possible with local sources - the only point is that if you change the hardware you have to reset everything. If the source is in the global rackspace, you just replace it there and it’s done, because in that case you don’t have to touch the local rackspaces anymore (since they stay on the local ports)

In principle, you can of course also use the send/receive function of “Send to Rackspaces” - the only problem is that you lose all the filter, transpose and keysplitt capabilities of the normal midi input - which can only be adjusted once in the global rackspace.

On the subject of kontact, I am not quite sure what is faster / more memory-saving - but my guess goes that the Global Rackspace could also be a better solution if you use kontact in many rackspaces and can accept short switching times for the sake of a better memory performance.

CU Ellis

6

Did you try Rig Manager for swapping Controller Hardware?

7

Yes… the Rig Manger seems to be helpful if you have HW controllers assigned to widget on the panel - but at last from my understanding it doesn’t work for the wiring…

8

It works for MIDI devices also

9

No - not for this use case… I just tested it… Interestingly the Rig Manger even remember mappings from former projects (I open a new empty project and still had the mappings from the former project…) - but this is not the usecase.

The task is, to exchange dedicated MIDI out object in the wiring view. Each MIDI out object have in my case dedicated settings that are controlled by widgets (Splitpoint, Transpose).

So what you can do with the Rig Manager is, to exchange the HW controller that controls a corresponding widget over MIDI.

What you can’t do is to exchange the MIDI input object that is assigned to the controlled widget…

10

I think you posted a simple example somewhere but I can’t find it anymore - where did you post it?

11

I sent it via PM - how ever here it is again:

test.gig (28.8 KB)

Just do a transpose in the setlist and check the two midi monitors…

THX
Ellis

12

With Rig Manager you can exchange a physical MIDI device for a MIDI Device Alias.
And you can define MIDI Control Aliases which itself can be used for mapping to a widget.

Rig Manager can not exchange physical MIDI Out Devices.

13

@pianopaul: Exactly that - and here helps the trick with the locale GP-Port. The point here is, that I don’t like to mix up controller equipment with keyboard equipment and keep the wiring free from any external HW controller MIDI data.

So controller equipment (in may case midi fighter) uses the regular way over the Rig manger and the Keyboard equipment uses the way over the global rack space…