Insane CPU usage
Superior Drummer 3 Pre-sales
-
First of all, I realize this is a presale forum...
First of all, I realize this is a presale forum but I guess Toontrack doesn’t like having an actual support form even though this software costs over $500 (Canadian).
On my brand new iMac, 27″, 5k, 4.0ghz i7, 8gb ram, 512 internal SSD, external sample SSD (256gb) not loaded with EVERY sample library, just the basic ones. Running a MOTU 8pre USB interface at 44.1khz.
ANY time I insert SD3 into a project the CPU usage spikes to over 300%, then up to 600%+ when I open the SD3 GUI.
Blank project or a barely even started mix of a project (torpedo wall of sound on about 10 tracks and that is NOT a CPU hog by any means).
Even running in stand alone mode it goes over 300% easily. I have tried running a kit with a SINGLE drum on it and the results are the exact same.This is totally ridiculous, this Mac is literally less than a week old so this is NOT a hardware issue.
Any time I open a project with SD3 inserted already it runs with a few clicks and pops around 150% cpu usage, then when I open the SD3 GUI one cpu core spikes and the hardware monitor built into OSX reports an excess of 300% cpu usage instantly then I get nothing but clicks and pops. I can run my projects at 1024 samples with less clicks and pops but I’d rather not because that is just insane that I would need to do that and there are still clicks and pops.
On top of the clicks and pops I also get errors regarding the audio and midi syncing at weird sample rates.Apparently telling SD3 I am using an SSD in it’s settings is broken as that makes the issue even worse. Cache mode or 16bit mode yield even more digital noise and pops and clicks.
I would like to know how I go about getting a refund for this, or if there is a fix for this issue.
I am currently downloading my copy of SD2 to use instead, since my band mate can run that on his 12 year old MacBook with zero issues.
Please don’t try to tell me this is a hardware issue because it simply is not, unless the recommended system requirements are beyond wrong.I’ve attached a couple images of this.
First of all, I realize this is a presale forum but I guess Toontrack doesn’t like having an actual support form even though this software costs over $500 (Canadian).
On my brand new iMac, 27″, 5k, 4.0ghz i7, 8gb ram, 512 internal SSD, external sample SSD (256gb) not loaded with EVERY sample library, just the basic ones. Running a MOTU 8pre USB interface at 44.1khz.
ANY time I insert SD3 into a project the CPU usage spikes to over 300%, then up to 600%+ when I open the SD3 GUI.
Blank project or a barely even started mix of a project (torpedo wall of sound on about 10 tracks and that is NOT a CPU hog by any means).
Even running in stand alone mode it goes over 300% easily. I have tried running a kit with a SINGLE drum on it and the results are the exact same.This is totally ridiculous, this Mac is literally less than a week old so this is NOT a hardware issue.
Any time I open a project with SD3 inserted already it runs with a few clicks and pops around 150% cpu usage, then when I open the SD3 GUI one cpu core spikes and the hardware monitor built into OSX reports an excess of 300% cpu usage instantly then I get nothing but clicks and pops. I can run my projects at 1024 samples with less clicks and pops but I’d rather not because that is just insane that I would need to do that and there are still clicks and pops.
On top of the clicks and pops I also get errors regarding the audio and midi syncing at weird sample rates.Apparently telling SD3 I am using an SSD in it’s settings is broken as that makes the issue even worse. Cache mode or 16bit mode yield even more digital noise and pops and clicks.
I would like to know how I go about getting a refund for this, or if there is a fix for this issue.
I am currently downloading my copy of SD2 to use instead, since my band mate can run that on his 12 year old MacBook with zero issues.
Please don’t try to tell me this is a hardware issue because it simply is not, unless the recommended system requirements are beyond wrong.I’ve attached a couple images of this.
