So I suppose that if you add a GP MIDI monitor plugin just after the MIDI in block it will display properly the MIDI messages sent from your controller? Which would mean that MIDI information are perfectly entering the rackspace…
interesting idea. I will try that next time it occurs.
I am still leaning toward a corrupted gig file: If this is soo rare and has never happened before, then what else could it be.
(on rackspace 20 of 25 of removing kk plugins)
Understood, and I certainly don’t discourage going through all those steps.
I’m just looking down a different path.
“Midi not getting to the VSTs” would not explain the behavior apparent in either the video in post one or the VSTs springing back to life when he deletes a “blue wire”. The fact that the VSTs do not produce sound, even on their internal VU meters when he is pressing keys on their internal virtual keyboards, yet the virtual keys can be seen moving, points me to something other than “midi not getting through”.
Two incremental things I’m wondering:
- is it always Komplete Kontrol VSTs that go silent, or does this also happen with the Arturia ones?
- is only a “blue wire” that makes it come back to life? What if it’s a red midi wire that’s deleted and re-added?
the entire rackspace, with mixed arturia (not used via KK) and KK plugins goes silent
i also thot of trying the red wire, and hadn’t tested that idea yet
ok, i have pretty good news. After removing all the kk files, it has not happened yet.
I dare not mark this as resolved until further testing, However I am of course almost relieved, and greatly appreciative. whew, I had a month into this (just bot GP, and took a risk to abandon mainstage to program 30 songs for a band, that has some high profile venues/shows coming up)
mostly… i have to admit, I enjoyed this community… and the comradery here, impressive… cant wait for more issues, jk, there is much to discuss, and excited about gp4
1 Like
So what happens if you now out just one back?
add back a Komplete Kontrol plugin?.. I will test that… after the PTSD wears off, lol
I have to admit, I am saddened about the concept of not using KK. It is a fantastic way to audition many different patches quickly, have a standard interface, standard arp features, standard search location (for patches), HAVE a search, know where to save patches, volume in same place, meters in same place, patch files are saved in same place… the list goes on… not sure if it has sunk in yet. My focus was on fixing this, and getting thru these upcoming gigs without the onstage panic i was going thru.
edit, conversely, I can perhaps audition patches with KK, then use the direct VST when done, just another step
I hope you don’t mind a stupid question here, but…
Is there ANY OTHER application running on your computer(s) that might be (intermittently) hijacking your audio interface? Or an application running in the background that is common to both computers?
Just trying to think of what might be overlooked, and abandon all assumptions.
good idea, however the other rackspaces work, and removing an audio connection fixes the issue, so i think that rules out most of those ideas.
For now, the system appears to be stable, i have not had the issue since removing all KK plugins. (just a few hours ago)
Soo this begs the questions… if using KK (excessively) is an issue… would Kontakt or Reactor also become an issue?
are they not both ‘hosts’ within the GP host? and, say a few months down the line, and 100 rackspaces made from my blood sweat, tears, and years… (for dramatic effect) and therefore also become an issue? (once the critical mass has been crossed)
or… are those 2 different animals?
thanks
One has nothing to do with the other. Kontakt and Reactor (and Absynth and massive and guitar rig) all work perfectly fine. I’ve been using them for years, as have many others
That is EXACTLY what I was hoping to hear. (History of success) yay
Because I am curious, what is the loading time now without Komplete Kontrol plugins?
The reason I gave you steps to eliminate the KK plugins with once command was precisely this, but you must have missed my post from 2 days ago. KK plugins are the oddity here and all other plugins that we know off never had an issue like this. In fact - this is the first time in 5 or 6 years that we have something like this reported.
It may be that the hardware integration or some kind of inter-plugin communication of the KK plugins is responsible for them failing like this.
Removing the blue wire would “tickle” (so to say) the plugins in your rackspace which may reset them internally and resolve the problem that plugin got itself into. This is entirely an issue with the plugin itself and therefore I’d recommend not using the KK plugins. I know I couldn’t live with the fact that there “might” be a possibility that my rackspace is dead when I switch to it 
I could not go on stage with that fear.
I’m glad you finally found the culprit and I’m proud of our AWESOME community here which always amazes me with its perseverance and helpful and sound advice.
Cheers.
3 Likes
It is 50 seconds, for 25 rackspaces. Which is cut in half now.
Out of curiosity, what is the approx average load time that people here mention (ballpark is fine, or a range)
thanks again, and i will make a post flagged as solution (if that is how i should do it here)
Yes, that would have been more efficient. I haven’t used the plug in manager much, and hesitated when i saw it for sure. thank you
(just my luck haha) ok, that is good to hear
Your post did have a profound effect on the solution btw, thank you
Solution… don’t use komplete kontrol within GP. (edit, no issues in 18 hours of testing, which is good)
Yes, I was losing sleep over this for sure, finally got a good nights rest last night.
It is true, I have never been so impressed with the comradery here. Probably the best feature of GP is this forum.
5 Likes
What is still a mistery to me, is how could KK block the sound of all other non KK plugins in GP. And why moving an audio connection made all plugins be able to produce sound again. My natural curiosity suffers from this unsolved question 
Yours and mine both.
Something very peculiar is happening when one plugin can make other plugins go silent.
With Steven slate plugin Virtual Bus compressors I was able to crash Gem dopamine when predictive load was enabled.
So with bad coded plugins anything is possible 