Multiple SD3 Instances slowing down computer

[HARKNESS]

Hi,

I have created multiple custom SD3 Drum patches, all aprox 3.5 gigs each when loaded. I use a different drum patch for each song of my Ableton live set which means i need a separate instance of SD3 for each (17 patches/instances in total) But after i have loaded 7 or so the computers performance begins to really lag , the CPU level is at about 50% which is usually OK.

Is this a common problem or is there a lighter version of SD3 for purposes such as mine?

Are there any ways to streamline(shrink) SD3 in general to make the total gigs per patch smaller?

Any suggestions would be appreciated,

Thanks!

Superior Drummer 3 version: 3.1.4
Operating system: Windows 10

Topic

[Mac McCormick]

If it’s RAM use that you are worried about try using Cache mode. (It’s in the settings area under Performance) Using this will load only the drum samples that are being used in your project. The only caveat is that the first time through playing a song there will be a few clicks and dropouts as the samples are being loaded. But after that, the samples are in RAM and everything plays through perfectly.

Hope this helps!

-mike

Cubase Pro, Korg Kronos, M-50, Hammond XK-1c, Toontrack SD3, EZBass w/lots of expansions, many VSL Vi's, Shreddage 3 everything, and shit-tons of FX plugins.

[Mark King]

Multiple instances is bound to slow down your computer.

SD3 with older sdx,s plus Rooms of Hansa and Death & Darkness. Cubase and wavelab current versions. Roland TD50x using all trigger inputs for triggering SD3 only. Windows 11 computer. Various keyboards and outboard gear as well as VST instruments. Acoustic drums: Yamaha 9000 natural wood and Pearl masters. Various snare drums. RME BabyFace Pro FS and Adam A7X monitors

[Brooks H]

Yeah, that’s 60GB of RAM, unless I’m misunderstanding. If you don’t have that available, you’ll need to follow MT’s suggestion.

SD3 v3.3.6, EZbass v1.1.7, EZkeys v1.3.4
Studio One v5.5.2, Cubase v12.0.60
3.6GHz Intel i9 iMac, 64GB RAM, OS 12.6.1

[Scott Eshleman]

Mac McCormick wrote:

If it’s RAM use that you are worried about try using Cache mode. (It’s in the settings area under Performance) Using this will load only the drum samples that are being used in your project. The only caveat is that the first time through playing a song there will be a few clicks and dropouts as the samples are being loaded. But after that, the samples are in RAM and everything plays through perfectly.

Hope this helps!

-mike

…or ‘print’ your grooves to audio.

[Brad]

How much RAM do you have on your system. Under normal circumstances using RAM shouldn’t strain your CPU, however if it starts to get busy swapping memory in and out of storage due to a shortage of RAM that may seriously burden your system. You are playing in a live situation and activating kits within a set I assume?

Mac Studio M1 Max, RAM 64 GB, 1TB Drive, OSX 12.x/13.x and Windows 10 (VM)
DAW: Studio One Pro (always up to date)
DTX Express III (Extreme triggers), Nektar LX88
OWC Thunderbay Mini (4 X 1TB Sata SSD), Express 4M2 (4 X 2TB M.2 SSD), Envoy Express (1TB M.2 SSD)
Presonus Quantum, Faderport & Faderport 8
Black Lion Sparrow Mk2 A/D, FMR-RNP-RNC, MIDI Xpress 128, BM5A, KRK VXT4, Equator D5
2020 Macbook Pro 16GB RAM, 512GB SSD Audio(mobile rig)

• The post has been modified 2 times, last modified 5 years, 12 months ago by Brad.

[John]

Hi,

you can:

1. unload articulations in drums/cymbals you do not use, e.g. ‘Rim only’ on a Snare or Tom.
2. unload instruments you do not use; if that 4th and 5th Cymbal isn’t triggered anywhere in your song, unload it
3. restrict the Voices and Layers for instruments if you do not experience any unwanted side effects from doing so.
4. consider restraining the decay of instruments in the ‘Envelope and Offset’ property box.

BR,

John

John Rammelt - Toontrack
Technical Advisor

[HARKNESS]

Hi All ,

Thanks for the great feedback.

I have 16 gigs of RAM and Yes i am using an E Kit live that will trigger the sounds in SD3 so unfortunately i cant print the grooves to audio.

As far as the Cache mode goes would the ‘clicks and dropouts’ you mention happen on the first couple of play backs Each Time i open my project, or once only? I will give this a try later today (it’s 6:30 am here in Toronto)

So far i have unloaded all toms or cymbals not necessary per SD3 patch. Regarding unloading the articulations is that done simply by unchecking the boxes in the articulations drop down menu?

And as far as the restraining of the decay in the ‘Envelope and Offset’ property box , i had done just a little bit of that on a few toms here and there.In theory would pulling back the envelope even  slightly on EVERY drum/cymbal equate to less samples being used and therefore less RAM… if so do you suspect this would be a a significant or minimal improvement? Again , i will give this a try perhaps after seeing how things go using the Cache mode.

Thanks Again !!

Superior Drummer 3 version: 3.1.4
Operating system: Windows 10

[Brooks H]

HARKNESS wrote:

I have 16 gigs of RAM and Yes i am using an E Kit live that will trigger the sounds in SD3 so unfortunately i cant print the grooves to audio.

As far as the Cache mode goes would the ‘clicks and dropouts’ you mention happen on the first couple of play backs Each Time i open my project, or once only? I will give this a try later today (it’s 6:30 am here in Toronto)

So far i have unloaded all toms or cymbals not necessary per SD3 patch. Regarding unloading the articulations is that done simply by unchecking the boxes in the articulations drop down menu?

I would definitely recommend Cached Mode. You will only get the dropouts the very 1st time you trigger a particular sample, and it doesn’t happen every time. Most samples play fine the 1st time through from my experience (finger drumming on MPC).

Playing live, the one issue may be that your dynamics vary from warm up, adding all needed samples to RAM, to performance where you play a sample you haven’t added prior. Limiting velocity layers may help with that. If you’re playing back a pre-recorded performance, no worries about dropouts after the 1st pass.

If you’re playing the drums live, it might be safest to use ALL the other methods instead to shrink kit sizes, if you can get all 17 kits under 16GBs total, which should be possible. Then you won’t have to worry about the dropouts.

 

SD3 v3.3.6, EZbass v1.1.7, EZkeys v1.3.4
Studio One v5.5.2, Cubase v12.0.60
3.6GHz Intel i9 iMac, 64GB RAM, OS 12.6.1

[Madsen]

You could also just have two instances running, which will load the current and next kit. Don’t know exactly this should be programmed, but I think it would be possible.

[HARKNESS]

Thanks for the more detailed run down of the Cache idea, that was very clear and helpful.

I hadn’t thought of the ‘just 2 instances concept’ , that sounds particularly promising if it can work!

does anyone know how to automate drum patch changes within SD3 via Ableton Live?

(maybe this should be started as a whole new thread…)

Superior Drummer 3 version: 3.1.4
Operating system: Windows 10

[HARKNESS]

One last question re the multiple instances.

My laptop has 16 gigs of RAM but can handle up to 64gigs. Would installing maximum RAM be an immediate fix or is it not that straightforward?(i.e. with 16 gigs i can load 7 patches comfortably, with 64 gigs should I easily be able to load the other 10 patches?)

Superior Drummer 3 version: 3.1.4
Operating system: Windows 10

[Brooks H]

HARKNESS wrote:

One last question re the multiple instances.

My laptop has 16 gigs of RAM but can handle up to 64gigs. Would installing maximum RAM be an immediate fix or is it not that straightforward?(i.e. with 16 gigs i can load 7 patches comfortably, with 64 gigs should I easily be able to load the other 10 patches?)

Superior Drummer 3 version: 3.1.4
Operating system: Windows 10

Yes, that straight forward. There may be a bit of RAM used by other things, but if the kits total say 60GB, you should be good to go with 64GB.

IMO, it’s always good to max RAM on a music CPU using virtual instruments.

SD3 v3.3.6, EZbass v1.1.7, EZkeys v1.3.4
Studio One v5.5.2, Cubase v12.0.60
3.6GHz Intel i9 iMac, 64GB RAM, OS 12.6.1

[Brad]

Not sure if this link helps, I don’t use Ableton Live so I found it insightful.

https://forum.ableton.com/viewtopic.php?f=4&t=184758

Mac Studio M1 Max, RAM 64 GB, 1TB Drive, OSX 12.x/13.x and Windows 10 (VM)
DAW: Studio One Pro (always up to date)
DTX Express III (Extreme triggers), Nektar LX88
OWC Thunderbay Mini (4 X 1TB Sata SSD), Express 4M2 (4 X 2TB M.2 SSD), Envoy Express (1TB M.2 SSD)
Presonus Quantum, Faderport & Faderport 8
Black Lion Sparrow Mk2 A/D, FMR-RNP-RNC, MIDI Xpress 128, BM5A, KRK VXT4, Equator D5
2020 Macbook Pro 16GB RAM, 512GB SSD Audio(mobile rig)

[John]

Oh, and don’t forget to check if you are loading unnecessary bleed in one of the microphones.

John Rammelt - Toontrack
Technical Advisor

• This post was modified 5 years, 12 months ago by John.

[HARKNESS]

Awesome Thank You Very Much !

I’m gonna max out on Ram and hope for the best(i will do the ‘Bleed’ thing too)

[Author]

Replies