slicing into 128's
Posted: Wed Feb 05, 2014 12:33 am
Hi there,
I am trying to create a setup which makes slicing multiple drum loops directly into 128's more seamless, but I seem to get stuck, and before I resort to M4L, wanted to check here.
Basically, 128's are done by having a single drumrack with each drum cell hosting an instrument rack containing up to 128 chains with different samples that can be selected using the chain selector control (mapped to macros on the outer drumrack). The problem is that this works fine for the traditional way of selecting a bunch of individual sample files and dropping them into the inner instrument rack.
If I slice a drumloop though, it always creates a drum rack which doesn't have chain selector. The workaround here is to put a pitch device (as chain selector) in front and group both devices into an instrument rack, so far so good.
Once you try though to drop this instrument rack into the outer drumrack, Live recognizes that there is a nested drumrack inside the instrument rack, and directly maps all the cells in the outer drum rack to the cells in the drum rack therefore bypassing the nesting. So rather than sending C3 to drum cell 1 and on to instrument rack 1 as well as C#3 to drum cell 2 and on to instrument rack 2, all the different notes go to instrument rack 1.
Next idea was to NOT drop the 128's instrument into the drum rack but leave it on a different track while routing the midi from the central track with the drum rack per cell to the different tracks. But there seems to be no way to route midi from a drum cell to a different track, only routing externally (external instrument) is possible. Haven't tried that yet, so the other final option seems to be to have "send"/"receive" M4L devices in the drumcells/tracks respectively. which I will try tonight.
hope the problem is clear, and there is a native way to do that. I actually don't mind the fact that the central drumrack and the individual 128's sit on different tracks as this aligns quite nicely with the slicing workflow which creates a different track per sliced loop anyway.
thx Nick
I am trying to create a setup which makes slicing multiple drum loops directly into 128's more seamless, but I seem to get stuck, and before I resort to M4L, wanted to check here.
Basically, 128's are done by having a single drumrack with each drum cell hosting an instrument rack containing up to 128 chains with different samples that can be selected using the chain selector control (mapped to macros on the outer drumrack). The problem is that this works fine for the traditional way of selecting a bunch of individual sample files and dropping them into the inner instrument rack.
If I slice a drumloop though, it always creates a drum rack which doesn't have chain selector. The workaround here is to put a pitch device (as chain selector) in front and group both devices into an instrument rack, so far so good.
Once you try though to drop this instrument rack into the outer drumrack, Live recognizes that there is a nested drumrack inside the instrument rack, and directly maps all the cells in the outer drum rack to the cells in the drum rack therefore bypassing the nesting. So rather than sending C3 to drum cell 1 and on to instrument rack 1 as well as C#3 to drum cell 2 and on to instrument rack 2, all the different notes go to instrument rack 1.
Next idea was to NOT drop the 128's instrument into the drum rack but leave it on a different track while routing the midi from the central track with the drum rack per cell to the different tracks. But there seems to be no way to route midi from a drum cell to a different track, only routing externally (external instrument) is possible. Haven't tried that yet, so the other final option seems to be to have "send"/"receive" M4L devices in the drumcells/tracks respectively. which I will try tonight.
hope the problem is clear, and there is a native way to do that. I actually don't mind the fact that the central drumrack and the individual 128's sit on different tracks as this aligns quite nicely with the slicing workflow which creates a different track per sliced loop anyway.
thx Nick