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 StoreLoopy Pro is your all-in-one musical toolkit. Try it for free today.
LP:how to:? launchpad x /multiple instances/ separate instances from each other
hello,
does anybody have a clue, how to block different instances of loopy pro in aum trying to affect the launchpad?
the situation:
i have two different racks of loopy pro build up in aum.
one is for the launchpad x and the launchcontrol xl to be cliplaunching and processing the material.in fact i just rebuilt the knobs digitally and everything is mapped and works fine.
the second rack is for one shots and master effects, not be touching the midi signal of the devices in any way.
just being used via the ipad touchpad.
but it does.as soon as i play a one shot it shoes up in the launchpad device.
and i have to manually reattach the loop of the first rack to the knob.
is there any way i can block the second rack from doing anything with the launchpad device, but still have the first rack working? same for the launchcontrol.
this would give two persons the possibilty to play a live set over one ipad.
i appreciate your response.
Comments
In loopy pro’s Control Settings, turn off Automatic Bindings for the Launchpad. That should solve the problem.
thank you.i tried, but it still attaches the knobs to the launchpad.
might there be a way to set up different inputs via aum ?like different channels f.e..how might that look like?
What exactly do you mean that it attaches the knobs to the Launchpad?
the second photo and the third are mixed up.
first everything is fine, as soon as i add a one shot clip( here in orange) f.e. my launchpad starts to reorganize.
is there a possibility to set it back to normal after adding clip buttons or to prevent them from affecting the launchpad?
any trick.setting off automatic binding seems not to be working.
goal is to , in the end have my lpx and lc xl controlling the loops and an maudio oxygen 25 controlling the one shots, plus ,if it works ,an extra page for usage on the ipad for more one shots and fx.
thx
sry, it shows the buttons on the launchpad, but ones that i dont want to have there and shuffles my buttons on the device itself.
might one way be to erase all bindings and setup completely new after all buttons are made? would this be stabile?
Can you post screenshots of all the relevant screens...AUM routing matrix, Loopy Control Settings to show what profiles are active and then the profiles themselves? I am having trouble understanding how everything is set up. If you have set up bindings to the Launchpad session mode pads and the profile with the bindings is active then the buttons you bound to the Launchpad will show up on the launchpad.
I think I understand what’s happening – you added a one shot to the very top left of your project, which has interfered with the display on the launchpad. The LP maps the launchpad buttons to the screen is via their position – so the top left button on the launchpad will link to the top left clip in your project. If you add that one shot to the top left of your project, that’s going to affect the mapping. If you don’t want that, then you’ll either have to add it below the other clips, so it doesn’t push them over on the launchpad, or turn off automatic mapping altogether and bind it manually only to the clips that you want.
thank you.ill show when i completed the button setup.i left aum out now.
think i understood now that when i add a clip button this will show up in the launchpadsession view on the device( in my case even without automatic bindings) and when i erase the bindings and bind them new ,the launchpad should give me the correct bindings in colour and, erm, button displayed on the device.
is that correct?
thanks for your time , defi:)
It definitely shouldn’t happen if you have automatic bindings turned off, but yeah, once you bind manually, those bindings should stay put as long as you’re using a project profile, and not a global one. (https://loopypro.com/manual/#profiles for details)
the orange group is for my midi keyboard.
i want to use it as a clip launching device with some effects on the knobs and the start/stop function.
the group up right represents the launchpad x, the buttons i want to use.
the group down right represents the launchcontrol xl
the master on the right is just touchpad use.
Cool! Yeah, you’ll definitely want to bind that manually, and do it in the project profile
that is page b
it would be just for touchpad use.
it is mostly clips which will be affected by effect buttons.
i tried it a lot now.as soon as i play clips they start to show up in the launchpad device and shuffle my midi bindings.
the buttons seem to be one " row" further and the not bound clips that have been played show up on the launchpad in colour as soon as they are launched.
my question would be how to avoid those clips just for touchpad use to do some thing to the launchpad or the midi keyboard.
it is just one profile and the backup to it.
i turned off automatic bindings.still seems to lead to the exact outcome.
ill try around and give report.
You’ll have to turn off automatic bindings, to do that. I may be misunderstanding the question though
It would help us have a more complete picture if you posted screenshots of your Control Settings panel (so we can see what profiles are active) and then of the profiles themselves.
thaaaaanks a lot.
ill get going.ill tell if it worked. thank you so much.
is any out good or do have choose certain ones?do i prefer the daw outs or the midi outs?
@roggmanatee : now show us what is in the current project profile and the global profile.
You might want to do a web search about how to make a screenshot on your device. It is easier and better resolution than taking a photo of the screen.
sounds like a long night.ill just manually attach the bindings in projects and leave global untouched.
i might annoy you with some further questions during the process.:))
first would be if it might be possible to
" duplicate" the clip representation of my launchpad to , lets say a 2nd page and have the complete rack playing a different
loop-set after for example pressing a button that switches the midi binding to this particular set? it would not be necessary to have this visible on the screen, it would just have to switch to the loop -set.in fact it would be cool to do it without having it affecting the ipad screen.
this would make it possible to play a very big amount of loops in one session and to switch the launchpad loop set via button while still playing stuff via the touchscreen.
page 3 with " block" 2 and 3
for example:
switching the page.and switching through " blocks" on a page.
i would like to know if it is possible to go through these different loop-sets by button without having the touchscreen showing the changed page.and to handle them like "blocks" to switch through.
lets say the colours are mixed up, so it would show up differently on the launchpad then.
don' t know if this sounds stupid but the technical idea behind it would be
to block out every other button grid-"block" and just allow this one to be fed a midi signal to from a specific device, so only this would show up and be playable( and visible on the device).
sounds like a good choice for live playing options.
like " hey, this person made a ten hours live set just from one project"-style.
maybe this possibility already exists.
i might have missed this in the manual.
thx:)
@roggmanatee : when you set up a manual binding, normally the MIDI is being bound to a particular instance on a particular page. If you do that, the launchpad button will stay linked to the item on the original page. So, if you switch pages in Loopy, the pad stays bound to whatever clip you bound it to, even if it isn't on the current page.
Without seeing the profiles you have set up, it is hard to advise you about the problem you are having with with the two different Loopy instances and their bindings to your controllers.
thx, that was the answer i needed.
maybe it would be useful to create a possibiltiy to switch bindings in a particular page, so that you could have setup one page per midi device and can
choose between different sets in this page by switching a button.on this page this would make it visible in witch block you are working.
thx for your time:)
i erased all global bindings and stick to just one project now that i manually bind.
i will have a backup of it.
There are actions to enable and disable profiles. And a follow action for each page if there is more than one.