What's the latest from NI Karel? I too am wrestling with this issue on Cubase 6 on PC.
What about the other posters? Have any of you stumbled across a solution?
Brett
183,035 users have contributed to 42,273 threads and 254,974 posts.
In the past 24 hours, we have 2 new thread(s), 8 new post(s) and 52 new user(s).
I just had this issue with a tempo ramping down and a CPU spike and pops/clicks.
I went into each instance of Kontakt 5 and turned off the External tempo sync. FYI, it's in the Master section in BPM.
The problem totally went away.
BTW - I am running Cubase 7 in Windows 7 PC, with Ableton Live 8 and VEPro running as well. All in 64 bit.
Obviously a NI K5 issue. Hope this helps
Has anyone gotten further with this tempo change clicking in Kontakt 5 issue?
Someone earlier said that it only happens when Kontakt is in VEPro, I have proven this incorrect. It is happening when Kontakt is opened inside Cubase 7 here.
If you score film/TV, this issue is a huge one; I'm constantly trying to figure out how to work around this, but usually it's a huge inconvenience and time waster to solve. And I cannot write any accelerando or rallentandos, for sure.
Thoughts? NI still doesn't quite feel film scoring composers rank high enough to sort out problems specific to them!
That is my experience as well. Whether it's a jump or a ramp there is an audible pop.
I have not experienced this problem in DP or Logic which both use Audio Units. Also this does not happen with non kontakt instruments. So it appears this is a problem with the VST plugin version of kontakt for tempo synched instances. Is NI aware of this?
I have a support ticket in with NI re: this Kontakt issue. I find it hard to believe that there aren't more Cubase users having this problem.
Interesting that it's potentially a VST issue. I have not used tempo sync loops in Kontakt much at all in the past, so I might not have had this issue show itself in the past.
The thing is, it doesn't matter what the host is, Windows slave machines always run the VST version of Kontakt, so even if you're using Logic you are still using VST on the slave.
This tells me that it's not a VST Kontakt problem per se, but it is either a Cubase problem, or a VST connector problem. Does anyone here have Studio One or any other VST host to check? Actually as DP now can use VST, it could be checked using that, couldn't it?
Regarding people not having problems with Cubase, be aware that there are many more Cubase Windows users than Cubase Mac users, and it may not even be a problem in Windows. I can't test it for you, as I'm not using slave machines.
DG
Increasing the buffer size in my VEP server instances in Cubase fixed it for me. Took some of the load off of the CPU.
i was running 7 instances within Cubase (each with 4-7 instances of kontakt/play) at a latency value of 1 (buffer of 128). Increased them all to a latency value of 2 buffers and no more problems... Yet.
Jdiggity, have you tried putting a tempo change in your Cubase sequence and as you play across it, with Kontakt is ext sync mode, and you're not hearing a click or pop? Or try a tempo ramp up or down and see if it clicks.
would love to think that increasing the buffer as you said solves the tempo change Kontakt midi sync issue.
thx,
Mr A