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.
Glowing Audio Clips
Hi,
Can someone point me where to best read up on why, after starting to add midi-lean (computer keyboard) bindings to my project, I'm starting to see glowing/flashing audio clips during and after playing through parts of the project (ie: when the clock is paused or playing).
Guess it could be related to something else, but since the last major update I did was via the midi learn UI, I'm guessing it's something caused by the changes I made there.
Thanks very much
Comments
Please post a demonstration.
Don't have an easy way to share a video at the moment and wasn't able to find a way to attach here, so shared it via your support email, so should be in that inbox. Thanks
Can you post screenshots of the button actions? I am not 100% sure
Sure, here you go.
I’m trying to keep the stepped dial setting in sync with the button that’s pressed, whether the button is pressed directly via the touchscreen or via midi-learn binding…wonder if there’s a recursion/infinite loop that’s caused.
But not sure how else to keep all these things in sync.
Or is there a side effect from the Cancel action?
@danm: what happens if you remove all the actions besides the play actions?
Removed the Cancel Count Ins/Outs action and the Scroll: Stepped dial action (leaving only the play action) from the 3rd button from top (IntroWLead button) and from the 2nd button from the bottom (ChorusWBacking button), and then went back and forth playing these 2 play groups by pressing the buttons and no more glowing.
So, then I added back just the Cancel Ins/Outs action and still no glowing.
When adding back the Scroll: Stepped dial action too, the glowing returns.
Recursion issue?
Here’s what the stepped dial action looks like
Continuing to experiment...adding the Scroll: Stepped dial action back in to the button, but adding it as the first action and adding the Cancel Count Ins/Outs back too, but now as the 2nd action, and keeping the Play action as the 3rd action...this also removes the glowing issue.
But it also changes how the buttons react...instead of both buttons flashing when I press the next button, the next button just "lights up" as soon as I press it (even before the play action takes effect at the end of the prior play group finishing) and the current button turns off it's shading immediately
Here's screenshot of the action order I described above:
@danm: can you post screenshots of the dial setup and actions?
Nevermind. I see them
@danm : that stepped dial setup seems problematic. it is recursive. what purpose is it serving?
@espiegel123...
I’m trying to keep the stepped dial setting in sync with the button that’s pressed, whether the button is pressed directly via the touchscreen or via midi-learn binding...not sure how else to keep all of them in sync.
What are you using the dial for?
If state feedback is on for the dial and you remove stepped dial triggering from your buttons, does pressing the buttons result in the dial step changing?
If not, I suggest that you restructure your dial so that every other step is empty. In your actions, set the dial to the blank step and have the actions in the next step and use nudge to trigger the actions.
See:
https://wiki.loopypro.com/Stepped_Dials
thanks @espiegel123.
I've read that wiki page numerous times and will do so again.
Before I try to restructure things...
Can you elaborate on this, I'd like to try making sure "state feedback is on for the dial and remove stepped dial triggering from the buttons" to see if "pressing the buttons result in the dial step changing".
I know how to 'remove stepped dial triggering from the buttons', but can you explain exactly how I'd make sure 'state feedback is on for the dial', in the way you're recommending, please
Thanks
State feedback settings for a widget are accessed via the gear wheel when you have the widget open for editing.
Currently, Stepped Dial state feedback is "Disabled".
Are you recommending setting state feedback on the stepped dial to "First Action" or "All Actions"?
Thanks
Your dial steps have only one action. So, it won’t matter. When it doubt, try both options.
@danm
This works, thanks