No products in the cart.
I know this is a topic of VSTs that is as old as time, but I’m truly stumped and looking for thoughts.
I have a 2021 M1Max MacBook Pro with 64 GB RAM. One of the reasons I forked over the extra cash was because I wanted this machine to be able to handle anything I could throw at it with “live” VST performances. The loading times are incredible; all of my Toontrack libraries are on the local SSD and force cached mode is off. I can load even the largest kits with all articulations in just a couple of seconds; it’s fantastic.
For months I have finally been able to enjoy “real-time” performance with e drums, routinely running my buffer size as low as 32 samples in a host like Gig Performer. I’ve been using the Behringer Wing console as my studio interface. I have had zero complaints since I got the laptop about this time last year.
Suddenly, and without warning, annoying little audio clicks have begun to appear. For reference, most of my testing over the last couple of days has been with the “Cross stick One” preset front the core SD3 library. Nice big open kick with room ambience. I especially notice the clicks when I perform quick double strokes on the kick. I am running into an IConnectivity Mio XM interface through a Pearl Mimic module. The Mimic sounds great but doesn’t compare to SD3 in flexibility and ease of use.
At first I thought it was maybe a USB bus problem. I switched cables. Same. I switched ports. Same. Ran the VST in Studio One, Ableton, Gig Performer. Same, same, same. Then I bypassed the Wing completely. Opened SD3 standalone, monitored through headphones plugged directly into the 1/8” output on the laptop. Same result.
The question is why? Nothing has changed, except maybe a required SD3 update when I bought Hitmaker SDX recently. Just wondering if anyone has any thoughts or ideas beyond the old “raise your buffer” when my machine has proven over time that it can handle SD3 at 32, or at worst, 64. For information, I’m now hearing clicks up to 256 samples. Other thoughts?
Thanks in advance.
I know this is a topic of VSTs that is as old as time, but I’m truly stumped and looking for thoughts.
I have a 2021 M1Max MacBook Pro with 64 GB RAM. One of the reasons I forked over the extra cash was because I wanted this machine to be able to handle anything I could throw at it with “live” VST performances. The loading times are incredible; all of my Toontrack libraries are on the local SSD and force cached mode is off. I can load even the largest kits with all articulations in just a couple of seconds; it’s fantastic.
For months I have finally been able to enjoy “real-time” performance with e drums, routinely running my buffer size as low as 32 samples in a host like Gig Performer. I’ve been using the Behringer Wing console as my studio interface. I have had zero complaints since I got the laptop about this time last year.
Suddenly, and without warning, annoying little audio clicks have begun to appear. For reference, most of my testing over the last couple of days has been with the “Cross stick One” preset front the core SD3 library. Nice big open kick with room ambience. I especially notice the clicks when I perform quick double strokes on the kick. I am running into an IConnectivity Mio XM interface through a Pearl Mimic module. The Mimic sounds great but doesn’t compare to SD3 in flexibility and ease of use.
At first I thought it was maybe a USB bus problem. I switched cables. Same. I switched ports. Same. Ran the VST in Studio One, Ableton, Gig Performer. Same, same, same. Then I bypassed the Wing completely. Opened SD3 standalone, monitored through headphones plugged directly into the 1/8” output on the laptop. Same result.
The question is why? Nothing has changed, except maybe a required SD3 update when I bought Hitmaker SDX recently. Just wondering if anyone has any thoughts or ideas beyond the old “raise your buffer” when my machine has proven over time that it can handle SD3 at 32, or at worst, 64. For information, I’m now hearing clicks up to 256 samples. Other thoughts?
Thanks in advance.
Any software updates to your machine?
I am running five monitors on my system. Monitors usually do not interfere with audio interfaces, If they have built in speakers, then usually windows will try and reset them as the default, audio interface for the Windows audio system, I had to go into my audio system and disable every monitor that had audio capabilities. and this is only for the operating system not your DAW/SD3 audio.
The ASIO buffer size is usually what causes these kind of drop outs. Now, for that setting to be changed at random is rare! I personally have never seen that happen on any machine that I have owned since 1988. Now you’re running on a laptop, which are not all that powerful in the computing game. That’s why I’m asking if you got software updates specifically operating system updates. Both windows and Apple have a habit of adding shit in the background to their new latest version updates. And this, of course will impact CPU processing time etc. etc. etc..
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.
I just noticed that SD3 is now at version 3.36. what version are you at on SD3
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.
FYI
found no bugs so far
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.
All, in case my edited post got buried and passed over, it seemed to be a sample rate collision. Once I dropped my Wing console down to 44Khz from 48, pops disappeared. I still don’t full understand the why if it, as I thought SD3 playback was 48/24. Either way, thrilled to have a clean triggering experience again.
I have read much of this post but not all of it. So forgive me if I missed something.
Your last post about switching to 441k made me think of something: EZX samples are 16 bit 441K. So if you’re using an EZX for the drum samples I think that even in SD3 they are going to play at 16/441.
Somebody may correct me on this.
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.
I have read much of this post but not all of it. So forgive me if I missed something.
Your last post about switching to 441k made me think of something: EZX samples are 16 bit 441K. So if you’re using an EZX for the drum samples I think that even in SD3 they are going to play at 16/441.
Somebody may correct me on this.Superior Drummer 3 version: 3.3.3
Operating system: Windows 10
it’s a good thought, but I’m only using SD3 samples and SDXs.
All, in case my edited post got buried and passed over, it seemed to be a sample rate collision. Once I dropped my Wing console down to 44Khz from 48, pops disappeared. I still don’t full understand the why if it, as I thought SD3 playback was 48/24. Either way, thrilled to have a clean triggering experience again.
If I’m not mistaken, SD3 samples are 44/24.
jord
Hi all.
I would think that as a company, superior drummer would use a standard of 16 bit 44.1 kHz, as everyone is capable of reading this file, regardless of the daw and or computer system.
I didn’t think that they were 24-bit. Curious.
cheers, Ken
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.
I guess I just didn’t think that running my audio interface at 48 (and my VST host) would cause a sample rate discrepancy with the superior drummer samples, but it absolutely did. The problem has been non-existent since I switched my Wing console to 44.
Wow, I cannot believe that.
Wow, I cannot believe that.
I run 16/44.1 and 24/44.1 all the time the only thing is if I switch the sample rate from 16 bit to 24 bit in my daw the audio files all have to be converted, but never have I ever had to do any with superior drummer. It’s midi
Cheers Ken
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.
Wow, I cannot believe that.
Wow, I cannot believe that.
I run 16/44.1 and 24/44.1 all the time the only thing is if I switch the sample rate from 16 bit to 24 bit in my daw the audio files all have to be converted, but never have I ever had to do any with superior drummer. It’s midi
Cheers Ken
Superior Drummer 3 version: 3.3.6
Operating system: Windows 10
🤷♂️
I guess I just didn’t think that running my audio interface at 48 (and my VST host) would cause a sample rate discrepancy with the superior drummer samples, but it absolutely did. The problem has been non-existent since I switched my Wing console to 44.
Obviously, the drivers in your Wing can’t handle up sampling. This isn’t an issue with SD3.
jord
I guess I just didn’t think that running my audio interface at 48 (and my VST host) would cause a sample rate discrepancy with the superior drummer samples, but it absolutely did. The problem has been non-existent since I switched my Wing console to 44.
Obviously, the drivers in your Wing can’t handle up sampling. This isn’t an issue with SD3.
jord
1
Thanked by: BradWow, I cannot believe that.
Wow, I cannot believe that.
I run 16/44.1 and 24/44.1 all the time the only thing is if I switch the sample rate from 16 bit to 24 bit in my daw the audio files all have to be converted, but never have I ever had to do any with superior drummer. It’s midi
Cheers Ken
Superior Drummer 3 version: 3.3.6
Operating system: Windows 10
You are confusing bit rate with sample rate.
jord
I run SD3 in my 24 bit 48K -projects all the time and have no issues. So I don’t think it’s SD3. But my hardware interface just uses the sample rate it receives from my DAW (up to 24/192). There is no hardware setting for the sample rate and bit depth. And I don’t think I’ve ever seen a hardware interface that has this. The only thing I can set is the buffer size.
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.
BEST ANSWER
I guess I just didn’t think that running my audio interface at 48 (and my VST host) would cause a sample rate discrepancy with the superior drummer samples, but it absolutely did. The problem has been non-existent since I switched my Wing console to 44.
Obviously, the drivers in your Wing can’t handle up sampling. This isn’t an issue with SD3.
jord
I guess I just didn’t think that running my audio interface at 48 (and my VST host) would cause a sample rate discrepancy with the superior drummer samples, but it absolutely did. The problem has been non-existent since I switched my Wing console to 44.
Obviously, the drivers in your Wing can’t handle up sampling. This isn’t an issue with SD3.
jord
This makes the most sense. Also noteworthy is that I would only hear the crackle when triggering live; if I recorded the midi and played it back it was clean.
It makes me realize that this is likely the culprit with some other VSTs I’ve had issues with triggering live in the past, like IK Multimedia’s Sampletank 4. I’ll have to go back and re-test.
However, in my tribulations I bypassed the Wing completely, assigned the output to the external headphones port on my MacBook Pro, and still experienced the crackle Not sure what the sample and bit rate limitation is for the Coreaudio driver in Mac OS, but maybe it was the same issue.
Either way, happy to be enjoying a noise free e drumming experience again in my home studio.
Thanks for all the ideas
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.