Can you repro this issue with the native VSTs in your PC DAW

[DavidLowndes]

This is a long post, but I'll try to cover what I know so far in the hope that others will try and hopefully be able to reproduce this issue as I can.

If I have one of the native VSTs (Opsix, Wavestate, Modwave) on a track that's not playing notes for some time, I get high CPU usage that causes major audio problems with other tracks that are playing.

I've reproduced the issue on my PC in both Reaper and Cubase, both when using the motherboard audio device and an external FireWire (Presonus FP10) device, so I don't believe the DAW or audio devices are specific to this issue.

In the following video I show the CPU usage using the Opsix native because it shows the issue very quickly for me.

For comparison, after releasing the key:

• Opsix native takes only a few seconds to show the issue.
  Wavestate native took around 20s to show the issue.
  Modwave native took around 5m 30s to show the issue.

In the video I use Reaper (but use whatever DAW you have) to show the CPU usage issue.

• I add the Opsix native instrument and use the default initial patch.
  Play a note and release it. Don't play anything else.
  Wait for the CPU usage to increase (if you have a lot of cores, it may not increase much). Note that this may take some time - if it happens at all for you.

Here's the video: https://youtu.be/xVRAtCDmB6M

I've not been able to reproduce the issue with other 3'rd party VSTs or the older KORG Prophecy VST so I think the issue is particular to the 3 newer "native" VSTs.

I've so far been unable to reproduce the issue on a relative's much more powerful system (a Ryzen 7 with 16 cores), but I don't have access to it for long periods, so I don't know whether the issue may arise there over a much longer timescale, or, as it has many more cores, whether the issue would be as noticeable if it occurred compared to my 4 core system (i5-4460 on a Gigabyte H81M-DS2V motherboard).

If you do try to reproduce this could you reply to this thread with a yes/no and some idea of your system. If you can reproduce this, it'll be good to get as much information on your system as possible so that KORG can try to reproduce it and fix it.

Thanks
David Lowndes

[DavidLowndes]

A few people appear to have viewed this post, but hardly anyone has seen the linked video (judging from the YT stats of it).

Does the video link work for you?
Did my post make sense?

I'm surprised there aren't other reports of this issue from people with older (but still within the supported minimum requirements) hardware.

I've subsequently reproduced it on a similarly specified PC using Windows 10 with an i5-3470S on a Gigabyte Z77-DS3H motherboard with just the motherboard audio only.

One thing I've noticed on this machine is that Cubase's ASIO-Guard feature can often mask the end result (of audio breakup), but disabling ASIO-Guard on the opsix native VST in Cubase easily reproduces the issue.

[DavidLowndes]

And FWIW, it also reproduces for me with the latest Windows 11 (albeit an unsupported install on this hardware - even though it works fine).