[lightbox]

Scott wrote:

It’s been reported to the programmers and they are looking into the fix to be included in an update.

Now that was a quick fix even though it turned out to only be a cosmetic issue 🙂 Thanks a lot!

1

Thanked by: Scott

[lightbox]

Scott wrote:

It’s been reported to the programmers and they are looking into the fix to be included in an update.

Thanks Scott for confirming this. I also received the mail regarding my support ticket.

Cheers
Martin

[lightbox]

Ok, I did some further investigation monitoring the actual RAM Usage vs. the RAM Usage display in SD3. Looks like it’s a bug in the Windows version of SD3 because the actual RAM Usage grows beyond 16384MB but SD3 seems to have a threshold in the RAM Usage display where RAM beyond 16GB isn’t just added but counted from zero.

[lightbox]

Whagi wrote:

… like you say it could be a Windows issue …

I meant “an issue with the Windows version of SD3”.
I do some pretty heavy lifting on both workstations, not only audio production but also quite a bit of video post production. No issues.

[lightbox]

Then it looks like a Windows specific issue.

I’ve already tried on 2 studio workstations (Win10 Pro, one with 64GB RAM, the other one with 80GB RAM).
Loading until 16384MB … then poooof. 🙁

Have opened a support ticket earlier today, still no answer. Let’s see.

[lightbox]

Brad wrote:

Are you working on these presets within SD3 as a plugin within Cubase? Does the same thing happen when you run SD3 standalone?

Happens with both, Cubase plugin and standalone software.

As mentioned in the first post, I’m on Windows 10 Pro with 64GB RAM in my workstation.

[lightbox]

The RAM usage indication in the top right of SD3 rises while loading a rig with All Bleed enabled on all microphones.

Once it reaches 16384MB (16GB) it suddenly drops down and loads again, for example to only 2870MB RAM Usage. No error message.

 

PS: I’m not having problems with factory presets. I’m making my own presets with All Bleed active on all microphones … and I route all microphones individually and raw to individual outputs because I want to mix the drums in Cubase, not in the SD3 mixer.

• This post was modified 4 years, 9 months ago by lightbox.

[lightbox]

Stefan Branberg wrote:

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)?

I’ve had massive issues with CPU spikes on a Windows 10 system running Cubase 10 Pro. Selecting or unselecting an SD3 track makes a HUGE difference! I went through all tips and tricks for optimizing my system for pro audio that can be found on the internet, without success, until …

I read somewhere that Intel Turbo Boost Max Technology could cause issues as well, so I deinstalled the software and deactivated Intel Turbo Boost and EIST in the BIOS. Only after doing this, I could (finally) start using SD3 again on my new workstation (X299, Intel i9 7900, 64GB RAM, 2TB Samsung M.2 NVME).

I still see some spikes in VST Performance when an SD3 track is selected but at least it doesn’t max out and I don’t get dropouts anymore.

Superior Drummer is the only VSTi that seems to have these performance issues and I wish, Toontrack could come up with an update that fixes these problems!

[Author]

Replies