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.
MIDI Bindings, “This page only” "active page” How to use them?
I’m setting up an array of MIDI bindings now in Loopy Pro. The bindings screen offers two options “This page only” and "active page”. I assumed this meant that if, for example, I set CC60 to control a widget on Page A and chose “This page only” that means it won’t affect the same binding on Page B. I tested it with a widget on each page. I tested again with Active page.
The results I got are counter-intuitive. The widgets on both pages were in lockstep when both were set with “This page only.” Setting to “Active page” and they were independent.
It seems like “This page only” really means the incoming control signal is not filtered based on location--the control will affect the change no matter what page is active.
And “Active page” means the control signal is blocked from all pages except the current page being viewed.
Is that right? Or am I missing something here? I searched the Forum, the manual, and the wiki and couldn’t find a straight explanation.
It would really help to have some examples of scenarios with each of these options. In my setup I have all clips and performance widgets on one page, and an array of widgets corresponding to each of my foot controllers on another page; I use those “portal” widgets to trigger widgets on the performance page. From what I gather from tutorials and sample templates this is the way to allow me to experiment with different setups (e.g. strict synching for drums vs free ambient looping) without having to re-bind the foot controllers each time. But maybe I’m over-designing and I can use “active page” bindings and a separate page for each of my setups.
Thanks,
Steve
Comments
@ThinAirX : I think you are referring to summary text that is displayed after you create the binding. It may be clearer if you think about what Loopy displays when you pick the target.
Let’s say you have a button “Do This” on every page.
If the binding says “active page”, it means that the binding triggers the “Do This” button on whatever page is visible when the binding was triggered.
“This page only” means the “Do This” button on one particular page is triggered.
Bindings to a particular target (displayed as “this page only”) don’t consider what the active page is. They are for times when you want to trigger a particular widget or clip regardless of what page is active.
When you choose targets, if you choose from a particular page, you are binding to that item in that page. When you pick from the All Pages page, you are picking something to trigger from the page that is active when the trigger comes in.
Which you choose, depends on what you want to do.
Ed, can you please explain this further? I’m struggling to understand the relationships between the midi binding options and the initial trigger setup. That all-page option is, first, not well documented (I learned about it from Michael’s tutorial) and it’s confusing because it offers up one page as the “all pages” screen. What am I missing here?
Examples would really help here.
Thanks,
Steve
Let’s try again. I had hoped my last explanation was clear.
Do you want an explanation based on using midi learn or manually setting up the binding?
All I’ve used so far is MIDI learn, so let’s start there. What are the advantages of doing it manually?
I do appreciate your efforts to explain these intricacies to dullards like me. BTW, I’ve studied a number of your tutorial vids and sample templates. I learn something every time, but I also see lots of advanced combos and features that I’m trying to ignore until I get my basic setup working smoothly.
If we are talking about MIDI Learn, let’s say I have 4 identical pages. Like this:
Let’s say I midi learn button A on Page D as shown:
This setup means “when cc24 comes in, trigger Button A on Page D”. Button A of Page D will be triggered when cc24 comes in regardless of what page is active at the time.
If instead the target is Active Page
CC24 will trigger Button A on the page that is active when CC24 arrives
@ThinAirX : does this clarify the issue?
@ThinAirX : Can you let me know if this clarified what This Page Only and Active Page mean? If so, I'll update the manual and add the video to the quick tips tutorial playlist.
@espiegel123 Yes! This is now perfectly clear. As with your other videos, I really appreciate your stupidly simple explanation and how you break it down to the barest elements. AAAA. BBBB. DDDD.
It might help for future versions to change This Page to some phrase that makes it clear. “This Page” to me implies that I have to be viewing the page for the binding to work. Maybe call it “Global.” Then Active Page makes more sense, or change it to “Viewed Page.”
Thanks for taking the time to clear this up.
Steve
@ThinAirX : I will add the information to the docs and add the video to my loopy quick tips and demos playlist.
I suspect any words used in the buttons will seem ambiguous to someone. So, I’ll document it in the manual for anyone needing further.
FWIW, to me, “Global” would imply a button on all pages rather than a particular button on a particular page. The reasoning behind the terminology is that “This page” means “link to the item on this page”.
Maybe move the word “only.” This Page / Active Page Only
I know this seems like a picky complaint, but this is from the perspective of a newbie who is already swimming in all the options and interactions of this incredibly powerful app. When I set things up following the manual and tutorials, it’s all so logical and beautiful. But then I fire it up and test and things don’t work as promised and I struggle to pinpoint the problem. That’s when such a simple misunderstanding of simple terms can lead to an hour of trouble shooting.
I’m not complaining. I’m just trying to understand. I'm also instigating a thread that other newbies coming after me can resource and help them understand.