For some time I have had an issue with crackling noises, mainly involving the Wavestate Native and NI Icon Bass vsts. The workaround was to turn all vsts off for every song until they were needed. It was “clunky” but it worked.
But Korg have issued an update for Wavestate Native, which doesn’t mention the vst being a processor hog, but I am in my third setlist since and there hasn’t been a single crackle! This might be of interest to @Derek as you use the Korg Wavestate Native products.
Thanks for pointing out. I’m away on business for a few days, but will check for updates on the weekend, when I’m back home.
Well, I updated all my Korg VSTs yesterday and it looked good. Today, whilst I have been doing other things, I have ran two songs, one of which uses two Wavestate instances and one of which uses Wavestate and Modwave.
I have literally left them running for hours, come back, played, stopped, changed songs (often a trigger for the overload issue), chnaged back to the song, left them playing again, and have had zero problems.
So, whilst Korg have not acknowledged it in their feature update list, it looks promising that they have done some update to solve the problem.
I’m glad it works for you as well, Derek. I emailed them about the problems I was facing, but the conversation eventually drifted into silence, but it seems that they have dealt with whatever it was. I am emailing them to let them know.
I’ve left it running tonight in Cubase as well in one of the songs that uses two wavestate instances (which I am in the process of recording, and that looks fine as well.