4

[pumpkinking]

Hi Olof,

Thanks again for responding – I do appreciate the time in understanding the request and refining what I’m referring to.

The primary workflow issue that I’m referring to would be adding instruments or enabling articulations of existing instruments that are not currently midi mapped.  Secondary would be refining/validating the midi-in/edrum mappings.

Here is a specific example – in the SD3 core default kit, the ride cymbal has a few duplicate note assignments, eg 51 and 113 both trigger the bow tip articulation.  This means that, should I need to assign a note to a new articulation or instrument, I could use one of these two notes and not remove existing functionality (although an e-drummer would have to take care to not remove the one mapped to the e-drum kit).  Say for example, I want to add the “FX” articulation for the ride (which by default is not midi-mapped), an I use the “add note” menu item available in the midi mapping callout for FX.  Knowing which midi notes are either unassigned or unmapped duplicates from the layout window would be a helper here.  Currently I have to gather this info from several sources.

I know there is a suggested note menu item, but I have found this to sometimes be destructive (changes notes that are assigned and I am using).

What would really be wonderful is a GUI “connection board” of sorts that would allow me to connect incoming e-drum midi to instrument articulations directly, and all visible in a single window like the midi layout window.  The midi-in/edrums window can do this, but only one-by-one without the “world view” of the entire set of 128 notes.

I have done this myself with a spreadsheet where I have columns for midi-in/edrum note, articulation note and articulation name.  Seeing that is actually quite helpful, especially when I can sort by different columns.

Anyway, thanks for reading and tolerating my verbosity, and hopefully the UX team can think about these workflows and some cool visuals that might help.  Keep up the great work!

Thanks, Joe

1

Thanked by: Olof Hermansson

[pumpkinking]

Hi Olof,

Thanks for the response!  I exclusively use SD3 for e-drumming, but I have a custom trigger setup that uses two eDrumIn modules for which there is no supplied e-drum preset, so I must create user e-drum presets for everything I do.  It seems that my user e-drum presets are not supported by the “dim extra notes”.

Is this expected?  It would seem this “dim extra notes” functionality would be especially useful for people who create and maintain user e-drum presets (ie. those who need to modify the note assignments and look for open notes to add new instruments), and yet that seems to be a case where they do not work.

Thanks and have a great day!

• This post was modified 3 years ago by pumpkinking.

[pumpkinking]

I have done this successfully, using an additional instrument and a separate CC for the controller (CC5 in my case, set in an eDrumIn module). What was tough was finding enough available/usable midi notes to capture all of the articulations in the second hihat to have it full-featured.  But it is possible (albeit not simple).

Reply To: Two Hi Hats version: 3.3.4
Operating system: macOS Ventura (13)

[pumpkinking]

Hi.  I have done this successfully (although using a different kick for the second).  You will want to manually tweak the addl kick mixer setup to match the effects and bleed of the stock kick.  I notice in your mixer screenshot that the X-kick channels have no effects or bleed so you will need to configure that or it will sound completely disconnected from the rest of the kit (likely what you are referring to).  This is just “the way” when you add instruments to a kit in SD3.  Maybe there is a way to copy/paste settings, not sure.  I just do it all manually.

Reply To: Issue with adding second kick to standard kit version: 3.3.3
Operating system: macOS Ventura (13)

[pumpkinking]

I’ve been using it standalone since upgrading to Ventura 4 days ago with no issues.  Have not yet tried in my DAW.

Reply To: macOS ventura version: 3.3.3
Operating system: macOS Ventura (13)

[pumpkinking]

Yup – multiple choices for how to change the notes.  Actually I have a combination of changes in the modules and changes in SD3 saved midi maps.

[pumpkinking]

You will need to change the midi notes output from the modules to not overlap.  I have been using 2 modules with SD3 for a couple of years now and I spent the time up front to pick midi notes on the module configuration interfaces such that each trigger was sending out unique midi note values.  Takes time but you only have to do it once (unless your actual triggers change).

[pumpkinking]

Check out the percussion list for Fields of Rock (bottom of the ping detail page) – see if that has what you need.

Reply To: Tambourines and shakers version: 3.2.8
Operating system: macOS Monterey (12)

[pumpkinking]

In the future, maybe refrain from deriding people trying to help, even if you perceive that help to be “totally irrelevant”.  This is, after all, a community help forum: when people respond, take it or leave it, but don’t discourage it.

Reply To: Superior Drummer 3 stutters on blazing fast AlderLake hardware version: 3.2.8
Operating system: macOS Monterey (12)

[pumpkinking]

The OP’s theory postulates that the issue is related to SD3 running on a bigLITTLE processor architecture (realizing that there are many aspects of this processor configuration that might be a potential reason).  I was merely pointing to a bigLITTLE processor architecture (Mac M1) that functions well with SD3.  So I was hoping to help eliminate possible sources of the problem.

Reply To: Superior Drummer 3 stutters on blazing fast AlderLake hardware version: 3.2.8
Operating system: macOS Monterey (12)

[pumpkinking]

I cannot speak for the Alder Lake processor or Win11, but SD3 running on my 8-core Mac M1 processor (arm64 arch, 4 big, 4 LITTLE) seems to run almost exclusively on the efficiency LITTLE cores, even when I try to play as aggressively as I can, with no stuttering.

Reply To: Superior Drummer 3 stutters on blazing fast AlderLake hardware version: 3.2.8
Operating system: macOS Monterey (12)

[pumpkinking]

You might be limited by the 4GB of RAM in your machine.  If you try to use an SD3 kit that uses more RAM than your machine has, you will have audio artifacts like you describe.

Make sure the kits you are loading in SD3 are less than 4GB (maybe a few 100MB less).  There are presets in the 2-3 GB range, and you can always remove pieces to get the memory down.

Reply To: Switched from EZD to SD3 and now I have severe pops and clicks version: 3.2.8
Operating system: macOS Monterey (12)

[pumpkinking]

Pretty much.  Check out what trigger brands the edrumin has been tested with (they maintain a list in the forums).

Ive personally set up some large kits for specific projects like the rototoms/octobans in Hansa, a large D&D double-kick kit with a second hi-hat, and a Ludwig kit in the core library with a double kick, a high concert tom, second hi-hat and a side snare.

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

[pumpkinking]

BEST ANSWER

Library drive speed will only affect the initial kit loading (assuming you’re not using the on-demand load feature, and the whole kit loads at once).

you can estimate the loading times by looking at the size of the kits/presets you use and measure the real drive performance.  I suggest not looking at advertising/marketing figures for drive performance, but instead look at reviews of your SSD that contain real measured performance, or use any of several free tools to measure it yourself.

once you have the kit sizes and drive speed, it is simple math to estimate kit loading times (size/speed=time, assuming the units align).  So an 8GB kit will take 13 seconds to load from a drive with 0.6GB/s read performance.

once the kit is loaded, the library drive speed should have no impact on performance since the samples are all in memory.

Reply To: Ssd drive speed version: 3.2.8
Operating system: macOS Monterey (12)

Library drive speed will only affect the initial kit loading (assuming you’re not using the on-demand load feature, and the whole kit loads at once).

you can estimate the loading times by looking at the size of the kits/presets you use and measure the real drive performance.  I suggest not looking at advertising/marketing figures for drive performance, but instead look at reviews of your SSD that contain real measured performance, or use any of several free tools to measure it yourself.

once you have the kit sizes and drive speed, it is simple math to estimate kit loading times (size/speed=time, assuming the units align).  So an 8GB kit will take 13 seconds to load from a drive with 0.6GB/s read performance.

once the kit is loaded, the library drive speed should have no impact on performance since the samples are all in memory.

Reply To: Ssd drive speed version: 3.2.8
Operating system: macOS Monterey (12)

[pumpkinking]

Also maybe check the memory usage on the machine when you have the DAW open and SD3 plugin loaded with the kit in question.  If that combo (plus whatever else you have going) is using all of your free memory, you would be starting to use swap, and that can cause distortion.

I have seen this when I had two different SD3 tracks in my DAW (recording two different preset kits in the same project).  The total mem used was greater than the system memory and the SD3 samples started getting choppy.

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

[Author]

Replies