Hi,
I have a Rackspace that loads OK into a new Gig and seems to operate as expected, however when I attempt to duplicate the rackspace GP (5.0.9, Windows 11) hangs.
Gig file attached.
What happens if you export the rackspace and then drag the exported version back into GP (where it should create a new rackspace)?
Do you have any GP Script in the gig? If so, what happens if you remove it (and recompile to clear the code)? Does duplication still fail?
I can’t get any hang when I try to duplicate, but I don’t have Forager, Cthulhu, or Bazlille—so, one would deduce that the issue could be in one of those 3 plugins. Remove one at a time and try to duplicate until you don’t get the hang–the culprit will become obvious.
EDIT: I also see you have a SongSelect scriptlet in the Global rackspace. I wonder if that too may be a culprit.
Hi.
After trying all the suggestions above,I have determined that removing the ‘MIDI Out (loopMIDI DAW to KMo)’ output block enables the rackspace to duplicate.
That block represents a virtual port defined by LoopMIDI.
Ah yes, I don’t have loopMIDI installed at the moment.
I note that export/import worked OK.
I also note that clearing and recompiling the code from the scriptlets on the Global Rack Wiring page did not help.
Wouldn’t duplicate be just like export/import, but without the actual file as an intermediate product?
In theory – but that’s why the test is useful - to see if anything is different.
In debugging, one does not make any assumptions about how something should work.
OK, the virtual port ‘MIDI Out (loopMIDI DAW to KMo)’ was enabled on both the input and output sides of GP.
Disabling that port in GP on the input side solved the issue.
Yep – that’s a feedback loop - it’s pretty much the same problem that we describe in our blog