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.
Comments
Here's a potentially interesting use case that could possibly benefit from conditionals: Have track levels or automation follow strong transients from another track. For example, if a guitar or keyboard track has very prominent transients, maybe increase the velocity of strikes in a MIDI drum track.
You can hear this phenomenon in recorded material when a guitarist (for example) is following a powerful drum-fill (or vice-versa) to emphasize part of a song, such as a build up to a coda or a chorus.
In order to express this the object model for other tracks or the mix and the transient information would need to be exposed such that you could reason about it/ take action.
(I guess this is basically side-chaining lol)
$0.02 - Michael
Not sure if this has already been mentioned? Could really help with CPU management in templates when you are just freestyling
If CPU > or. < X% then Y
Examples of Y Actions… all to bring your CPU back down so you can keep going seamlessly
A. Mute/Disable known CPU hungry effects or instruments
B. Enable/Disable your preferred (high) CPU effect and enable/disable second preference (low) CPU effects
C. Bounce a midi clip to an audio clip and mute the instrument
I have successfully connected the guitar pedal Valetone Gp-5 to loopy pro via USB cable.
I can select presets using a stepped dial and forward and back buttons
It would be great to have a conditional load of a preset for an action that would let you choose a preset with a stepped dial and assign that to a button.
For example I want to assign 4 presets quickly using the radial dial and then when you long press a button it would load that preset into the selected button.
The condition would be “if preset is selected with the Stepped dial, on a long press,load that preset into the selected button” (kind of like saving radio stations in your car)
Then I could have 4 different tones that I can quickly set up to 4 preset buttons (A-D) selected wth the stepped dial rather than have to program them in.
Having text labels appear on buttons would be helpful. If preset 20 is selected then 20 would appear on “GP-5 preset A” as “Preset 20”
Looking forward to the conditionals launch.
Cheers
Don

example screen shot of GP-5 on right side
“And I’ll add the ability to hide pages soon. “
Also the ability to simultaneously view multiple pages would be great.
I like to “hide” all my state dials on a page so i don't see them on my main page but when i’m programming what all my widgets do i have to keep jumping back and forth between them to see if my dials are behaving how i want them to
I'm sorry to have made trouble here.
https://youtube.com/shorts/oxK1AaYE8Cw?si=smv36cqvOYULO4Tu
As a one man band musician, all four limbs (and occasionally mouth) are utilised to create music simultaneously. Therefore an efficient workflow that streamlines interaction with the iPad screen is desirable. Of all the available apps, Loopy Pro is easily the most flexible/creative platform I’ve come across on IOS to achieve this and my current setup serves my own needs beautifully! This latest feature opens up soooo many new possibilities for streamlining that my brain is hurting (in a good way!) I totally get why some are ‘weary’ (me too!) as it could easily add a level of complexity too great for some to comprehend but based on his previous form I have complete faith in Michael’s ability to implement this new feature in a user friendly way. The video above demonstrates this principle perfectly!
Thank you Michael
Right, I call this one “snapshots” but I’m not sure conditionals will solve it. I get LP perfect and I want to capture the state and be able to put it on a step on a dial. One press and done. A boy can dream!
+100. I was going to write the same thing.
Oh it's going to open up some insane abilities , but as with all software only a small percentage of power users will use them to full potential. The rest ? Well it's going got give Michael and Edward some doozie support puzzles to untangle!
I hope there will be a global "By Pass conditional processes" for trouble shooting! ;-) ie
"Bypass Conditional Processing IF I'm clicking around like I dont know what is going on" ;-)
I too, hope it isn't impeding the more general development of LP... especially the release of the desktop version which IMO is the big jump for LP.
Not sure if mentioned above but I’d love the ability to have a sort of shift feature. So action happening on condition that a certain button (shift) is pressed.
Conditionals won’t make Loopy Pro more difficult to use. You won’t need to use conditionals if you don’t want to. They open up new possibilities without making the existing capabilities more difficult to access.
They open the door to making ready-to-use complex workflows. Most people won’t use them directly. Conditionals enable us and and other project developers to create projects that people can use out-of-the box.
A while back, I posted an RC-30 emulation because a number of people wanted one as they are used to its workflow. I was able to do it by using (many) stepped dials to implement conditional logic. It was a ton of work. Even though the workflow seems simple, an RC-30 (and most hardware loopers) have a lot of conditional behaviors. If conditionals had been available, it would have taken much less time to put together and it would be easier to modify and adapt.
Conditional midi out is supported too I guess? That would make LP3 a nice Bome Midi Translator replacement for some of my stuff...
I’m an example of a diligent user daunted by the complexity. Even before discovering this thread initiated by Michael, I’ve been grumbling to myself that LP is another example of software that is so advanced, so responsive to user requests for features, so powerful and flexible, that casual users like me choke on the creeping complexity. There are so many instances when a feature, an action, a function shifts meaning, or disappears altogether, depending on the context. So what happens is I struggle to add a feature, it doesn’t work, I post here, and Ed or Wim or some other kind soul patiently shows me what to do and explains the context, and I feel silly for missing such an “obvious” solution. Also, some of the descriptions are ambiguous—example: I still have to guess when faced with “"This Page Only/Active Page when setting a binding.
I’m awed by the power of LP, and constantly impressed by what it can do when I finally get everything working. I’ve migrated everything in my setup to LP—things I labored to get to work in AUM are easy in LP. I don’t need MIDI Designer anymore. So I’m not whining. But I am agreeing with Wim above:
Here’s a suggestion. If you want to add tools for template builders, hide that functionality in a professional layer of some sort. For example, the way Logic Pro lets users turn on or off the Advanced Settings panel. There are so many times when I’m staring at a list of options where I’m faced with options for special-case operations that are appreciated only by advanced users. It would save me time and aggravation if I could cruise in Normal Mode and not be faced with all those permutations and combinations.
Here’s from Logic Pro settings:
