CPU Glitch Bug (CPU goes crazy for no reason then goes back to normal)

[rickpress]

Has anyone had a bug with Waveform before where the CPU can suddenly go really high in terms of CPU usage for no reason and then reset again to a more normal level? I have no idea what's causing this. Even just using one instance of Subtractive on a track can cause this.

No idea why this happens.

[nowgad]

Don't know if it looks like it or not, but I never get high CPU usage when using TW (Processor 2015 release), according to Win10 Task Manager. On the other hand, the load inside the DAW, according to CPU usage, can be very high for no reason - the same project either works normally, or with a high load. With such fluctuations, in most cases, I deal with clearing the RAM, and clearing the C drive of temporary files, where TW is installed, before starting the DAW.
And if anyone is interested, then by enabling the Shadow Defender sandbox on the disk on which TW is installed, you can reduce the load by 10-15%. But, you will have to tinker with the settings, since all project files, preset save folders, Racks, and even better plugins (or folders with saving presets), etc., need to be transferred to any other disk (without Shadow Defender protection) so that the changes are saved at the end of the session.

[UnionS8]

Has anyone had a bug with Waveform before where the CPU can suddenly go really high in terms of CPU usage for no reason and then reset again to a more normal level? I have no idea what's causing this. Even just using one instance of Subtractive on a track can cause this.

No idea why this happens.

Is it really Waveform related? I experienced CPU spikes with my two previous computers, and it was always connected to IRQs and bad drivers (mainly nVidia). And it affected all my DAWs.

[eliasfuentesc]

This might be unrelated to your issue, but I recently learned that Waveform does a full render of your edit every time you close it (in order to update the “preview”), and that bumps the CPU usage drastically. You can cancel the render by opening the “Background tasks” flyout on the top-right area of the program. You may also find other background tasks (that could be the culprit) in there.

[dysjoint]

You can turn the preview off in settings. I actually love that feature, every time I open Waveform I can have a quick listen to see where I'm up to with each project.

On the cpu issue, it could be Windows background tasks?? I get glitches and it's definitely not processor power, haven't nailed down a cause yet.

[rickpress]

Same as what happens on Linux Waveform.

I've created a simple edit. And it maxes cpu. I copied and pasted the same clips and set up the same edit in another tab and then it runs fine. This is a clear bug. Although there is no video you can see in the video.

I've emailed Tracktion about this. Last time I mailed them they replied (wasn't about this) so will see but this is a crazy bug. I've terminated all the background processes like Antivirus etc. No idea why it's happening. No reason an edit should need to be moved to a new edit for it to run properly. I've also shown them the performance in Mixcraft Pro Studio 10 (runs fine) whereas Waveform doesn't. In FL studio I am getting about 50% for cpu meter as well - actually a bit better maybe 45% in FL bfor the same simple edit or start of an edit.

It's quite ridiculous and made using Waveform on Linux when it happens virtually unusable other than creating an edit then creating another edit. Had same problems in Ubuntu 22.04 / 22.10 / 23.04 and Ubuntu Studio 23.04 so swithed to Windows and lost patience with Waveform so ended up upgrading Mixcraft and will stick with that until the devs make Waveform more stable.

Also found a weird clip bug where duplicating a clip between projects when you move the clip the midi data goes missing but when returned to the same spot will show.

Getting really tired of the bugs in Waveform.

I want to use this DAW primarily but guess it will be Mixcraft going forward until they fix these silly bugs.