Skip Rackspace

General discussion about Gig Performer
1

I asked this question back early in the year, but was wondering if anything has changed with V7. Essentially, is there any way to skip a rackspace when loading a gig file? either as it is loading if it gets “stuck” or upfront to mark it somehow?

If not, how to get past a particular rackspace that is preventing my gig file from loading and crashing GP every time? I send the “error report”, but not sure what that does to help me.

I have a gig file that worked fine the last time (a few months ago) I used it. Now it won’t load and hangs on a particular rackspace and plugin before erroring out every time. Nothing changed except time. I thought it might be the plug-in itself - licensing or something - Waves CR8 - but I have other gig files that use that and they load and work fine.

Best course of action here?

KenM

2

Are you sure it is cr8?
You can disable the plugin in plugin manager.
Then you should be able to load the gig file.
Then remove the plugin and in plugin manager activate the plugin.
Load the plugin and save the gig file
Then reload the gig file.
This way you get rid of a maybe corrupted plugin state

3

You can load the gigfile (a copy…) with a text editor, delete this one rackspace, save the file and load. If only this rackspace is corrupted, it should work.

4

Yah - I did that the last time I asked this, and it does work. Was just hoping for something more “built in”.

5

Not positive - that is what is “showing” when it locks up, but maybe it is the one after it? I will give this a try.

6

Well - it seems to be one instance of CR8 that is causing the problem. Once I went back to a back-up far enough, I found one that works. I don’t think that rackspace (should have) changed, but the older one works. Gonna export that rackspace and import in the new gig file and see if that works.

7

Waves again… :face_with_peeking_eye:

8

It seems to have come down to a missing sample in an instance of the CR8. I must have moved it after the fact while “organizing” lol. Anyway - I got it working again now.

However, it would be nice to be able to “auto disable” a bad behaving plug-in rather than just crash. What would have been ideal is a little message that said something like "Please note that an instance of Waves CR8 was unable to be loaded due to the missing sample ‘mysample’ in the rackspace ‘myrackspace’ "

That may be asking for a little too much lol …

1 Like
9

Awesome idea - if only the plugin would report such failures back to the host …

1 Like
10

lol - I figured as much … but something? anything? rather than just a crash/error screen? I don’t know what is reasonable.

12

If you know that CR8 is the problem, then why not just temporarily start GP without it loading any gig file and just disable that plugin in the plugin manager

1 Like