I am running the whole band through three instances of GP (Mics/ Instruments/ Guitar)
In Instruments I have about 30 Rackspaces and I figured out that my RAM (32GB) is at about 80%, CPU is safe…
I had a lot of bypassed plugins in the copied Rackspaces; I erased the not needed once but still have high RAM.
In each Rackspace I have Addictive Drum2, triggered by a midi widget. This needs quite high RAM.
The idea is now to create a fourth instance just for the Drum based on a Global Rackspace, as my drummer plays most of the time with the sam kit and setting.
Unfortunately I have general problems to understand the Global Rackspace wiring (usually I follow some YouTube instructions…) BUT, how does it work with midi??
Could somebody be so kind to let me know how I have to set it.
Thanks in advance!
Below a photo how it currently looks…
Because their is no connection between the „From Rackspace“ and the „midi“ widget.
As I said, I as well do not understand/ know, how to set the normal Rackspace up n cooperation with the Global Rackspace.
The idea is saving RAM but keeping the flexibility…
If you are going to use a separate instance (or not) for the drummer, the MIDI In plugin will be the one associated with the drums controller. It can be set up in either the default rackspace or in the Global rackspace. The only restriction of the Global rackspace is that there can be only the one rackspace and no variations.
Just to be clear, the lack of variations in the global rackspace was a design decision and not a restriction.
Remember that you can control global widgets from your rackspaces so changing variations in your local rackspace can change settings in the global rackspace.
Was not able to test it yet; but in any case, I guess
I can forget the Global Rackspace, it will not help me to save RAM. (As I understand it correctly)
I just make individual Rackspaces, if an Individualisation is needed.
Are you running out of RAM? The main purpose of the Global Rackspace is for stuff you use pretty much all the time so that you don’t have to duplicate everything in every rackspace so that certainly will save some RAM, if RAM is in fact an issue.
If all else fails, then predictive loading would let you have hundreds of rackspaces in a small amount of RAM!
Yes, the drums are used in each song, most of the times with the same setting.
Just some songs have different drum settings.
The reason to run the instruments through GP is the flexibility.
Instead of running a fourth instance just for the drums it is may better to keep the drums in my instruments instance, put the standard drum in the Global Rackspacke; and just stack the drums in a Local Rackspace when it’s playing something different from normal…
But that means I have to understand how to trigger midi in the Globel Rackspace by OSC…
Predictive loading is the choice for a gig, when we have a fixed playlist, but for practice it’s not good, my crew will kill me if the habe to wait for the loading…
Let’s see.
Thanks
Flodder
I will first try to do it with the midi OSC setting, as this will not work I try your scriptlet.
As I haven’t worked with the scripting so far it would be the next challenge…
The nice thing about scriptlets that someone has already coded is that they act as a regular midi plugin in wiring view. So if it works as you need then you don’t have to edit/understand the code at all: plug and play!
I almost forgot to give the feedback to the result.
I tried it with the midi by OSC which was easy, thanks to the
explanations, at the end!
I kept the drums in the “Instruments” Instance and run them through the
global Rackspace. RAM usage is lower now.
I have a problem.
For some reason the midi signal, which is coming in from the drums to the midi out OSC is not reaching the midi in OSC in the global rackspace.
In the main monitor of GB I see the midi signal coming in, but not just the green lit is shining, as well the orange below…?
I have absolutely no ideas what to do?? My drummer is off…
If it worked before it is probably that you used an IP address which is no more valid. If you don’t use the local host IP address 127.0.0.1, for what you are doing, you should.
Thanks David.
The first time I set it up it was the from you mentioned IP and it worked, even if the Notebook IP is different.
Please consider, it is just the routing from the normal Rackspace to the global Rackspace.
Which IP should I use?
Thanks!
If you keep local with regard to the network connection, i.e. don’t connect to another computer via a network connection, then use the local host address which is 127.0.0.1
From a local rackspace to the global rackspace on the same computer this will always work. Whatever the current IP of the computer, the 127.0.0.1 address is implicitly always valid.
I haven’t changed anything at or in the network according to the working status, but it doesn’t work anymore.
What means the orange lit showing in the midi income status?
I am really in trouble if I do not get it back to working status…
Sorry but you don’t provide any info, how do you think we could find what’s wrong with your setup while knowing so few about it. Could you post your gig file, such that we could see what could be wrong with it?
Sorry David,
I don’t know which Info you would need.
I have put the gig file on a stick and will send it as soon I am in a network ( I message from a mobile phone currently, the machine GP is running on I do not bring online… Windows…)
