No products in the cart.
I have no idea why but when I play while using SD3 all the audio is crackling and glitching out. I don’t really know what the problem is, my Mac should be able to handle the program no problem. If anyone has any suggestions I’d appreciate it
Buffer size is usually the culprit. What interface are you running through? And does changing the buffer have an impact?
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)
I have been having the same issue and I’m on a PC. Try changing the block size within the DAW. This hasn’t completely taken the popping away for me but it has been drastically reduced. Currently, I’m set to 256. 128 pops, 512 pops. For me, popping / clicking only happens with my Toontrack software (SD3, EZBass, EZkeys) so I am now looking into my toontrack settings. No luck so far though. I hope changing the block size works for you.
This is definitely a computer issue. Have you tried a latency checker to make sure nothing on your pc is causing the problem?
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
Try opening up SD3 software outside of your DAW. Under ‘Settings’ open up ‘Audio/Midi Setup’, change the buffer size to 1024. Apply and close. Then open up your DAW and give it a test. This solved the issue for me. Hopefully it does for you too.
NOTE: My sample/buffer within my DAW is set to 256 but I’ve changed it up / down and the popping / clicking is gone.
Good luck.
1
Thanked by: marius.v.rus@gmail.comAlso probably need a bit more information on the specifications of your computer. I run my i9 with buffers at 64 which allows real time playing from my edrums. Those buffer sizes you are using are very high so it’s either a low spec computer or it has a bottle neck somewhere.
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
I had the same problems.
The game changer was the cache mode in the performance tab.
Change the setting to “force cache mode”.
In my case this led to a significant lower use of RAM. Only disadvantage – as far as I can assess – is, that the first time a new drum is played, the sound is not yet the one it should be, because SD3 has first to load it into the cache.
Hope this helps, good luck!
(EDIT- This quit working, was only a temporary fix)
Just had this issue for the first time in FL Studio 21. I went into SD3 > Settings Tab > Performance > CPU Cores > 1 (Dropdown Menu) > (Changed from 1 to 8)
This solved my issue, depending on your CPU the core number may be different. This also may not solve your problem, if your project is already CPU intensive. Potentially you could save a copy, delete all instruments except drums, do my fix, and finally bounce drum tracks out. Or bounce everything BUT drums INTO the track with SD3.
Try opening up SD3 software outside of your DAW. Under ‘Settings’ open up ‘Audio/Midi Setup’, change the buffer size to 1024. Apply and close. Then open up your DAW and give it a test. This solved the issue for me. Hopefully it does for you too.
NOTE: My sample/buffer within my DAW is set to 256 but I’ve changed it up / down and the popping / clicking is gone.
Good luck.
Out of curiosity, what prompted you to try this approach? It wouldn’t seem that the buffer setting in the standalone app should have any bearing on the performance of the VST. Does it continue to solve you issue, these many months later?
I am running SD3 on a M1Max w/ 64GB ram and I still get pops at anything 128 or below. This is frustrating, as the laptop was purpose spec’d for running VSTs live. I can’t see any reason that a machine with that much power shouldn’t be able to run SD3 glitch free. It takes less than 2 seconds to load a 4000MB kit, but the performance is still spotty.
Try opening up SD3 software outside of your DAW. Under ‘Settings’ open up ‘Audio/Midi Setup’, change the buffer size to 1024. Apply and close. Then open up your DAW and give it a test. This solved the issue for me. Hopefully it does for you too.
NOTE: My sample/buffer within my DAW is set to 256 but I’ve changed it up / down and the popping / clicking is gone.
Good luck.
Out of curiosity, what prompted you to try this approach? It wouldn’t seem that the buffer setting in the standalone app should have any bearing on the performance of the VST. Does it continue to solve you issue, these many months later?
I am running SD3 on a M1Max w/ 64GB ram and I still get pops at anything 128 or below. This is frustrating, as the laptop was purpose spec’d for running VSTs live. I can’t see any reason that a machine with that much power shouldn’t be able to run SD3 glitch free. It takes less than 2 seconds to load a 4000MB kit, but the performance is still spotty.
Superior Drummer 3 version: 3.3.5
Operating system: macOS Monterey (12)
Hi there,
I am running the exact host, both from Monterey on the internal drive and Ventura booting from an external NVme m.2 drive.
Are you experiencing problems from within a DAW? If so, which one and version?
Audio interface type and model as well.
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)
So I am having the same issues, mind you I don’t have any issues running EZD3 in standalone or as a plug-in in Logic. With SD3 I am having pops, crackling, and dropped sound consistently. I have played with the buffer at 32, 64, 128 and 256 and nothing fixes it.
It has happened with last interface a Presonus mixer and it is now happening with an Apollo x8. I am ready to sell SD3 and just use EZD3…
I have been running SD3 with an Apollo (in Logic) on various Macs since 2017 without any issues.
What are the specs of your computer? As well if you are using any expansions which ones?
jord
Hi Jord,
Thanks for your response. I am on MacBook Pro M1 16”. I was having the problems running Ventura MacOS. I decided to upgrade to Sonoma to be able to also upgrade Logic to see if it solved the problem and it didn’t.
My last ditch effort was to uninstall SD3 and redownload and reinstall after updating my OS and that seems to have fixed it. I was only able to play my E-Kit for a couple of minutes.
I’m gonna give it a stress test tomorrow. I am just surprised that EZD3 has never had that problem but SD3 has it regardless of MacOS version installed.
Hi,
please review the Settings > Performance tab. What are your settings there?
BR,
John
John Rammelt - Toontrack
Technical Advisor
Hi John,
Thanks for your reply. My performance setting is at one (1) Core. I had it at 8 cores originally but eventually realized in order to run SD3 in Logic it needed to be set one core. I also run it at one core in Standalone mode.
Well, started my testing of SD3 with Logic Pro X and same issues with drop sounds and crackling/distortion. I tried SD3 in Standalone and didn’t have any issues but could only play for an hour before I had to head to work.
For giggles I tried EZD3 with Logic Pro X and no issues. I guess the combination of SD3 and Logic Pro X is just not working for me.
To rule out Logic Pro X as the culprit I am going to install Protools and run SD3 and see how it goes….
I am running a MacBook Pro M1 16″ 16GB of RAM and SD3 Libraries on an external USB-C Samsung S7 SSD Drive. MacOS is Sonoma latest version. Running latest version of SD3 and several SDXs.
No products in the cart.