5

[pumpkinking]

Some things to look at…

Have you tried standalone?

Are you hearing the distortion on other instruments or only snare?

Have you tried to load a supplied preset with the same snare and see if the distortion is there as well?

Reply To: Distorted snare version: 3.2.8
Operating system: macOS Monterey (12)

[pumpkinking]

To help you answer your question, let me pass along some real data from my system.  I have a Mac mini M1 with 16 GB RAM, and I started Logic Pro X with an SD3 plugin linked to a track.  I have screenshots attached of the SD3-reported memory consumption (2823 MB) and the process memory consumption for Logic (312.5 MB), the SD3 AU (2.72 GB) and other Logic-related processes (these total ~11 MB, and there might be a few more but they are all very minor).  My conclusion is that the 2.72 GB reported for the AU is (nearly) exactly what is reported by SD3, and the rest of the memory consumption of the Logic session is

Reply To: How would SD3 performance be running a new Mac Mini M1 with 8GB of Ram? version: 3.2.8
Operating system: macOS Monterey (12)

• This post was modified 3 years, 10 months ago by pumpkinking.

1

Thanked by: Red Gear Music

[pumpkinking]

I currently have 20 triggers in my kit connected through 2 different modules.  I’ve been able to use all 20, although with some SDXs it is easier than others, depending on how many pieces the SDX kits support out of the box.  You can always add X-Drums, but I find them a bit laborsome to balance to the rest of the kit and there is the matter of no X-Drum bleed (I’m sure there are nifty solutions, just never worked that much on it).  I find that Death and Darkness provides a very large number of tom/cymbal slots in the two kit configurations supplied and fits well with a large e-kit.

I will say that ultimately you’ll be limited by the 128 midi note limit (Theoretically, there are two drum midi channels – 10 and 11 – but I have not found that SD3 can differentiate them).  One way this has limited me is in the total number of articulations usable on pieces that tend to have a lot (like hi-hat).  At some point you’re going to have to make a concession on either advanced articulations, or drop standard articulations of the basic kit pieces (like rim/rimshot on toms).  Also the midi mapping of new triggers gets tricky as you fill up the midi notes (you end up searching for mapped notes that you are not using, changing them and then making sure your module sends a different midi note).

Reply To: MIDI drums for big kits version: 3.2.7
Operating system: macOS Monterey (12)

[pumpkinking]

On your iMac, pull down a free app from the App Store called “AmorphorusDiskMark”.  Once it is installed and open, then select the disk where your SD3 libraries live and run all tests (Just click on the All button).  It will take a few minutes, but then look at the “Read” column (specifically the SEQ1M QD8 and QD1 numbers) and you should see something like the attached (which was measured on my SD3 library SSD.

Those numbers are in MB/s (and they are sort of best case scenario, but probably reasonably close to real world).  So now look at the size of the library you are loading in the SD3 window, and divide it by the smaller of these two #s.  In my case, the amber kit is 10227 MB, and I divide that by 612.11 MB/s for SEQ1M QD1 Read score and I get 16 seconds.  The actual load time is 25 seconds, and the reason it is longer probably has to do with the details of how the libraries are stored and retrieved, but it should be within ~2X of the calculation.

Reply To: Is There Any Way of Speeding up Legacy of Rock Loading Time? version: 3.2.7
Operating system: macOS Monterey (12)

• This post was modified 3 years, 11 months ago by pumpkinking.

[pumpkinking]

Have you measured your library storage hard drive read speed?  My calculations showed the kit loading time were just about what the speed measurements predicted.  If you are not seeing that the loading times match what speeds would suggest, then something else is going on.

The speedy reload could come from caching, so might not be reflective of the nature of your fresh loading delays.

Reply To: Is There Any Way of Speeding up Legacy of Rock Loading Time? version: 3.2.7
Operating system: macOS Monterey (12)

[pumpkinking]

Even 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.

 

Reply To: Is There Any Way of Speeding up Legacy of Rock Loading Time? version: 3.2.7
Operating system: macOS Monterey (12)

1

Thanked by: David

[pumpkinking]

Check 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).

Reply To: Some kits are distorting whilst playing TD50x version: 3.2.7
Operating system: macOS Monterey (12)

[pumpkinking]

You 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.

Reply To: TD17KVX paired with Superior Drummer 3 – HiHat is bleeding the off-notes version: 3.2.7
Operating system: macOS Monterey (12)

1

Thanked by: Kim Mossige

[pumpkinking]

Running?  Yes – community verified.  Official support?  Not yet that I’m aware of.

Reply To: SD3 Monterey version: 3.2.6
Operating system: macOS Monterey (12)

1

Thanked by: Pit P

[pumpkinking]

I’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.

Reply To: Transferring User Tweaks To 2nd Computer version: 3.2.6
Operating system: macOS Monterey (12)

1

Thanked by: anthony cruz

[pumpkinking]

I 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.

Reply To: Transferring User Tweaks To 2nd Computer version: 3.2.6
Operating system: macOS Monterey (12)

1

Thanked by: anthony cruz

[pumpkinking]

I 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.

Reply To: macOS Monterey SD3 Be Compatible? version: 3.2.6
Operating system: macOS Big Sur (11)

1

Thanked by: Headplay

[pumpkinking]

I 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.

Reply To: Mac OS Monterey support version: 3.2.6
Operating system: macOS Big Sur (11)

5

Thanked by: kentuckychrome, 12345_11, tama42 and 2 others.

[pumpkinking]

I’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.

Reply To: SD3 distorting and clicking also latency issues version: 3.2.4
Operating system: macOS Big Sur (11)

1

Thanked by: thebaz_1

[pumpkinking]

Yes, 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.

Reply To: Is SD3 M1 compatible? version: 3.2.4
Operating system: macOS Big Sur (11)

1

Thanked by: adiaz7531

[Author]

Replies