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.
Select Prev/Next Button Widget
Hi All,
I know how to setup midi and/or computer keyboard to select prev/next audio clip, to select the clip and also know how to setup mappings to play/record the selected clip.
What I'm wondering about is if there's a recommended way to select next/prev button widgets on a page.
I do know how to map specific buttons on a page to specific midi/computer keyboard triggers, but wondering if there's a "next/prev" for button widgets on a page, similar to the "select next/prev" functionality that exists for audio clips.
Thanks
Comments
It sounds like you're saying you'd like to have a button on a controller to be able to trigger whatever button you "select"?
There's no action to change the target of a midi or computer keyboard trigger. You can do this using a stepped dial though. Set each step of the dial to trigger the widget you want. Then map something to the scroll action of the stepped dial to nudge it up or down one step.
[edit] this doesn't sound exactly like what you want now that I read through it more carefully.
Normally, changing the target of a midi message would be done through profiles and you would use the "Step forward or backward through profiles" action to do it.
There could be better ways, so best to wait for the expert to weigh in.
Thanks @wim. I'll wait to hear what others have to say.
Basically, I want to do this because I have buttons I use to trigger song parts and would like to not only be able to trigger a specific button/part by sending a specific midi signal or computer keyboard press (ie: press number 1 to play section/play group 1), but also be able to send a midi signal or hit a computer keyboard key to press (or take some action) on the next or previous button on the page.
Thanks
The word "select" applied to widgets is tripping me up a bit. There's no analogue between selecting a clip and selecting widgets.
There is only ever one selected clip, and it's a possible unique target for actions. There can be any number of widgets of several types, so what would the context be for "selected" widget?
What you really want to do is change the target of a midi or typing keyboard event. I get that if you're thinking of a single set of widgets doing a single thing it seems like that's the "selected widget", but the term doesn't really fit in Loopy Pro's context.
I hope that makes sense.
Sure, where I'm saying "select a button", we can substitute "have an action triggered on a button widget" or "press a button widget"...I'll edit my prior post to reflect this change in verbiage
No need to edit anything. I just wanted to make sure that terminology didn't muddy the waters too much.
Okay. Looking forward to hear if anyone has any thoughts on this, Thanks
There is no inherent notion of selected/current/next/previous widget. You could accomplish that with a stepped dial that you nudge to trigger widgets in a particular order.
Stepped dial with nudging works well, thanks very much @espiegel123 and @wim.
When set to "active page" the actions of the stepped dial should be able to trigger widgets that are not on the same page as the page where the stepped dial resides, ya?
Seems so, but just wondering as I'm seeing some unexpected behavior there...not a big deal as I'm flexible as to which page I put the stepped dial, but just wondering bc I can do some more testing and report my findings if this may be a bug.
Thanks
Side note: You can also nudge a stepped dial with it press gesture. I sometimes do this so that I can just tap on the dial rather than dragging on it. That backfires a bit if you move your finger though. So what I sometimes do instead is add a label below the dial, then set the label's press action to nudge the dial. As long as I remember to tap the label instead of the dial, this works well.
Sorry, I don't know the answer to your question about active page.
Interesting, great tip, thanks!
Are you saying that tapping the label works better bc if you try to tap the dial there's more of a chance for a misfire since the dial can react to either press or nudge?
When you talk about active page, do you mean when midi learning?If so, see the manual’s explanation.If you mean something,can you explain more and perhaps illustrate with a relevant screenshot or screenshots?
What unexpected behavior are you seeing?
Yes. Or a button, of course, but that takes up more room. Another benefit is you can leave the name of the dial empty and then the value shows inside the dial and is more visible rather than at the bottom of the dial. I find it works nicely visually.
Thanks @wim. Yes, @espiegel123, I'm talking about when midi learning...when I first tried it, seemed like the dial didn't work unless it was on the same page as the buttons it was triggering. But, I can double check and follow up with you if there seems to be a specific issue, but sounds like there's no known issue you're aware of
If the dial triggers widgets on other pages and works , the issue was probably that your midi binding to the widget was not set up correctly. Active page means the dial will only be triggered by midi when the page it is on is the visible page.