1. IMPORTANT:
    We launched a new online community and this space is now closed. This community will be available as a read-only resources until further notice.
    JOIN US HERE

(Phase-save) Layering of Kicks (Snare, etc.) without using the same midi note

Discussion in 'Feature Suggestions' started by Goldstein, 23/4/11.

Thread Status:
Not open for further replies.
  1. Goldstein

    Goldstein NI Product Owner

    Messages:
    159
    Hello,

    I'd like to see a feature for a basic thing that came into fashion:
    - using multiple kicks instead of just one: one with ooomp (lows), one for snap and another one more dry/middle.
    - usually they play together and get processed and mixed independent

    So because we need to keep these 3 kicks separately availabe too with their midi notes (let's say C1, D0, C0), we want some some of midi router / splitter in front of the drum machine. So let's see we send a signal on Midi note B0, then this signal gets sent to C1, D0, C0 and each kick gets its own output. Like that we still can also trigger just one of the kicks, for example if we want to play only D0 in the verse, etc...

    Of course this could also be done by the DAW, but doing it inside Battery would free the DAW from things like having 3 tracks, etc. But workaround ideas for DAWs are welcome for this (I currently use Presonus Studio One) and sometimes other DAWs.

    I'd like to see this built into Battery.

    Greetings,
     
  2. djdsk

    djdsk Forum Member

    Messages:
    234
    Hi Goldstein

    I also suggested this , you can at the moment just select 3 pads onto one midi note so you could put 3 layers for a kick onto C1 for example . The only problem is when you begin to use the Humanize effect in SETUP it gives every sound a different value . So if using timing the layers come out of sync . Id like to see this changed as i also want to use it like this .

    Also if using layers like this then the volume , panning etc must be able to be changed relative and not just absolute like it is now.
     
Thread Status:
Not open for further replies.