Assigning a plugin to a pad forces it into submix – a featur

Yeah, the submix definitely sucks. But there is a reason for forcing pads to it. Say you put an insert on a pad. Then you sequence that pad on two or more different tracks in the same sequence. The problem that would come is that the software wouldn't be able to determine which track to send the plugin audio too, especially if the tracks are triggering the pad at the same time. This would likely destroy cpu performance and cause major software instability. Nonetheless, it still sucks, but was necessary!

Which means there won't be a fix/change for this in 1.7 ? You don't have to answer…

My way around the assign plugin to pad issue is to just use the track mixer and only have all different sounds on separate tracks.. Esp bass sounds and all drums.. but i typically just put each sound on its own track thus allowing me to use the insert effects in a way that is much more viable for the workflow.

problem with that is lots of people program their drums live on one program. i don't like to program one pad at a time.


thats why we're praying for track explode in 1.7 !!!!

fdodds wrote:problem with that is lots of people program their drums live on one program. i don't like to program one pad at a time.


thats why we're praying for track explode in 1.7 !!!!

You can copy the initial performance. Then copy, paste, delete per track after that.

That's the way I've been doing it, even JJos has track explode (in a different name).