No products in the cart.
mrdrennan
Participant
Topics Started: 2
Replies Created: 15
Has Thanked: 2
Been Thanked: 0
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
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
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
Reply To: The Dreaded “Snap Crackle Pop” 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.
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.Reply To: The Dreaded “Snap Crackle Pop” 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 it only happens on certain presets, have you watched you SD Master Fader for peaking and/or the channel your DAW is on. High dynamic midi will distort a lot of default mixer presets. I turn my plugin master fader down often due to this.
It’s a good thought, and I did make sure that gain staging was all appropriate. Strangely enough, if happens even on the lightest of strokes. I did try switching to some other presets as well. It’s not AWFUL, but enough to diminish the experience.
Are you using another display? If yes, could you try disconnecting it. Just for a test.
Any other software running that also may be using the audio interface? I noticed a few glitches when I had lots going on graphically with Studio One and any virtual instrument.
Can you put your display to sleep and see if it still happens?Reply To: The Dreaded “Snap Crackle Pop” version: 3.3.5
Operating system: macOS Monterey (12)Oooh man this really had me intrigued for a second. One thing I did recently change was rearranging my studio and, yes, I am pushing not one, but 2 external monitors. Alas, I disconnected all external displays and even sleep the MacBook display, but the crackle is still there about every 5th or 6th strike. I notice your Mac Sfudio is spec’d very similar to mine; what are your experiences with buffer settings?
After disconnecting your displays did you reboot the MacBook?
Standalone my buffer in SD3 is at 64. Not a lick of problems. (I’m not Mike Mangini, but I rolled as fast as these old digits will let me)
Studio One buffer is down to 32, with 2 instances of SD3. UVI Falcon, EZBass and a bunch of guitar tracks.
Now I am, using a Personus Quantum (Thunderbolt 2 through an adapter), so the basic rig is quite different.
Can you get a hold of another interface (borrow, beg, steal)….. see if there’s something there?
Do you work with any other VIs? Does the same thing happen?
You are running native and not via Rosetta, yes?
Sorry I don’t have anything really specific to provide. A bit of a head scratcher really. Your rig is more than capable.
Reply To: The Dreaded “Snap Crackle Pop” version: 3.3.5
Operating system: macOS Monterey (12)
- This post was modified 2 years, 4 months ago by Brad.
Man I’m truly stumped. I’ve recently tried all the fixes suggested here and even went so get as to switch to Dante Virtual Soundcard to bypass the USB bus. I wish I knew what was going on.
*EDIT
it appears to have been a sample rate issue. I knocked my Wing down from 48 to 44 and voila…annoying artifacts gone. Now my question is, aren’t the SD3 samples recorded at 48/24bit? I swear I’ve had my mixer at 48 for months.
Im not sure if this help, but i had a similar problem on my previous laptop.
My solution was to minimize the Superior Drummer windows while playing,
so the windows desktop was visible. Weird solution, and i never found out why that worked.Reply To: The Dreaded “Snap Crackle Pop” version: 3.3.5
Operating system: Windows 11
Tried it but no luck!
An elementary thought but try using another set of headphones?
Tried several pairs.
How many devices do you have hooked up to your USB? You might be driving it to the point where CoreAudio just cannot keep up. You might want to consider purchasing the Audio over IP option for your Wing. Using USB for audio is rarely a good choice.
jord
Looking into Dante, as that’s what I used on X32. However, I had some troubles with Dante on the M1 Macs, even after they released a compatible version of Dante Virtual Soundcard.
Sorry one more random thought now that I have had my third espresso…. you mentioned rearranging your studio…..
Did you lengthen the distance between your computer and interface, MIDI interface, anything?
Reply To: The Dreaded “Snap Crackle Pop” version: 3.3.5
Operating system: macOS Ventura (13)
No substantial cable runs. I did not restart after disconnecting the displays so I will try that when I return from Super Bowl watching. Thanks for trying to help me work through it…my experience to this point has been much the same as yours…a dream for e-drums!
If it only happens on certain presets, have you watched you SD Master Fader for peaking and/or the channel your DAW is on. High dynamic midi will distort a lot of default mixer presets. I turn my plugin master fader down often due to this.
It’s a good thought, and I did make sure that gain staging was all appropriate. Strangely enough, if happens even on the lightest of strokes. I did try switching to some other presets as well. It’s not AWFUL, but enough to diminish the experience.
Are you using another display? If yes, could you try disconnecting it. Just for a test.
Any other software running that also may be using the audio interface? I noticed a few glitches when I had lots going on graphically with Studio One and any virtual instrument.
Can you put your display to sleep and see if it still happens?Reply To: The Dreaded “Snap Crackle Pop” version: 3.3.5
Operating system: macOS Monterey (12)
Oooh man this really had me intrigued for a second. One thing I did recently change was rearranging my studio and, yes, I am pushing not one, but 2 external monitors. Alas, I disconnected all external displays and even sleep the MacBook display, but the crackle is still there about every 5th or 6th strike. I notice your Mac Sfudio is spec’d very similar to mine; what are your experiences with buffer settings?
If it only happens on certain presets, have you watched you SD Master Fader for peaking and/or the channel your DAW is on. High dynamic midi will distort a lot of default mixer presets. I turn my plugin master fader down often due to this.
It’s a good thought, and I did make sure that gain staging was all appropriate. Strangely enough, if happens even on the lightest of strokes. I did try switching to some other presets as well. It’s not AWFUL, but enough to diminish the experience.
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.
You solved it Brad! Turns out I was on 3.2.7. There must have been a bug because I tried it once again before I updated with the same result, but 3.2.8 behaved exactly as you described. Thanks!
I don’t recall the exact presets. I do know that I chose a channel that had an fx chain on one preset and not on the other to see if it would work. I assumed that loading the channel strip from the processed channel to the unprocessed would remove all of the effect inserts, but it did not. I’m on Mac OS Monterey and Superior and all libraries are up to date.
Thanks.
No products in the cart.