Chris Wickens
Participant
Topics Started: 1
Replies Created: 5
Has Thanked: 0
Been Thanked: 0
@Stefan said:
Hi! Thank you guys for reporting your issues. I notice in your screenshots that you both have the channel that has superior 3 on it selected in Logic. If you unselect it, does the issues go away (or get any better at all)? When selecting a channel in Logic it goes into “Live Input Mode” and forces all rendering of that channel to the last thread, that might already be used for other stuff (https://support.apple.com/en-us/HT201838). Maybe you have already tried this, but I figured that I would check with you at least. On my macbook pro it makes a lot of difference (I know that it’s a bit of a hassle keeping track of what channel that you have selected but Apple does write “It’s a good idea to keep a track that uses an Audio channel strip selected in the Arrange window, unless you’re actively playing or recording to a Software Instrument”).You might also try to change the number of CPU cores used by superior, using only one core seems to work better for me with Logic’s “Live Input Mode”.
The CPU load when loading the “Djent Style”-preset that is loading in the screenshot that uses standalone will be very high while loading the sounds, and that does take some time on that one, but after that is done it should calm down.
Well after reinstalling and leaving every setting alone, de-selecting the SD3 track seems to clear any problems up.
Thanks for the help!
@Stefan said:
Hi! Thank you guys for reporting your issues. I notice in your screenshots that you both have the channel that has superior 3 on it selected in Logic. If you unselect it, does the issues go away (or get any better at all)? When selecting a channel in Logic it goes into “Live Input Mode” and forces all rendering of that channel to the last thread, that might already be used for other stuff (https://support.apple.com/en-us/HT201838). Maybe you have already tried this, but I figured that I would check with you at least. On my macbook pro it makes a lot of difference (I know that it’s a bit of a hassle keeping track of what channel that you have selected but Apple does write “It’s a good idea to keep a track that uses an Audio channel strip selected in the Arrange window, unless you’re actively playing or recording to a Software Instrument”).You might also try to change the number of CPU cores used by superior, using only one core seems to work better for me with Logic’s “Live Input Mode”.
The CPU load when loading the “Djent Style”-preset that is loading in the screenshot that uses standalone will be very high while loading the sounds, and that does take some time on that one, but after that is done it should calm down.
I had to uninstall SD3 to use my band mates account copy of SD2, but I will reinstall it tonight and see if this helps. Thanks for the suggestions!
@Henrik said:
I read your post but while I tried to see if I could get Superior to behave like it does for you on my 6 years old Macbook, I forgot that you had tried higher buffer sizes… You seem to have the view of us as trying to rip you off, which we don’t. If we didn’t have happy customers we wouldn’t survive, so we will help you!
– 16 bit mode will actually increase the CPU load since the samples will be recalculated from their original bit rate.
– Have you tried to increase the nr of CPU cores in Settings/Performance?
– What is the load of your CPU when you load the Default preset in standalone, using the built in audio interface? I would like to compare the CPU load to my Mac to see what difference we have in a similar scenario…
I’ve tried increasing the cores in logic and in sd3 with no different results, using auto or user defined core count. Constant spiking on one cpu core no matter what.
The cpu usage is no different with the default kit. It has high CPU usage immediately and the CPU spikes even worse as soon as I open the GUI. Stand alone is spiking immediately.
Using my interface or the built in audio has the same results.
@Henrik said:
Are you using any external MIDI devices to play Superior Drummer 3 in real time (e-drums, keyboard etc)? If not, I suggest that you increase the buffer size and see how that works out. When I mix my songs I use something like 1024 buffer size, since the latency isn’t a problem in that scenario, and the CPU load is decreased…Superior Drummer 3 is using slightly more CPU than SD2, but it shouldn’t be nowhere near several 100% of your computers CPU – if nothing drastic is going on (say you are using 100 EQ plugins and have them all opened, or similar)… Note that the CPU usage will increase while the Library and Drums and Mixer Presets are loading (as it is in your first screenshot). The CPU usage should decrease when it has finished the loading.
“First of all, I realize this is a pre sale forum but I guess Toontrack doesn’t like having an actual support form…” – there is a Superior Drummer 3 help forum at https://www.toontrack.com/forum/superior-drummer-3-support. Can’t you access that?
I am sorry that you are having these problems, but I assure you that we will try to help you to fix these issues!
Access denied to that forum. I have zero midi devices connected, this is being programmed from midi tracks created on a track.
I know that this software takes some time to load samples but as I said this happens even with only a single drum being used.
Buffer size makes no difference, I guess you didn’t even read my post just glanced at it.
What is the process to get my money back?
Brad, this software recommends 8gb. My ram usage is not an issue.
You’re not alone, after spending this much on a piece of software I expect them to have some sort of support forum.
I guess they only care if you’re about to buy it, after that you’re on your own!
No products in the cart.
Get all the latest on new releases,
updates and offers directly to your inbox.
Note: By clicking the 'I WANT IN' button, you will not be creating a Toontrack user account. You will only sign up to get our newsletters, offers and promotions to your inbox. You can unsubscribe at any time from a link at the bottom of each email. If you want to learn more about our privacy policy, please find detailed information here.