why is an organ sound playing in all my rackspaces - its not globally set and I have no organ anywhere…
is this a glitch???
Could your hardware keyboard be responsible?
no - hardware is arturia controller - not possible - weird glitch
I shut down the gig file and loaded it back up - it was gone - not cool
It’s easy to check, try with another organ plugin and see is that one glitching.
I would guess it’s stuck note? Did you have organs anywhere?
That’s the thing I have organs in the gig file but none in the rackspaces where I was playing it - and I don’t have any global instruments (just effects)
So I rebooted and it was gone - I wish I could recreate it
Any chance you used 2 instances of Gig Performer?
And you’re sure you were changing rackspaces, not just variations?
Alternatively, could some scripting be involved?
I wish! Ill be back today rebooting and checking all my settings.
I think a good feature request is to get rid of the legacy change all midi blocks option when changing an instrument.
Another critical feature is to make it extremely hard to mess with a rackspace - a pop up window that says something to the effect of " be careful you could spend hours rerouting all your midi items etc"
This is such a good program - but some of us do not think like programmers - we think like musicians - and some items require some hand holding.
What relation is between changing an instrument(VST?) and MIDI blocks?
You could revert the rackspace to the last saved version.
1 Like
I think jweisgal is talking about the option to apply changes to all midi in blocks with the same name (or something like that). As David pointed out, it is better not to resort to that and instead have the Rig Manager set up.
But, I think what often happens is you start set up rackspaces before you get into using the Rig Manager. And at that point it might be helpful to use that option once before setting up the Rig Manager (and never using it again).
It sort of agree that a caution message would be helpful.
Jeff
Yes - DHJ was very helpful and we set up a main rackspace - in fact - that should be the default when you start.
that way you have a foundation that is unchanged.
It’s extremely useful for people who have not migrated to the rig manager.
If your needs are simple, then it’s still very useful - and you can easily change back by just using the same process again.
I think one big difficulty with which we’re faced is that people tend to just jump in and start using GP without really understanding all its capabilities. We get that, it’s really easy to use it at the beginning but when people don’t (even quickly) review the documentation to understand all the capabilities, it’s easy to go down a hole.
If I had $1 for every time someone asks a question that is addressed in depth in our really excellent user manual, I could retire today 
1 Like
Maybe even a bigger warning? “Please see manual [link] first to determine if you want to proceed.”
Or:
“BE FOREWARNED, ALL MAY BE LOST IF YOU PROCEED ON THIS PATH!” 
Ahh, easy for me to say.
Yes, but all is not lost since you can easily reverse the procedure!
2 Likes
I’m tempted to suggest that this warning should be placed on the outside box of any computer somebody purchases
6 Likes
I believe @jeffn1 was referring to the idea of having a Rig manager master for all startup users. That sort of caution statement - or introductory statement - if its best practice to have a Master - it should be the default. And that one should be incredibly hard to edit and save without a caution.
the one that pops up I would not even have as an option. Every time you start to manage or move certain midi blocks to other keys - (which in my case is a lot as I’m deciding the best place for the song production) - having this pop up every time is not ideal.
I’m saying remove the option altogether.
My perspective is from a technically inclined user - but not a programmer.
I think we beat this thread to death
6 Likes