I used to think I was alone on this issue until some recent digging unearthed a multitude of composers with the same issues. I have since submitted
two tickest to NI for which I have received only the auto-reply to which you all are no doubt familiar. It's truly a shame that NI hasn't addressed this
major issue. Tempo changes are at the root of what a sequencer can excel at as well as being crucial in a film composers tool chest. Here's what
I have discovered in trying to find a workaround or anything that might get this thing to work. First off, this is definitely corolated with CPU usage
and buffer size in addition to project complexity. They all really tie together ultimately in that the CPU can either handle it or not. I concur that this
issue can happen outside of VE Pro as I can get it to happen when K5 is hosted in Nuendo. As stated earlier, on very small projects this does not
present itself as there is evidently enough CPU overhead to compensate for what I believe to be bloated code in K5. Again, ramps are way more
troublesome and can bring my 12core Mac, with almost all SSDs, to it's knees. IMHO it's not the amount of playing tracks that matter, rather how
many tracks are in the given project - regardless if they are playing or not. Also, I don't believe this occurs in K4. I was testing yet again and was not
able to get K4 to fail which I think is good news and I have made NI aware of this. I'm afraid this won't help any of us but perhaps as some have
stated if we film and T.V. composers keep pressing maybe NI will fix this. In the meantime any useful workarounds are all we can hope for.
FWIW, I almost never post but this problem is so glaring and doesn't occur with other plugins e.g. Omnisphere, RMX, U-he, Waves, UAD, etc.,
that I felt compelled to jump in the fray.
Mac 12core (2 x 2.93 GHz 6-core Intel Xenon) OSX 10.8.5, 64GB ram, Nuendo 6.x, 2 x 480 3GB/s SSD, 2 x 480 6GB/s SSD, 1 2TB 7200rpm