Noise issue w/ Superior Drummer

[DoYouLikeHam]

How might I figure out how/why I’m having this noise issue… please listen to linked WAV created from SD3 as Ableton Live plug-in.  I didn’t readily notice any sound meters peaking.

https://drive.google.com/file/d/1b2JxfJMv9rn_FBMyY3ZOGWAQzWOfx3SW/view?usp=sharing

Thanks!

Superior Drummer 3 version: 3.3.3
Operating system: macOS Big Sur (11)

• This post was modified 2 years, 9 months ago by DoYouLikeHam.

Topic

[DoYouLikeHam]

I have the same issue when playing SD3 in Standalone Mode.

Here’s another file created from an ‘out of the box’ groove, bounced from directly in SD3:

https://drive.google.com/file/d/1YIdLyqZjlxqYoXuPUoAQ8jhqVeeYTMmG/view?usp=sharing

• The post has been modified 3 times, last modified 2 years, 9 months ago by DoYouLikeHam.

[Ken]

Good evening gentlemen.

In standalone mode, you must select an audio device.
The screen will show you your output latency, buffer latency and sample rate. I use ASIO as device type.

If you go to the driver settings of the device that you select and play SD with, the ASIO buffer size should be displayed in samples. There may also be choices of low latency mode, etc.

I am currently running at 128 samples, in low latency mode on my audio device. I have no issues and that gives me an output and latency of 5.8 ms with a buffer latency of 2.9 ms at a sample rate of 44100 Hz. As reported by SD3.

If I drop my audio device to 64 samples I will have problems with exactly what you are describing.

if I drop my audio device to 64 samples I will have problems with exactly what you are describing.

I hope this helps

cheers Ken

Superior Drummer 3 version: 3.3.3
Operating system: Windows 10

Cheers Ken
SD 3.3.6 on Windows 10 | Cubase 11 Pro DAW
expansions : N.Y.Avitar | Latin percussion
Yamaha multi 12 | DTX 450k | Trigger IO (x2)
Super stupid fast computer with i9 and 18 speed double clutch gearbox
5. Audio interfaces.

1

Thanked by: GWANG-HO BANG

[DoYouLikeHam]

Hi @Ken S, thanks for the consideration– I’m on a Mac… I tried all buffer rates from 64 to 2048 and the issue persists.  I also tried changing my sample rate from 48k to 44.1k, and still have the issue.  This happens regardless of what I am using as my output device: Scarlett 18i20, MacBook speakers, TD-50X, etc…

Superior Drummer 3 version: 3.3.3
Operating system: macOS Big Sur (11)

[DoYouLikeHam]

Hmmm.. I wonder if this effect is designed/ expected… I seemingly had the bad luck of picking a preset that has this issue… others don’t readily exhibit it.

I was the ‘Broken Ayotte’ preset… I noticed if I mute, or just reduce the level, of the “Amb Ribbon” track, the offending sound goes away.

Superior Drummer 3 version: 3.3.3
Operating system: macOS Big Sur (11)

[DoYouLikeHam]

Here’s another thread of someone complaining of the same problem w/ the same preset:

https://www.vdrums.com/forum/advanced/vst-samples/1262070-static-on-certain-drums-in-superior-drummer-3

Superior Drummer 3 version: 3.3.3
Operating system: macOS Big Sur (11)

[drumjack52]

What exactly should I be listening for? High pitched? Low pitched? What? Listening on high quality Adam cans and JBL LSR308 monitors.

Superior Drummer 3 version: 3.3.3
Operating system: macOS High Sierra (10.13)

Jack
aka musicman691 on other forums
Superior Drummer 3.4.0
Area 33 1.0.0
Death and Darkness 1.0.1
PT 2021.6
OSX 10.13.6
3.46 GHz hex core 2012 MacPro 48 gig ram

[Damian Blunt]

BEST ANSWER

The Amb Ribbon mic channel is routed to an ambience bus with a high amount of bit reduction. The sound is intended.

Damian Blunt - Toontrack
Quality Assurance
Betatesting

[DoYouLikeHam]

Thx, Damian– I was just reading about the “Punch Exciter 180” and wondering how that related to your comment of Bitcrushing… I hadn’t noticed the separate routing.

I’m very new to SD, and relatively novice to this signal routing.. so learning as I go…

For others that may run into the same question.. here’s a visual:

Superior Drummer 3 version: 3.3.3
Operating system: macOS Big Sur (11)

1

Thanked by: Damian Blunt

[MikeMcN]

I was hearing the same thing using a MacBook Pro with M1. It happened whenever I selected more than 1 CPU core in settings. Changing it back to 1 core fixed it.

Operating system: macOS Monterey (12)

[Author]

Replies