4

[pumpkinking]

Works fine on my MBP with M2 Pro running Ventura.

Reply To: Does SD3 work with M2 Silicone and Monterey version: 3.3.6
Operating system: macOS Ventura (13)

[pumpkinking]

I have attached two screenshots here that show the MIDI mapping o0f racktom3 from my module into SD3.  The eDrumIn module screenshot shows that I have assigned MIDI note 70 (and channel 11) to the rack tom 3 center hit, and this is from module #2 (I have split my 20 triggers across the two eDrumIn modules).  The SD3 screenshot sows that incoming MIDI note 70 is mapped by SD3 to note 67 which is high tom 3 center (SD3 does not use the channel other than for filtering which I am not doing here).

In most cases, I have manually assigned the MIDI notes sent from my 2 modules to be the exact value in SD3, but in some cases different SDX kits will have different assignments, and to keep my module assignments the same across all kits, I have created SDX-specific midi maps to allow me to seamlessly switch between SDXs without having to change anything (either than loading the user midi map).

I do not have a TD-50 so I do not know what the MIDI note configuration is like for that module.

Let me know if I have not provided the detail you were hoping for.

 

Thanks,

Joe

[pumpkinking]

Hi Dan,

I use the kit modules to change the midi note values that they generate for specific triggers.  This capability was available (albeit cumbersome) on the 2 Alesis modules I used to use.  I have since switched to 2 eDrumIn 10-input modules and the software interface supplied with them has a straightforward way to assign midi note values and channel to each trigger (incl multi-note triggering like ride and snare).  I’m moving my kit this weekend so cannot screenshot at the moment, but when it is back up and running I’ll send screenshots of both the eDrumIn config and how I am mapping the midi in SD3.

-Joe

[pumpkinking]

One more possible enhancement in this space that just hit me would be a CSV output that would contain a row for every midi note value in the kit/preset and columns that would show the midi-in/edrum mapping and instrument/articulation.  This would be very handy to see it all at once and validate that it is setup the way I want.

[pumpkinking]

Your best bet, if you’re looking at a small number of notes, is to change the outgoing midi note from the second module using the configuration interface on the module.  I have two modules and this is the way I have decided to manage it.

Failing that you could have two instances of SD3 (two SD3 tracks in your DAW, for example), each with a channel filter, and map each instance to one of the modules.

Reply To: Using two identical Modules within SD3 version: 3.3.5
Operating system: macOS Ventura (13)

1

Thanked by: Michael Dumanski

[pumpkinking]

This is what I was able to determine for the post-SD3 SDXs based on some research.  Might be inaccurate….

 

11/17 SD3 Product and Core

11/17 Rock Foundry

5/19 Orchestral

9/19 Decades

11/19 Death and Darkness

3/20 Rooms of Hansa

9/20 Legacy of Rock

9/21 Fields of Rock

9/22 Hitmaker

11/22 Area 33

Reply To: EZX & SDX release timeline version: 3.3.5
Operating system: macOS Ventura (13)

[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, 2 months 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)

[Author]

Replies