Sign In:     

Forum: Wishes and new features

Topic: Deck Merging
So let's say you only play on 2 decks and on deck 1 you have the drums and then deck 2 you have the new track but the drums are underwhelming so thats why you put a loop on deck one. Now you think the song sounds better like this but since you only have 2 decks you have to kill deck 1 eventually.

Here I present you: Deck Merging

You merge deck 1 into deck 2 and it keeps the slider values and loop that you have applied to deck one and their value changes proportionally to the changes you make on the new deck merge. So now you have a free deck again! I think ideally it should only be activated when theres a loop present.
 
Posted 2 hours ago
If you are combining drums from both decks, you probably achieve that with a deck move (Deck 2 > Deck 3) and then activation of Dual Deck on Deck 1 (might have to change some mappings for pads for that to work, as the dualdeck operation in a lot of cases has to be explicitly specified in the script if I'm not mistaken).

If you are replacing the drums of deck 1 with deck 2, you can use the Stem Swap Sampler (record the drum loop from from deck 2 into a Stem Swap Sampler bank, go to that bank on deck 1, and trigger the replacement).

An extension (not sure if it is already possible) would be to make the Stem Swap sampler layer instead of replace (which would do the first suggestion more directly and without the use of an extra deck).
 
Have you tried it?
 
you've just invented moving the sampler output thru a deck. Which we can do.
 
So you're saying you can create a sample on the fly from a loop, and then play that sample on a loop on the desired deck?
 
hang on, you haven't even invented that, you've invented turning the stems for the drums up.
 
🤨 Do exactly what I said on the fly and then Ill believe you