It's NOT more complaining, I'm hoping I can be of help!
From what I gather there are a few people experiencing problems with this setup (and similar setups) but from browsing this forum it would seem there are still some facts to be established so I thought I'd take it upon myself to help narrow down the cause of the problem through a series of observations.
OBSERVATION #1 - Crashes don't occur in 'empty' projects
When I tested the demo versions of these lovely compressors, I simply loaded up some audio in a blank project and got tweaking with CL1. Everything worked well, so obviously I rushed to the AA store pretty quickly after that. The next time I called up one of these badboys in a working project, the interface came up blank (white) so I had to use Cubase 7's "Use Generic Editor" option (which sucks) in order to get the sound I wanted.
OBSERVATION #2 - Crashes are inevitable as project size grows
IF I start my project with one of the CL plugins early on and everything's OK, it's only a matter of time before that CL plugin brings Cubase down. In other words, it would seem that at some point after more plugins are added, the CL plugin will malfunction. The first sign of this is the fully white GUI, the second sign is Cubase throwing up an error message (much like the ones already posted to this forum by other members).
OBSERVATION #3 - I can run 500+ instances of CL1 with no problems
If I start an 'empty' project, load a wave loop, setup the CL1 compressor in a typical fashion, hit play, duplicate the track, then duplicate both of those tracks, then duplicate all 4 tracks, then 8, and keep repeating this process.. I get above the 500 channel mark before I can't add any more instances. At this point my CPU and disk meters are going wild, but CL1's interface still shows up as normal and Cubase appears to be otherwise stable (at least it's not crashing).
OBSERVATION #4 - The bit-bridged 32bit build running in C7 x64 dies quicker
If I run the same test as in my previous observation but this time using the 32bit version of CL1 running through Steinberg's own BitBridge, the BitBridge itself crashes long, long before I get anywhere near 500 instances. If I kill BitBridge via the Windows Task Manager, Cubase remains stable. I mention this only to highlight that running the 32bit version in C7 x64 is not a solution, since the BitBridge itself will bring Cubase down. (Hence I only buy 64bit plugins now)
And my thoughts...
I wonder whether or not it's possible that there's some sort of 'clash' between the CL Series plugins and some other manufacturer's plugin or plugin framework that could be causing problems with instances of CL1 in busy projects. I have quite an insane collection so it would be difficult for me to narrow down, but for instance I use a lot of SoundToys, FabFilter, Plugin Alliance (Brainworx), iZotope, PSP Audioware, Audio Damage, Slate Digital, Sonimus, Valhalla, Sleepy Time DSP, etc...
Perhaps I will find time to do a 'clash' test to see if there is a specific plugin or manufacturer that upsets the CL Series plugins. No promises though! If anyone else who's experienced this problem is reading, perhaps you could have a look at what plugins you use among those that I've listed above.
Thanks <3
Owen...
P.S. I understand that this problem is not specific to Cubase
P.P.S. I understand that it also occurs with the other Arts Acoustic plugins P.P.P.S.
