CPU Usage Issues (Leak?)

[Tyne]

G'day

When mixing a 26 track project (a quarter of the tracks/plugs I've flogged Cakewalk with in the past) I've run into an issue. Running my new project template (with around 80 tracks pre setup with plugins ALL SWITCHED OFF except Master Bus plugs), I loaded everything in, got to work, and about half way through noticed glitches, dropouts, and unexpected clipping, so I checked CPU usage. Internal load was as expected, but CPU usage in the system was pinned. Adjusted interface buffersize in increments up to the maximum 2048 samples. Issue remained (I can generally mix large projects at 256 - 512 samples without an issue)

Rig Specs:
Ryzen 5600x @ 3.7 Base, Max 4.8GHz

CMW32GX4ME3200C16 32GB @ 3266MHz CL16

Asus B550M-K  Board

Geforce 1060 3GB (Custom OC)

970 Evo Plus NVMe Drive

Windows 10 Pro 64bit

Tascam US2x2HR Interface.

Generally Cakewalk isn't that resource hungry. I began to freeze tracks, which sometimes failed to freeze entirely, Restarted the project, same issue. Restarted Cakewalk, same issue. Restarted computer, same issue. I went so far as to switch off all plugins, remove all plugins, and further delete all audio from the project. After closing the project but leaving Cakewalk open, the issue remained. I have attached photos with the project open, the project closed, and my 'idle' cpu useage after closing Cakewalk. The spikes are from opening Snipping tool.

 

It seems as if Cakewalk is:
A: Still utilizing CPU when plugins are switched off/FX rack is off.

B: Still utilizing CPU when the project is closed.

 

The issue potentially pertains to UAD's new Spark plugins, of which I have a few in my project template, however, theoretically, the system should only react when those plugins are switched on. As mentioned above removing the plugins one by one failed to reveal any culprits, leading me to suspect the issue is perhaps a Cakewalk setting.

And yes, background processes were checked, Cakewalk was the CPU hog. In addition the usage was cross checked with OCCT.

Any information is greatly appreciated, please let me know if you wish me to supply any other details.

 

 

 

 

Edited March 15, 2023 by Tyne

[John Vere]

What I think I’d do is make a save as copy of the project and start deleting plug ins with an eye on the CPU meters. I think bypassing doesn’t unload them. 

[57Gregy]

11 hours ago, Tyne said:

And yes, background processes were checked,

I have read in these forums that that is no longer necessary and may have never been necessary. 

[Tyne]

7 hours ago, 57Gregy said:

I have read in these forums that that is no longer necessary and may have never been necessary. 

Unless it's Chrome. It's always Chrome.

9 hours ago, John Vere said:

What I think I’d do is make a save as copy of the project and start deleting plug ins with an eye on the CPU meters. I think bypassing doesn’t unload them. 

Did that. Cleared the whole project, deleting audio, every plugin, and switching off all Prochannels. Empty project, basically. Issue continued.

It seems as if something is leaking processing cycles once it's loaded. Reminds me of old school browser memory leaks where deleting all the tabs didn't stop Firefox chewing up 4 gigs of RAM back in the day, only restarting the program fixed it. Except this time it's CPU processes.

Is there any way to unload the plugin by bypassing it in the FX chain? Every plugin basically these days has a bypass button built in, I'd rather be able to unload the plugin with Cakewalk, and bypass internally for comparison.

 

I understand I'm pushing my hardware hard, a 5600X and basic Tascam ASIO interface aren't exactly processing gods. But I have flogged this program before with huge projects (120 channels) and loads of Plugs (Mostly Waves/Soundspot/Sonarworks, perhaps up to 80 plugs), especially back when I was a more amateur producer, line by line editing rather than AUX/Bussing stuff. These projects were also completed on a 4790K with a monster overclock on it. Seems weird to have these issues after the upgrade, unless UAD's Spark plugs simply are so resource hungry and/or bugged that they oblitorate the chip.

Edited March 16, 2023 by Tyne

[billp]

@TyneApparently you are not alone:

https://uadforum.com/community/index.php?threads/cpu-usage-skyrockets-after-latest-spark-update.61058/

 

[Tyne]

1 hour ago, billp said:

@TyneApparently you are not alone:

https://uadforum.com/community/index.php?threads/cpu-usage-skyrockets-after-latest-spark-update.61058/

 

Indeed, a very similar issue. Glad to know it's UAD's problem and not Cakewalk. Greatly appreciate you finding that, I had done some initial searching but was pressed for time to dig deeper.

 

As fate would have it, an update is available for UADx Extension as well as all plugins, with the release of the Fairchilds. I had thought I was up to date with the post Febuary patch that fixed this issue, as I do recall having updated UAD very recently (in the last three weeks). I must have just missed it by a few days and not checked again. Kinda wish the plugs would prompt an update, rather than having to open UA Connect all the time.

 

Installing updates now, will report back with findings.

 

EDIT: Issue seems to be resolved. Will monitor over the coming weeks but, the same project as above is now running around the 30 - 40% CPU useage that I would expect with 33 plugs loaded, 14 of which are UAD. Greatly appreciate everyones help. Will bump this thread if the issue reoccurs.

Still curious about if there is an option to unload plugs by cycling them on and off however as mentioned above. If not, does anyone know if that's a feature Cakewalk is considering? Will post it in the feature requests if so.

Edited March 16, 2023 by Tyne