Opinion: Addictive Drums 2 "minimalist" drum map

[Dave G]

I'm enjoying Addictive Drums 2 so far! However, I'm overwhelmed by the default AD2 drum map. It's adequate but jumbled and more than I need. Before using the map on my projects, I'd like to create a custom map that has what I need but missing nothing useful. Surely, I want to avoid the risk of discovering I'm missing a drum articulation from my map later on down the road...

I wish to use a simple, easy to navigate "minimalist" drum map for AD2. I'm simply seeking the most common and basic articulations of all the drum parts without any redundant and extra hits.

I'm okay with the sticks, kick, snare, and four toms. I have three cymbal + choke combinations assigned. (I'm considering removing the ride + choke combinations, as I've never heard that used.) I think my biggest confusion is the several hi-hat articulations available...just too many and more than I'd like to have. So I'd like to minimize these articulations to the common basics.

I feel sometimes my OCD for simplicity gets the best of me. Please let me know your thoughts, opinions, and suggestions on the above. Thank you!

I've attached a screenshot of my current AD2 drum map so far. (I'm embarrassed to have to point out that this attachment isn't showing in Firefox.)

Edited September 3, 2023 by Dave G

[Glenn Stanton]

i took the original AD2 drum map, and i made copies for different MIDI sources since each of them had decided to use "alternate" notes for things. so if i source my MIDI from Hookpad, Musescore, Toontrack, or some other MIDI library, i know to just open the AD map i edited. i'm not sure this is the best approach as it has taken 10-15 minutes for each one to adjust the note # in the source to the AD note #.

so maybe just bite the bullet and take the baseline AD drum map and tweak it for your source(s). and just ignore the ones you're not likely to use or simply remove them if you aren't concerned with some of the articulations being played.

[JnTuneTech]

3 hours ago, Dave G said:

I think my biggest confusion is the several hi-hat articulations available...just too many and more than I'd like to have. So I'd like to minimize these articulations to the common basics

One of the first thoughts that comes to my mind, regarding your post, is that "common basics" are really going to be individual, rather than common. -For instance, in what I mostly program, hi hat variations are one of my pet peeves, as there are never enough in any sample set to match real world variations. -For me-.  And, as to a ride & choke combo - I have played plenty of drum passages using expression on the ride - I would never leave that out.  -But again, that's me-.  I suppose our OCD nature needs to be recognized as personal, and although it's natural also to compare, and even helpful to learn some other viewpoints, one might want to try and focus on what method actually suits us best going forwards.

Sometimes it's about interoperability - between projects, or established standards, so then there's that too. -Way back when, as I began to program early MIDI drum modules that started with GM drum mapping as a basis, I was initially frustrated at some of the groupings and limitations of that system.  I still never found a "perfect" distribution of drum parts in mapping, and now with the depth of some drum sample sets, I find I can hardly make an "optimized" map that always covers the basics in any given sample set. In fact, I bounce back & forth between maps, depending on the material I'm covering, and whether the default sample sets are sufficient, or need to be customized (which for me it's about 50/50). -I'm just glad I can create & use alternate note name maps in Cakewalk for use in the PRV, that one ability alone helps me navigate my drum mapping OCD much more comfortably.  -All the programming still eats up so much time though!

[Dave G]

[Please pardon my reviving this topic so long after originally posting. I abandoned the project for a while, but still seek answers.]

Thanks for all of your input! As a newbie/amateur, I have remaining questions on hi-hat articulations. These simply aren't elaborated on in the Addictive Drums 2 Manual PDF.

Typically, I don't have a need to utilize every specific Hi-Hat articulation that AD2 offers. I'm looking to finalize my basic drum map that includes every articulation I'm likely to use.

Before integrating my AD2 drum map into all my projects, I wish to familiarize myself with how these articulations work in a real-life scenario -- to tell them apart and understand how to utilize them properly on the PRV. The image attached is my updated drum map's "Hi-Hat" section (keys 53 - 59). Here are my observations; please comment accordingly:

• I assume that the hi-hat is open by default, not closed. Does the foot pedal typically push down to close the hi-hat, or to open it?
• I assume that "HH Open" is the default action of pushing the pedal to open the hi-hat.
• The four "HH Open A, B, C, and D" seem to all sound similar, just gradually a harder attack with each key.
• How does "HH Foot Splash" differ from "HH Open"?
• I assume that "HH Closed" is the articulation of hitting the bell, tip, or shaft while the hi-hat is closed.
• I've observed that each "HH Open" and "HH Foot Splash" are muted/choked by the "HH Closed" and "HH Foot Close" keys.

Simply looking for explanations on exactly how these functions work. I worded these questions as clearly as I could. Any further insight and/or explanation is appreciated. Thank you again!

Edited November 30, 2023 by Dave Grund

[JnTuneTech]

1 hour ago, Dave G said:

• I assume that the hi-hat is closed by default, not open. Does one push the foot pedal down to open the hi-hat, or to close it? - No set answer in real life - drummers can adjust the "default" -at rest - per taste. Pushing the pedal down does normally push the two cymbals together, and physically the pedal can close them tighter, and depending on adjustments, the lifting of the foot off of the pedal can allow spring action to then open the cymbals. Sample representations, however, will vary, and are much more literal, and limited in scope.
• I assume that "HH Open" is the default action of pushing the pedal to open the hi-hat. - Refer to the answer above, & other info below.
• The four "HH Open A, B, C, and D" seem to all sound similar, just gradually a harder attack with each key. - Partially -Yes - good ears! But more actually primarily the sound variations produced by the 2 cymbals in differing ranges of proximity, or open-ness, if you will.
• I assume that "HH Foot Splash" also opens the hi-hat with the pedal. If so, how does this differ from "HH Open"? -Refer to the answers above, & other info below.
• I assume that "HH Closed" is the articulation of hitting the bell, tip, or shaft while the hi-hat is closed. - Basically, "Closed" there only refers to the position of the hi hat, and any following description would indicate if any of the other items you referenced are also in play. Actual samples vary - listen first.
• I've observed that each "HH Open" and "HH Foot Splash" are muted/choked by the "HH Closed" and "HH Foot Close" keys. -Yes. In most drum sampler default setups, an actual relationship is programmed between those samples, so that it mimics what actually happens in most typical drumming scenarios in real time linear play.

In bold are comments from what I go by, and have experienced, and I apologize in advance for any errors I may have made! I hope any of it helps.  -BTW - I find it great that you are following up on your posts - even if it took some time! Glad to hear you are still at it, and reading the answers & opinions.

- More  regarding the bulleted items you posted:   Almost all the drum sample players I've used so far operate on similar descriptions, but use the same mechanics, if you will, to emulate a physical drum kit piece recorded, and typical variations. There is one notable difference, however, when programming sampled hi hat sounds. In most samplers, there is an option to control hi- hat "open" articulations with a pedal (which is normally a MIDI CC variable), and most of us will input that manually in real time, as you would a real hi hat pedal setup. For the answers to your assumptions, though, that doesn't seem to be evident in your screenshot. so:

All the rest of the hi hat sounds, are different "articulations" - not actions - representing actual hi hat samples. Generally those are used in fixed-note playback scenarios, or mostly by programming manually. -I will note that in your example, "Open A, B, C, D" is rather generic labeling IMHO, but you did the best thing by listening to the sounds and clarifying how you would actually name and potentially use them! -Other samplers often use Quarter Open, Half Open, 3/4 Open, Full Open, which may make more sense - but again, listening is usually more accurate anyway.

And other than that, HH Closed simply means the sample was played with the hi hat closed - and the various articulations are various versions - articulations - of that, and similarly HH Open means the sample was recorded with the physical hi hat open - and again often you want various positions and styles of that, and again it can all be described many ways in different samplers. - There is no action - just samples being played. The hi hat "foot" samples are recordings of the sound made - generally - by pressing quickly down on the pedal (and closes it from an open position - listen and a good sample should sound just like that), and the "Splash" is the sound you get when you let the foot pedal on a physical hi hat come up - and typically that lets spring action open the cymbals (splash). -But just listen to it and see if it is what you want. -If you have never played drums before, it may not be clear how it all works for many of these sounds though, but once you do, you will know where it usually all fits! -That is of course, if you want to emulate a physical drum kit. -But you could actually just create whatever sound sequence you dream up!

-Wonderful thing about drum mapping is that you can make any layout you want. Hard thing about drum mapping is that you have to choose between your own maps - choices, or adapting to others that already exist, depending on what type of MIDI you are working with!

[Dave G]

21 hours ago, JnTuneTech said:

In bold are comments from what I go by, and have experienced, and I apologize in advance for any errors I may have made! I hope any of it helps.  -BTW - I find it great that you are following up on your posts - even if it took some time! Glad to hear you are still at it, and reading the answers & opinions.

Thank you for your extensive knowledge and wealth of information! This is pretty much what I've been looking for.

After I posted this, I watched several YouTube videos of the hi-hat in action. Although I found some answers there on the mechanical aspect of the equipment, I also realize that it partially depends on the drummer's preference in setup and intended use. I know I could've visited a music equipment retailer and spent time at a drum kit to familiarize myself in a more real scenario, but that's far beyond means and necessity.

If we may take this discussion back a few decades...

When I first began composing MIDI music in the 90's, all I knew to work with was the General MIDI universal drum map. Although this drum map is laid out without rhyme or reason -- various drum piece articulations jumbled in no particular order -- I conformed with it and grew accustomed to it. But now with Addictive Drums, my options have become greater...and unfortunately, much more challenging and complicated.

For somebody with OCD, it's a painstaking process to make decisions and commit to them. One being, of course, creating a custom drum map tailored to preference. In this case, I want to integrate every vital drum piece articulation but exclude any that I feel are redundant or unnecessary.

Once this drum map is complete, it'll be the basis of all my projects and maybe I can finally get them off the ground. I'm overthinking and obsessing too much over the fact that I may not like it later. I guess that's why it's taking so long...I want it to be right.

Anyway, I appreciate everything I've learned here. It just feels complicated assembling a custom AD2 drum map that's not too busy or difficult to work with. I'm not looking to create a commercial product...it's just a personal hobby I'm trying to remind myself to keep it simple.

For now, my questions have been answered. Thanks for your help!

Edited December 1, 2023 by Dave Grund

[JnTuneTech]

Just a quick addition to think about: I have found over the years that making use of the Drum Map feature in Cakewalk really allows me to do what you are seeming to do within the sampler map, only in my experience, much more flexibly & adaptable - in the long run. I can (and do) for instance, create Drum Maps that only use the note/kit pieces I care to see and deal with on the screen, -entirely eliminating any other ones visually. And once you learn how it works, you can add & remove mapping on the fly when needed. And many more optional uses become available - but only if you want to use them.

I also have spent many years dealing with the GM (GS, XG, what have you) note mapping conventions, and never have been quite happy with that drum mapping, other than the interoperability aspect (which can be very important of course). I am glad to have the capabilities of Drum Map creation in Cakewalk for making my own organization.