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.
Scenes not triggering in exclusive mode from another page
Hi everyone, I’m new here. I’ve been using Loopy Pro for a few years with acoustic (meditative) instruments, synthesizers, and an Akai MPC. Absolutely love it!
I recently started using scenes. My scenes (8x8 grid) are on page B and work perfectly using the solo/unsolo method.
Now I’d like to control those scenes from page A, but I can’t get it to work properly. I tried using a trigger widget:
On page B, it works perfectly (exclusive mode).
When I copy the same widget to page A, it partially works, scenes trigger, but they’re no longer exclusive. So when I start scene 2, scene 1 keeps playing instead of stopping.
If I move the widget back to page B, everything works again.
Is this expected behavior when controlling scenes from another page? And is there a way to make it work in exclusive mode from page A?
Thanks,
Deep
Comments
Please post screenshots of your widget’s actions and their action settings and a link to a screen recording demonstrating the issue.
It is working for me to solo/unsolo exclusive groups from a different page.
https://youtube.com/shorts/1Fg2jdrikXM?si=fB_gGgLbU3n4T5Vg
@espiegel123 , thanks for your reply! I add the video below. I'm curious what i did wrong..
@Deep : use the press to Solo/Unsolo in your main buttons. I’d suggest using the solo/Unsolo actions in your buttons on page A rather than the indirect method you have of toggling widgets to toggle other widgets.
See what I did in my video.
@espiegel123 First of all, thank you for taking the time to respond to me — I really appreciate it.
.
The method you described is actually what I started with… well, almost. The first thing I tried was selecting the scene buttons, copying them, and pasting them onto the new page. When that didn’t work properly, I tried creating new buttons on the new page with the same actions as the scene buttons (solo/unsolo, targeting Group 1 / Page
When that also didn’t work, I tried using a widget instead.
All three methods gave me the same result: they work fine on the page itself, but the exclusive mode stops working as soon as the buttons are placed on a different page.
I tested it with the 5x5 sample project, and there it works perfectly. But as soon as I expand that sample project to an 8x8 scene, I run into the same issue again.
At this point, I really don’t understand what I’m doing wrong. The button actions on the new page are identical to those on the scene page, and I’ve made sure that not only the group numbers are correct, but also the page letters.
Please zip your project and upload it into the thread.
Thanks so much—I really appreciate your help and input!
I use this project for live performances with a setup that includes several acoustic instruments with contact mics, standard microphones, a vocal mic, a synthesizer, and an Akai MPC. Each source has its own input, running through a Zoom L20R mixer.
In Loopy Pro, the first page functions as a digital mixer, with FX sends and a few “donuts” for quick access. The second page is set up as an 8×8 scene grid. The donuts on the right side of the scene buttons operate independently and are not tied to the scenes.
Everything works well on my system, except that I’m unable to place a duplicate of the scene buttons on the first page.
Have you tried putting separate buttons on the first page that do nothing but trigger the scene buttons? I think that should work and provide feedback too.
Sorry for not responding earlier. I took a look at your project. You have run into a bug that has been fixed in an update that we are working on.
There are workarounds. If your groups are intended to be mutually exclusive, setting them to be mutually exclusive in the group settings will solve your problem.
Also, do you really mean to have solo/unsolo behavior for the scene buttons? In most cases that I have seen, unsold isn't really used. Do you make use of unsolo?
If you don’t use unsold then you won’t have to worry about providing refunds.
@espiegel123 Thanks again for your time — really appreciate it.
I had two performances this week, and overall things went very well. I created a knob to quickly change pages, which works reasonably well. I have to say, Loopy Pro is fantastic for the kind of music I make.
It would be great to have the scene buttons from page B also available on page A, but… it is what it is. I also read that there might be a fix coming in the next update? 😀
The workarounds aren’t entirely clear to me. As far as I understand, I already have the groups set as mutually exclusive — right?
Regarding the behavior of the scene buttons: I found two approaches in the sample folder and tried both. One uses play/stop groups, and the other uses solo/unsolo. Both methods work perfectly on my system, as long as all buttons are on the same page. I don’t know about not using unsolo? i just followed the sample projekt.
However, as soon as I move or copy a button to another page, the mutually exclusive behavior stops working.
@wim I also tried using a widget button. This works fine as well, but again only when the button stays on the same page. As soon as I move it to another page, the mutually exclusive behavior breaks
Is my project a bit of a strange setup?
The goal is to perform live using all my different instruments from page A. On page B, I would have scenes with pre-recorded sounds ready to use as an additional layer during live improvisation.
If I could also control the scene buttons from page B on page A, I wouldn’t need to switch pages at all during a performance.
I really like working with a standard project. Most of my music is improvised, and if I prepare something, it’s usually only the day before. Because of that fast workflow, I find it helpful to have a consistent base project that I can rely on most of the time.
@Deepfryguy : your groups are not set up as mutually exclusive. Here is the current setup of one of your groups:
Tap the mutually exclusive icons to make the groups mutually exclusive with each other and the buttons should work across pages.
Mutually exclusive will look like this:
Ha! I had a feeling it would turn out to be something simple.
I did notice those numbers, but I assumed they meant the groups were already mutually exclusive — not that I still had to configure them myself. It just shows: no matter how well something is designed, there will always be people who don’t immediately understand it 😄
Thanks again for your patience — everything I asked for is now working!
That said, I’ve run into a small issue. During my performance yesterday, I used scenes i made the day before for the background music. When I was on scene 4, I wanted to trigger a loop from scene 3 again during improvisation (because, well… anything can happen in improvisation). That worked fine without stopping the loops in scene 4.
Then I triggered a loop from scene 5 as well. Eventually, I pressed the scene 6 button, which stopped the loops from scenes 3, 4, and 5 and started the loops from scene 6. I actually really liked this behavior.
With the new mutually exclusive setup (now that I finally understand how it works), this is no longer possible. Now, when I trigger a loop from another scene, all loops from the currently active scene stop — which makes sense, because that’s exactly what this setting is supposed to do.
What I really liked before was the flexibility to freely trigger individual loops across scenes, while still having the scene buttons behave in a way that starts all loops from that scene and stops the others.
So for my use case, the previous setup actually worked better. But in that case, I can’t have scene buttons on another page, right?
I can live with this, but………. Is there maybe still… Wel i realise I ask a lot of your time…
Play actions have an option to respect play groups or not. You can set up a binding of widget that trigger with respect play groups turned off when you w as my non mutually exclusive behavior
I think you may have misunderstood me. I'm not saying to move the button to another page. I'm saying to make an additional button on the other page.
The second button does nothing other than to trigger the first button on the loop page and to reflect its state. The button on the loop page is still doing the real work. No matter which button you use, their state will be in sync and the behavior should be the same.
I believe the issue he initially ran into is a bug in 2.0.5 that causes solo actions to only work correctly on the current page regardless of what page the button is on that triggers the action.
@wim, thanks for your time as well. I think I understand your suggestion, and it sounds like a good idea. However, if the additional button isn’t on the same page as the scene buttons, the behaviour changes—just like @espiegel123 mentioned.
@espiegel123, I’m already using the “loops play independently” setting. It seems I can turn loops on or off within a scene, and it even remembers their state when switching between scenes. However, when I start a loop from another scene, all loops in the currently selected scene turn off.
So I get the feeling I just wait until the bug is fixed, would you agree?
In any case, I really appreciate the time you’ve both taken to look into this “problem.” I love this forum and I definitely love Loopy pro!
you can create an an alternate binding or button that has respect play groups turned off for when you want to trigger another group without stopping the playing group.
@espiegel123 What I noticed during my improvisation, and what I really liked, is that I could turn a loop on and off outside of the selected scene, while the normal scene button behavior still worked.
So I’m not looking to trigger a completely different scene alongside the currently selected one. I also like it when everything refocuses on the scene once I select it again. In that sense, I’m basically looking for the exact behavior that Loopy Pro has with the default settings and “loops play independently” enabled.
If I understand correctly, you’re suggesting that I could use a button to trigger another scene alongside the one that’s already playing—but that’s not what I’m looking for.
I’ll take another look at it later. For now, I think I’ll just assume that if I want to work with scenes, I should simply stay on the scene page—and that’s fine. The way it works already is really great!
Also, if I have a piece where I use scenes without changing anything within them during a performance, I can use the “Mutually Exclusive” option. And then i can add scene buttons on page A. I would just need to adjust that in the project beforehand.
So honestly, it’s already working really well. Thanks so much!
How are you triggering the individual clips? Whatever method you use, you can turn off respect play groups. For instance, if you are doing it by touch, you could edit the default tap gesture. That way yet scene buttons can be for triggering the play groups mutually exclusively and touch will be independent
@espiegel123 Amazing. I had never really looked into those gestures before. A whole new world just opened up for me!
I’m using the start/stop method now, and I really like how I can easily copy those buttons to another page. After editing the default gestures, everything now works exactly the way I want it to. With the main buttons i can move between scenes. These buttons work now on other pages as well and they even give feedback. And on the scene page i can turn on/ off loops in other scenes without changing the running scene.
I really love how deeply you can go into Loopy Pro if you want to, while it still remains so simple and intuitive to use. That balance is really inspiring.
Thank you so much for all your answers and your patience! I really appreciate it!
Glad to hear it worked out!