www.megadrum.info

Been configuring my ARM 32 input MD with XLN's recently released Addictive Drums 2. I've just discovered they added 2 x MegaDRUM preset options in the AD2 MAP settings window: 'MegaDRUM Basic' & 'MegaDRUM Advanced'. I've only explored hi-hat functionality so far but it's looking good... with my DIY hall effect sensor HH it was easy to configure a very natural feeling response, from tightly closed to fully open, inc chicks and splashes using AD's 'Learn' feature. Need to delve into this some more to explore its full potential.

One other neat feature for edrummers: AD2 works in standalone mode i.e. no additional DAW software required if all you want to do is make sounds rather than record them.

Hi John! Ahh! Somebody did finally see it! You won the contest, John!

The two MegaDRUM presets are a nice result from my work with the AD2 Beta. (About 2.5 months work) where I made some nice connections with the XLN people.

We are soon going to release the two corresponding configuration files for MD. The idea we have is to offer a fixed midi map for the all the inputs (1-32) and use AD2's corresponding naming conventions for the slots. This will give MD users an easier and faster journey and bring down the configuration complexity.

So stay tuned best MD friends! More information is coming!

Best regards

Anders

Excellent work Anders!! Great news to hear you were working with XLN on this. Very well done!

Got a couple of AD2/MD questions you may be able to help with...

1. When using the LEARN function in AD2, what is the correct method to save each individual 'learned' sound to a particular kit piece. For example, I find when I use LEARN to set the various open hi-hat sounds (A/B/C/D), it assigns the last used open sound to all other hi-hat positions. I then have to use LEARN once more to restore a closed tip sound to achieve the correct sound for the pedal down position. I can make the whole variable deal work but I haven't figured out a fail-safe sequence to set up the various CC settings - it seems rather hit and miss. I'm assuming there's a correct way to do this? As a sidenote... I notice the actual pedal movement graph that used to display real time pedal position in the previous AD1.5 hi-hat setup screen is no longer working in AD2. Do you know if this will be reintrouduced when the MegaDRUM presets are finalised?

2. AD2's velocity curves appear to override curves applied in MDM. Is there a preferred method? i.e. if I decide to rely on AD's velocity curve options for all kit pieces, is there a particular velocity curve I should assign in MD for this to work correctly or does AD always overrule all MD velocity curves?

Hi John
A bot off topic but can I ask what sort of latency you're getting with the focusrite?

airflamesred wrote:Hi John
A bot off topic but can I ask what sort of latency you're getting with the focusrite?

According to Centrance LTU (http://centrance.com/downloads/ltu/), it's in the 2 to 3ms range from the Focusrite 2i2's input to output at 41000Hz/89 samples. Each time I run a test the LTU results vary. Not sure if it should be a constant figure?

As for playing the kit, there's no perceivable delay - it feels good. The 2i2 made a a very noticeable improvement over my Win7 PC's onboard soundcard and ASIO4ALL drivers. No doubt the new laptop helps as well: Win 8.1, i5, 8GB RAM.

Thank you
I'm toying between the 2i2 or Steinbergs UR22 after wasting money on a Tascam US1800.

airflamesred wrote:Thank you
I'm toying between the 2i2 or Steinbergs UR22 after wasting money on a Tascam US1800.

The 2i2 is my first ever audio interface so I've nothing to compare it to other than my PC's original soundcard. Seems to do the job

I first considered a used Presonus or M-Audio Fast Track but after checking ebay prices for a couple of weeks, decided a brand new 2i2 (£119 with warranty and USB 2.0) was a safer bet than an older USB 1.0 soundcard that usually ended up selling for £80 to £90.

Hi John!
1. Regarding the hihat mappings in AD2. Check the text below from my upcoming manual:
(I am also including the BETA version of the two related MDS files. - You can have a look in them and get an idea how I have mapped the hi-hat.)

It is not possible to do the learn function to get all articulations A-D. But you won't need that. Check my MDS files...and make a choice - The MegaDRUM Basic approach or the Advanced approach - it is more or less only the hi-hat handling which is different. The AD2 hi-hat realtime position indicator was supposed to be back in the 2.0.1 version which was released last week - but I am guessing we need to wait for a couple of weeks more.)

2. There are actually really no recommendations where to set the midi velocity curve. I have done mine in the MD. But both will work perfect. But don't use both...However it could be useful to handle the Hi-hat pedal velocity curve in MD...because you don't have that function in AD2.

Please note that all specific e-pad/cymbal settings in the attached MDS files have been set to default/zero...so it is only the midi values/names which is right - so if you save this MDS config over your current pad settings...don't call me!

From my manual:
The MegaDRUM Preset Map in AD2
Both the MD presets are following AD2’s default map in terms of note values and the reason is to make it easier to support and maintain the MD presets in the future. However, both presets are a bit different compared to each other on a couple of points.

MegaDRUM BasicAll mapping for the hi-hat pedal and related type of hits have been mapped to each note in MD, e.g. Closed, Half closed-Open, Chicks and Splash. We have completely switched off AD2’s own hi-hat logic for handling chicks or splashes in the Basic settings. This way to handle the hi-hat is mentioned in the Addictive Drums manual named as the scenario 2 for the hi-hat implementation. AD2’s hi-hat articulations have been set to be rather flat based on the cc:04 pedal value. You could change it to fit your play style and hi-hat gears.

In the MegaDRUM Basic settings - We have not used any advanced functions like positional sensing for the snare - all keymaps in the MegaDRUM_Basic.MDM are pointing to the exact value. (none cc:04 or cc:16 based input notes has been used)

MegaDRUM AdvancedThe hi-hat settings is using AD2’s own hi-hat engine and logics for handling closed to open hits and functions like the chick and splash. This hi-hat functionality is described in the AD2 Manual as scenario 3. The MD is only sending bow/edge hits + the hi-hat pedal position value over the cc:04 channel. The rest is handled by AD2's own hi-hat logic to determine hi-hat splashes or chicks. (Done through setting the sensibility in AD2.)

The MegaDRUM Advanced preset also includes the positional sensing settings configured to receive on the cc:16 channel for the snare. These setting has also have been slightly adjusted on the sensitivity for positional sensing. We have also enabled cc:16 for the two ride cymbals for future MD purposes.

Best Regards

Anders

Hi all,

I am interested in building an e-kit with the MD32 and would like to use the AD2 software in standalone mode.
I would like to know what laptop/Tablet/PC would be best for that combination?
My objective is portability between my house and church which I play a Roland TD-20x
I was thinking the surface pro 2.
any suggestions is much appriciated

cheers,

JG

Anders, I'll try your mds files later tonight. This is looking good!

However, I'm a little confused re velocity curves...

angr77 wrote:There are actually really no recommendations where to set the midi velocity curve. I have done mine in the MD. But both will work perfect. But don't use both...

How do I know for sure which curves are being used - MD or AD? I don't see a setting in either program that enables/disables velocity curves. For instance, what happens if I have all curves in MD set to linear and I then make curve adjustments in AD? On the other hand, what if I want to carry out all curve adjustments in MD? If I leave all AD2 curves at their default (linear), does that mean AD has no influence at all on velocity?