Crosspost from the other thread mentioned by @beerbong, just to keep things connected. Maybe a mod can merge the threads?
Ok. I tried it. First everything went without problems. But then I thought, what if my system is too fast for this and I built a modificated benchmark with lots of kontakt instances. The more kontakt instances I had, the quicker I ran into problems. I ended up with 120 instances, ymmv depending on buffer settings and system power. So at least in my case it is clearly system spec related. I don’t know if it is more of a RAM issue, or a CPU issue, or whatever. An easy way to trigger the faulty behavior if it doesn’t do it on it’s own is quickly stopping and starting by hitting the spacebar twice while the test is running.
Anyways, here is my project, if you want to try it with an easily scalable test project that is bigger than the one by J Buckingham, but very similar. Just duplicate the tracks (some tracks) if you have a very beefy system or delete some. Requierments: Kontakt w/ factory selection.Dropbox - File Deleted - Simplify your life
Another propably related thing I ran into, when testing some of my bigger projects: sometimes the articulation wouldn’t switch (because it already was on slot 1/default or no articualtion selected at all) but the sound would cut out for a moment on various tracks just to come in a moment later. Clearly something that isn’t happening when on Cubase 10.0. Tried it kinda side to side.
My system specs: Win 10 Pro, i9 9900k, 32GB RAM, NVMe system drive, Samples on external SSD connected via USB 3.1.
Gonna crosspost this to the other big thread, just so it doesn’t get lost.