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.
Strange Stepped Dial behaviour
For every NEW inserted Stepped Dial, I get a strange response for the FIRST press of the Stepped Dial (see the picture for a simple setup):
The FIRST press will NOT move the Stepped Dial from position ONE to the next (second) step. BUT if I move back to the first position (after the first press), the Stepped Dial move to the next (second) position.
Is this a known bug? 👀
Comments
What do you mean by 'press'? Is this the action for the press gesture of the widget?
I tested in the latest Beta version and it's working as it should. I then reverted to the App Store version and it behaves as you describe. So, I'd say yes, this is probably a bug that will go away with the next update.
nvm. I was mistaken. The current beta also displays this behavior. I'll report this over on Slack.
@espiegel123 beat me to it, of course. 😂
It looks like the issue is only the very first tap after the dial is created.
Yes - it’s the action for the press gesture of the widget.
It is. And if you, for instance, put a “start-record” in the first step, the Stepped Dial will trigger record. But if you tap the Stepper Dial from the first position next time, the recording will NOT start.
So this MUST be a bug… 👀
Can you clarify? Are you saying that you are encountering an issue at some other time than the very first tap after you add the press action?