Quantize mute/solo

oscillotus

Hi! Is there a way to quantize the mute and/or solo button in LP so the action starts after a defined number of beats/bars? A bit like in GR-2?

espiegel123

@oscillotus said:
Hi! Is there a way to quantize the mute and/or solo button in LP so the action starts after a defined number of beats/bars? A bit like in GR-2?

See the action timing section in the manual’s Actions section

https://loopypro.com/manual/#actions

Also:
https://wiki.loopypro.com/Actions_Tips

wim

@oscillotus said:
Hi! Is there a way to quantize the mute and/or solo button in LP so the action starts after a defined number of beats/bars? A bit like in GR-2?

If I understand correctly, you're asking about quantizing the results pressing the actual mute buttons in the mixer? Not directly, but effectively yes, using actions as noted above.

oscillotus

Thank you both for your help, I will look into actions tonight!

oscillotus

Alright, so I think I get it! From what I understand, this needs to be setup individually for each audio track? This means, if I add a new AUv3, I need to add a new button and set it up with the new track? Or is there a way to automate this so it doesn't disrupt jamming flow too much?

wim

@oscillotus said:
Alright, so I think I get it! From what I understand, this needs to be setup individually for each audio track? This means, if I add a new AUv3, I need to add a new button and set it up with the new track? Or is there a way to automate this so it doesn't disrupt jamming flow too much?

I assume you're wanting to actually mute the plugins, and aren't recording to loops that you could just stop in a quantized manner?

What I like to do to minimize setup time is add several "dummy" plugins with everything already set up, then just long-press in the mixer and select "replace". I use StreamByter (Inst.) as it's lightweight and won't make sounds if I route something to it by accident. When you replace like this, all routing, actions, etc. are preserved.

Another way to go is to route your plugins to colors and monitor through the colors rather than the master. In that way you could have colors set up with mute buttons/actions in advance, and just route your new plugins to them.

wim

You can also have a single button set up to mute "Next Selected Color", which will prompt you for which color to mute. That's two taps rather than one, but might be the tidiest option. Again, you would want to have the plugins routed to single colors with monitoring and output done through the color rather than the master.

oscillotus

@wim said:

@oscillotus said:
Alright, so I think I get it! From what I understand, this needs to be setup individually for each audio track? This means, if I add a new AUv3, I need to add a new button and set it up with the new track? Or is there a way to automate this so it doesn't disrupt jamming flow too much?

I assume you're wanting to actually mute the plugins, and aren't recording to loops that you could just stop in a quantized manner?

That's exactly it.

@wim said:

@oscillotus said:
Alright, so I think I get it! From what I understand, this needs to be setup individually for each audio track? This means, if I add a new AUv3, I need to add a new button and set it up with the new track? Or is there a way to automate this so it doesn't disrupt jamming flow too much?

What I like to do to minimize setup time is add several "dummy" plugins with everything already set up, then just long-press in the mixer and select "replace". I use StreamByter (Inst.) as it's lightweight and won't make sounds if I route something to it by accident. When you replace like this, all routing, actions, etc. are preserved.

Oh I didn't thought about that! This might work for me as well! Thanks for the idea