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
I second this, adding Pace and Rule controls.
Also, already mentioned (small) color variations between playheads would be neat UI improvements.
well you can't really make your own scales can you. it's just a list of arbitrary scales. why not just have a keyboard where you can mark your scales. plus, microtonal scales are what I'm after and ZOA certainly can't to that. it's stuck with 12 tempered tones
It would be useful to have some good-sounding presets. I’m hearing some nice demos, but everything I’ve tried so far has been very bad, not even close to what I get out of Xynthesizr.
I think Zoa is primarily a MIDI generator, so it's limited to 12 "notes" per octave. You'd need a microtonal synth to reinterpret those notes.
No presets?
@rygrob
Ryan, been loving this app!
I ran into something this morning..
attempted to open a project I was working on last night, where I had a TWO instances of ZOA, each doing different things in an AUM project.
Evidently, when I saved the project in AUM it only saved the data in ONE of the instances, and copied it to the other.
Im not a coder or developer, so I have no idea what it would take, but being able to save different data in individual ZOA AU instances in a project would be a must.
@rygrob
And after using ZOA more, I’ve started to understand it more, and understand your reasonings for having certain things where they are. Please ignore any feature requests that may lead you away from your vision or concept of the app.
I just tried this in Audiobus, two ZOA instances (A and B in Audiobus parlance) with different configurations, feeding different instruments. Saved a preset, force-quit AB, reopened, and reloaded the preset. Both instances came back correctly, so no problem. If he can verify this happens in AUM, Ryan should maybe contact J.Liljedahl.
Confirmed. Saved AUM project with 4 differing instances, re-opened and all were the same.
I would like to be able to use a preset system. In standalone I am learning the app and creating some ideas I'd like to save.
A similar thing was happening with the free Audiomodern apps (Filterstep and Gatelab, though it might have been just Gatelab) initially. This was fixed recently, so it may be something to do with ZOA.
Shoot, OK thanks for the tip! I think I know why this is happening. Should be able to get a fix out in the coming week.
I didn’t find any, and monkey clicking fails to produce anything usable. If one doesn’t want to watch the instruction videos, probably Xynthesizr is the better choice.
Found with Id700 you can equalize moving the ends. Kind of musical. Reminds me of using generators when I first bought ipad.
I need better headphones ( quality at lower volume ) Think I hurt my ears with frequencies. Not with id700.
I just put my progress on the velocity/CC converter script on patchstorage, URL and notes below…
https://patchstorage.com/zoalocity/
WiP that converts channels of notes given out by ZOA into velocity and CC values. I’ve only implemented layer two so far, leaving layer one as default notes, while two can be set to either notes, (control value 0), velocity (control value 127), or and CC in between those two values…
You need to set up ZOA so that it transmits the second layer on MIDI channel 2 - maybe this input and output can be further implemented as each layer has four knobs right now, with a further two available for each - I’ll see
Sounds cool.
It seems to work just about ok so far, though seems like some things don’t respond as well to cc control as I’d expected; DRC seems really good at receiving CC though…
Will have to listen when you made it Krupa
Thanks! that sounds useful. I've been having some success using other Mozaic scripts such as Velocity Randomizer and the ingenious Midi CC Morph Pad to quickly change things like the root note, scale, etc. on the fly.
By all means, give it a go, I’m not likely to touch it for a day or two now as it’s sleep time before work begins again tomorrow 😁
Yeah I guess it’s just not for me. I was hoping it would be more open ended but it’s too much of a one trick pony to be of much use to me.
Color-coding the dancing dots from the playheads has already been suggested, but I realize that there's a problem when they overlap. It might be more useful to show only the dot for the currently selected playhead, so we can understand how it is traversing the grid. Then have a "Show All" button to restore the current mode.
Thanks for the quick reply!
Why does it send out a morphing pattern of notes. Then reduce to not many. Then not respond to toggling off/on auto spawn?
The morphing pattern follows the rules of the Game of Life. Try slowing down the pace of Life; I'm using 2 bars. The playheads still find plenty of variety even though the grid isn't changing.
It reduces to not many because that's how the Game of Life tends to evolve. And I agree that Auto Spawn should be smarter about detecting a repeating situation. You can tap the Respawn (R) button to force it.
Respawning would be much nicer if we could have a density slider, the current one activates way too many imo.
Yeah this would be good for sure
@rygrob
I just noticed a funny conflict between ZOA and AutoPad. AutoPad ignores Note Off messages, and takes a second Note On on the same note to turn it off. Now, ZOA sometimes outputs the same note twice. When AutoPad receives this duplicate note, it silences until the next note arrives, creating a gap in the pad drone. Easily fixed with a little StreamByter glue, but should the playheads maybe have an option to suppress duplicates?
Update with +/-24 semitones range , nice