Understood, but I am talking about the CPU hit when I am using the plugins located in the Global Rackspace as compared to using those same plugins in a regular rackspace.
Like I suggested, I don’t know if this is true for other systems. I don’t know if the CPU hit is worse using OSC than if I just used a MIDI IN block in the Global Rackspace.
But, even taking that into account, it seems to be working nicely and it definitely seems to have reduced my ram usage substantially. So far, so good!
I loaded up the gig file in my other laptop. [I did figure out that I needed to change options to enable OSC, which I did].
But, it seems I am not getting sound from the instrument in the Global Rackspace unless I switch from the local rackspace (actually in the Setlist mode) to the Global Rackspace. Then I get sound.
So, I will have to spend some more time on it (I did not have time this morning).
But, I figured I would throw this out. Maybe there is an obvious thing someone can tell I am likely overlooking when this happens.
Thanks, as always…
PS. I think I “fixed it” by just switching back and forth between rackspaces in set list mode. I do not know the reason why (maybe it needs a “reset” after the reconfiguration of the regular rackspace with the Global rackspace?). So, if I just switch to a different rackspace and then switch back (within the song in set list mode), it starts behaving properly. It seems like (hopefully) I only need to do this once for each song part and then save the Gig file, and then issue is resolved.
