pumpkinking
Participant
Topics Started: 5
Replies Created: 84
Has Thanked: 12
Been Thanked: 32
pumpkinkingEven a fast SSD connected through the wrong interface will be slow, so you might need to tweak your setup. You could measure the read performance of your various drives with a free app (like AmorphousDiskMark – never used it but is free and has good reviews). Then you could compare with expected performance for the drive, others’ posted performances, etc.
If the SSD speed check is OK, then it is not drive performance causing your issue.
FYI – I just ran the above mentioned speed test and my SD3 library SSD read speeds were reported as 696, 613, 168 and 30 (all MB/s, tests: SEQ1M QD8 & 1 and RND4k QD 64 & 1).
Using this SSD the amber kit (10227 MB with my config) loads in 25 seconds. If I do the math that is about 400 MB/s, so not too far off of the sequential read results quoted.
1
Thanked by: DavidpumpkinkingCheck out the memory footprint of the kit and compare it to the free memory on your machine. The crackling could be computer artifacts from SD3 needing more memory than is available (I have experienced this before). I say that because I use the amber kit and it tops out at 10GB for my config, and you indicate that your system has 8 GB RAM. You might consider 16-bit samples or the non-cached mode for the kits that need >6-7 GB (or whatever is free before you start the SD3 application).
pumpkinkingYou might check whether you’re triggering a hi-hat splash. There is a splash sensitivity slider in the Midi In/E-Drums window on the Hi-Hat Pedal tab.
A splash is triggered based on the timing of a foot pedal close/open sequence, and the slider likely controls that timing. You can also toggle splash off entirely in the same control tab.
1
Thanked by: Kim MossigepumpkinkingRunning? Yes – community verified. Official support? Not yet that I’m aware of.
1
Thanked by: Pit PpumpkinkingI’m not sure if these are tweaks “per project” as much as saved user presets for a given component that would be selectable within a project. I’m def not the expert but it seems like copying that over in addition to your project .sd3 files would work.
1
Thanked by: anthony cruzpumpkinkingI share .sd3 files between two computers that also share the same SDXs (done though remote mounting drives/folders on macOS). This works well and allows me to keep my SD3 project edits (midi mappings, kit tweaks, track midi edits, etc) in-sync between the two machines.
1
Thanked by: anthony cruzpumpkinkingI upgraded my system to Monterey the day it was available (Oct 25), and SD3 stand-alone and as a plug-in for Logic has been working fine. Not an exhaustive test, but I’ve not noticed any difference so far.
1
Thanked by: HeadplaypumpkinkingI just completed the macOS Monterey update on my Mac Mini M1 and opened SD3 and it worked as expected. This was a minimal check – just a quick run-around on the edrum kit with an SD3 core lib config. Will do more exhaustive check later today.
pumpkinkingI’ve noticed the clicking noise as well, and I’m using a Mac so seems to be unrelated to the audio driver and settings. I notice the clicking specifically when I change kit/SDX and start playing while it is still loading the samples, and the clicking persists after the samples have loaded, so seems like a corruption of the samples in memory. I do not have dynamic caching set and always load all samples into memory. It seems if I am patient and wait for the samples to all load before playing anything, I can avoid the clicking noises.
This issue does not seem to affect bouncing, and I can change to another kit and back, waiting for samples to load, and the issue goes away.
1
Thanked by: thebaz_1pumpkinkingYes, I am using it on a Mac mini with a silicon M1 chip. SD3 is still not natively supporting M1 (and as such uses Rosetta) but I have seen no issues, and responses by Toontrack in another support ticket indicates that the M1 native support should be coming soon.
1
Thanked by: adiaz7531pumpkinkingHi monospace. You might be on to something but I’m not able to see it consistently. If I just open the core library to the default kit, and then place the offending cymbal in slot 5, I hear what you are referring to clearly. However, if I take an existing core custom preset that I use frequently and do the same, it is OK. So far I cannot explain why this is the case, however…
Here is more info: if I solo the Ambient ribbon mic, the cymbal is clearly from the right. If I solo the OH Dynamic, it is very much from the left. And if I solo the Ambient near it is close to middle. So maybe check your mixer, maybe the preset that sounds good to me has the OH Dyn off or lowered. I’m wondering if just one mic (OH Dyn) was L-R reversed. I’ll keep playing with it.
pumpkinkingI just went through all of the articulations on this cymbal in the 5 position you indicated, and they all appeared to originate more in the right side of the stereo field than the left, although the sustain approached a balanced L/R quickly. Hard to accurately measure in the SD3 mixer (that I know of anyway) so I cannot prove it. But I did compare it to the default cymbals in positions Cymbal 1 and 2 and there was a distinct difference in perceived location in the stereo field.
pumpkinkingYou should be able to open the Midi In/E-Drums menu, hit the tom rim you want to map, and change its note mapping to the Ride->Bell shank note (or whatever midi equivalent you want) in the mapping tab on the right side of the menu.
pumpkinkingYou might want to compare the midi monitor values when playing the hi-hat in standalone vs. as a plugin to see if there is a difference in the incoming midi values for a closed edge/tip trigger.
I also had this happen once or twice in standalone and I resolved it by powering my modules off, refreshing the midi devices, powering them back on and refreshing/selecting again. You have to make sure you reselect the midi preset you want to use. Just seemed like a glitch to me, I think I had the hihat pedal closed while powering up the module and SD3 and maybe that had some negative interaction.
pumpkinkingThe M1 chips appear to have 8 cores, but they are not all the same: there are 4 “big” cores and 4 “little” cores. The big cores are for compute-intensive workloads and the little cores are for smaller workloads (and are much more power efficient). How these cores all work together is controlled by the hardware/software architecture, and very likely has different modes depending on the workloads. I am guessing these modes include configurations that use just the 4 little cores and just the 4 big cores, and possibly all 8 together, although the throughput will be different between big and little cores, so I’m not certain of that.
My guess is that these processors work best when running applications that require 4 or fewer threads, although I have no data to back that up. That said, I have a mini with an M1 chip and I have SD3 set to 4 cores.
No products in the cart.
