This means that inside Addictive Drums 2’s Map Window a snare trigger has to be assigned to C#1 as well, and this step has to be repeated for each single Drum Rack pad/chain. To further explain this process, here is an example: the Snare pad in Drum Rack – next to the kick – is triggered by C#1. From here you can see which note is played, and to which note it is redirected to trigger the right corresponding kit piece.

This is what happens in the I-O settings, which can be accessed once the Chain List is visible. In order for the MIDI patterns from the Beats section inside Addictive Drums 2 to be imported correctly, a custom MIDI mapping preset had to be made that corresponds with the routing inside the Drum Rack. All mixing must be done internally in Addictive Drums 2.īy default Addictive Drums 2 has its own MIDI mapping preset called “AD2 Standard”.

2ch preset - All separate outputs have been disabled, and all sound comes out of one stereo channel in Live.

You can determine the final balance of the sounds with Live's mixer.

Post Fader preset - The internal mixer of Addictive Drums 2 is still in use, causing the presets to sound identical to the previews inside Addictive Drums 2.

This causes the native drumkit presets to sound slightly different from the previews inside Addictive Drums 2. The loudness of the channels is determined by the faders in Live alone.

Pre Fader preset - This preset disregards the internal mixer of Addictive Drums 2.

When you unfold one of the project files, three choosable presets will be revealed:

als), one for users who own Max for Live, and one for the users who do not. The AD2 Suite project folder contains two project files (. From here you'll then be able to easily access the AD2 Suite project folder. alp file somewhere in your User Library, or in one of your custom folders in Live’s Browser.

Addictive drums 1 midi map pdf