Loopy Pro: Create music, your way.

What is Loopy Pro? — Loopy Pro is a powerful, flexible, and intuitive live looper, sampler, clip launcher and DAW for iPhone and iPad. At its core, it allows you to record and layer sounds in real-time to create complex musical arrangements. But it doesn’t stop there—Loopy Pro offers advanced tools to customize your workflow, build dynamic performance setups, and create a seamless connection between instruments, effects, and external gear.

Use it for live looping, sequencing, arranging, mixing, and much more. Whether you're a live performer, a producer, or just experimenting with sound, Loopy Pro helps you take control of your creative process.

Download on the App Store

Loopy Pro is your all-in-one musical toolkit. Try it for free today.

Changing a MIDI track's action dynamically

SystemSystem
in Loopy Pro
This discussion was created from comments split from: Loopy Pro 1.1.2: Loop Peel.

Comments

  • BruquesBruques

    This might be the wrong way to ask, replying to this, sorry if so, but while you're here(!), Michael, am I thinking about this wrong, is there yet (or is there in the roadmap planned) a way via follow actions to change a midi track's destination dynamically, so I can potentially have just one midi input channel and a number of synths and a selector thingy in the UI. Currently I pair midi tracks and au instruments, and use buttons to mute and unmute pairings. I wonder if some day there might be something elegant akin to but even better than ableton chain selectors? (actually need to try replacing the number of buttons with just one of the new widgets with multiple snapped positions on it instead). PS thank you greatly for incredible software.

  • MichaelMichael

    @Bruques said:
    This might be the wrong way to ask, replying to this, sorry if so, but while you're here(!), Michael, am I thinking about this wrong, is there yet (or is there in the roadmap planned) a way via follow actions to change a midi track's destination dynamically, so I can potentially have just one midi input channel and a number of synths and a selector thingy in the UI. Currently I pair midi tracks and au instruments, and use buttons to mute and unmute pairings. I wonder if some day there might be something elegant akin to but even better than ableton chain selectors? (actually need to try replacing the number of buttons with just one of the new widgets with multiple snapped positions on it instead). PS thank you greatly for incredible software.

    Thank you!

    Not just yet, but definitely do add an item to the roadmap - roadmap.loopypro.com

  • espiegel123espiegel123

    @Bruques said:
    This might be the wrong way to ask, replying to this, sorry if so, but while you're here(!), Michael, am I thinking about this wrong, is there yet (or is there in the roadmap planned) a way via follow actions to change a midi track's destination dynamically, so I can potentially have just one midi input channel and a number of synths and a selector thingy in the UI. Currently I pair midi tracks and au instruments, and use buttons to mute and unmute pairings. I wonder if some day there might be something elegant akin to but even better than ableton chain selectors? (actually need to try replacing the number of buttons with just one of the new widgets with multiple snapped positions on it instead). PS thank you greatly for incredible software.

    You could use streambyter or mozaic as a middleman if you don't mind putting your synths on different midi channels. If you set each synth to a different channel, you could send your midi through them and have them rechannelize midi in response to a message you send.

  • espiegel123espiegel123

    Or, you could route your controller to all synths and ise follow actions to mute all but the synth that you want to record...that will also free up a lot of CPU since muted synths don't use any audio processing time.

  • BruquesBruques

    @espiegel123 said:

    @Bruques said:
    This might be the wrong way to ask, replying to this, sorry if so, but while you're here(!), Michael, am I thinking about this wrong, is there yet (or is there in the roadmap planned) a way via follow actions to change a midi track's destination dynamically, so I can potentially have just one midi input channel and a number of synths and a selector thingy in the UI. Currently I pair midi tracks and au instruments, and use buttons to mute and unmute pairings. I wonder if some day there might be something elegant akin to but even better than ableton chain selectors? (actually need to try replacing the number of buttons with just one of the new widgets with multiple snapped positions on it instead). PS thank you greatly for incredible software.

    You could use streambyter or mozaic as a middleman if you don't mind putting your synths on different midi channels. If you set each synth to a different channel, you could send your midi through them and have them rechannelize midi in response to a message you send.

    Unfortunately not but thank you. I'm playing Linnstrument so MPE so using all midi channels all the time.

  • BruquesBruques

    @espiegel123 said:
    Or, you could route your controller to all synths and ise follow actions to mute all but the synth that you want to record...that will also free up a lot of CPU since muted synths don't use any audio processing time.

    thanks, so sorry for the continued thread hijack, but just to clarify then, is that the case then that a muted synth uses no processing? (unlike in daws of years past the channel being muted wouldn't stop it using processing if receiving midi).

  • FriedTapewormFriedTapeworm

    That is correct. I have a template that I start all my songs with. It has enough synths to crash the project 3 times over loaded, and they are all routed to the same midi controller. I inmute what I need to record, then mute and unmute others to add different instruments. It is honestly the best feature in LP for me personally, as I never have to make any midi connections. Just open the project, unmute instrument of choice, and start jamming.

    @Bruques said:

    @espiegel123 said:
    Or, you could route your controller to all synths and ise follow actions to mute all but the synth that you want to record...that will also free up a lot of CPU since muted synths don't use any audio processing time.

    thanks, so sorry for the continued thread hijack, but just to clarify then, is that the case then that a muted synth uses no processing? (unlike in daws of years past the channel being muted wouldn't stop it using processing if receiving midi).

  • espiegel123espiegel123

    @Bruques said:

    @espiegel123 said:

    @Bruques said:
    This might be the wrong way to ask, replying to this, sorry if so, but while you're here(!), Michael, am I thinking about this wrong, is there yet (or is there in the roadmap planned) a way via follow actions to change a midi track's destination dynamically, so I can potentially have just one midi input channel and a number of synths and a selector thingy in the UI. Currently I pair midi tracks and au instruments, and use buttons to mute and unmute pairings. I wonder if some day there might be something elegant akin to but even better than ableton chain selectors? (actually need to try replacing the number of buttons with just one of the new widgets with multiple snapped positions on it instead). PS thank you greatly for incredible software.

    You could use streambyter or mozaic as a middleman if you don't mind putting your synths on different midi channels. If you set each synth to a different channel, you could send your midi through them and have them rechannelize midi in response to a message you send.

    Unfortunately not but thank you. I'm playing Linnstrument so MPE so using all midi channels all the time.

    Then I suggest my muting technique. As long as you are only playing one synth at a time, it works great. My main MIDI/synth template has more synths than my iPad 6 could handle all on at once, but I only record one at a time. I have a button that cycles between the synths. If I were to create it now, I'd use a stepped dial.

  • BruquesBruques

    @FriedTapeworm said:
    That is correct. I have a template that I start all my songs with. It has enough synths to crash the project 3 times over loaded, and they are all routed to the same midi controller. I inmute what I need to record, then mute and unmute others to add different instruments. It is honestly the best feature in LP for me personally, as I never have to make any midi connections. Just open the project, unmute instrument of choice, and start jamming.

    @Bruques said:

    @espiegel123 said:
    Or, you could route your controller to all synths and ise follow actions to mute all but the synth that you want to record...that will also free up a lot of CPU since muted synths don't use any audio processing time.

    thanks, so sorry for the continued thread hijack, but just to clarify then, is that the case then that a muted synth uses no processing? (unlike in daws of years past the channel being muted wouldn't stop it using processing if receiving midi).

    gotcha, thanks both. i will do that. and with a stepped dial to select.

Sign In or Register to comment.

© Vanilla Keystone Theme 2024