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
Yeah, but I think the term “wall of text” is an exaggeration. It’s pretty concise and efficient. Igor organizes it clearly and I’ve been able to find what I’m looking for quickly and easily in the past. I just overlooked it this time. It’s right there… if it’s been a snake it’d have bitten me
Looks like he just updated the app… off to update and take for a spin
Loving the new update- much more usable.
Oh wow! Super sweet ❤️ Can't wait to run some ambiebt electric guitar chops awesome 🙌
How can I directly record the external source into my layers ?
Click on Random at the top and all the way at the bottom of the drop-down list click on Options. In the Random Options window, decide which layer you want to record into (eg Shard) and click the button that by default says Sample All. At the bottom of the drop-down menu is Input.
I wasn't sure how it worked since I'm too used to the original way, but played last night and it works like this:
Set any layer (or a combination, or all) to Input. They will begin processing external input, either from the mic, or external hardware. OR, load it into the Effects slot in a host like AUM, etc.
You can set each layer to Input, Sample, or Loop.
If you have it set to Input, it will process input... then set it to Loop and it will keep looping. And/Or set any layer to Sample and you can load in-app samples or user input samples that will loop also.
You can change any layer at any time to be Input/Loop/Sample.
This is how I played with it last night. I'd set just one layer to input and the others to loop. None of Loop layers loop until you set them to Input and process input. Or, they will loop if you set them to Sample and choose a sample. This way, I can concentrate on one layer. Once I get the input processing I like, I change the setting for that layer to Loop and it continues. I then move to the next layer, change it to Input... possibly change my input source (or not)... and repeat per layer... building a complex composition. Some layers you might choose to just use an in-app sample or user imported sample.
I haven't had a chance to play with it long enough to see if input sources, once changed to Loop, are saved if you save it as a preset.
It's considerably better this way for building compositions than ExoSphere was at launch IMO.
It's not like this anymore after yesterday's update. Much better now. See my previous post.
Thanks for letting me know, @skiphunt. I hadn’t updated it yet. Looking forward to trying it out.
Also good to know: via input recorded Loops are saved with a preset!
Are they? I haven't had a chance to try that yet. If so, that's great
That's not my experience. I recorded loops on every layer, saved as a preset. I closed aum and reopened the session, there was silence. I loaded the Preset I'd just saved, again, silence. Could u double check that and let us know your steps?
It looks like it works in standalone but not in the plugin version
Ah ok, thanks
Actually, no, it seems to work if I change presets while the app is open, but they’re not preserved across app sessions. Something similar happened with the plugin. I’d say this is a bug.
@skiphunt thanks
I’m not sure it is a bug, I think I remember Igor mentioned somewhere that stuff recorded into buffers is not saved between sessions. So I think this is the intended behaviour, though I am not sure why that would be desirable. The norm seems to be for apps to save their buffers (Gauss, Enso, Circa are 3 examples of apps that do that, off the top of my head). I would prefer it if Exosphere did save the buffers by default, or at least if there was an option for that.
Yes, sorry, I tried this in AUM, saved a new user preset with recorded loops, opened a random factory preset, and then reopened the saved one, which apparently had saved the recorded loops !. BUT after closing AUM and reopening and reloading the preset, the loops had "disappeared." Apparently, loops are only saved during one session... Too bad.
I’m wondering if it’s possible. Do you know if Circa saves the layered overdubbed samples during a session when saved as a preset?
It’s not only possible, it’s the norm, yes
Ok. Yes, I’d much prefer that behavior as well.
For ExoSphere, Igor, Soundbox, and general dark noise fans…
I recently unlocked Soundbox so that I could make instruments from my own samples and recordings. I created a personal Soundbox pack using a combination of ExoSphere recordings, blocs wave samples, and field recordings.
I then played my new Soundbox instrument into Igor’s BeatCutter app and set it up in feedback mode to endlessly generate constantly changing soundscape.
Then fed that feedback output from BeatCutter back into ExoSphere, with all layers set as constant input, and set up a 3-step sequence in ExoSphere to add even more gradual changes that slowly glide into each step.
Did ALL of this on just an iPad mini 5. Only hit 48% DSP despite all the complexity. No artifact and runs smooth.
Results were mesmerizing
Good idea. Thanks for sharing.
I was going to export my first Soundbox pack to share, but somehow screwed up and accidentally deleted all my presets sample EXO files in the process.
I also grabbed a minute of recording output, but I hit the BeatCutter template randomizer a couple times and it was decent but not as good as what I started with.
Here’s a little bit that gives a rough idea at least:
Ipad mini 5 user here, on a single instance exosphere consistently eats 50 to 60% Cpu whatever the preset, even when muting all layers or deactivating all effects. I don't know what's considered acceptable in terms of CPU usage now that some ipads have a lot of horsepower, but this is certainly the most resource-hungry plugin across all the ones I've tried. For an app that's supposed to run in background for long ambient soundscapes it certainly kills the battery fast.
Personnally I'll move to lighter alternatives, even though I quite like the app otherwise.
If you look at the audio/video post I made just before yours... I'm running an ipad mini 5 (ipadOS26.2)
I've got Soundbox loaded (huge CPU user) as instrument to play into BeatCutter (also not light on CPU) - AND, I'm running that into an instance of ExoSphere feeding all 5 layers and live processing at the same time. Not only that, but I'm running the sequencer in ExoSphere as well. And only using 48% DSP. Look at the image in the post as proof.
I ALSO had Safari with nearly a dozen tabs, mail, and X running in the background
You don't state what host you use but check the buffer first of all, if AUM 1024 when not live recording is fine.
Also, it's fairly commonly known that iOS needs a little challenge to make more memory kick in.
But, I would start with a reboot and try again, if Skip can do what he does with same iPad as yours, you obviously doing something ... not right
I use it inside Loopy Pro, and tried changing the buffer size, but even at max buffer size the CPU is still the same, oscillating from 40 to 70%. For comparison synthmaster 2 uses 5 to 10% on the same setup, Digistix 2 5%, tb reverb 5%... it seems hard to incriminate the host or the overall settings.
Did you force a restart? You might have some ghost remains, restart your iDevices often (Apple recommends). Also a filled up disk can be a problem.
Just to try , I dug up my old Air3 and in AUM with a 512 buffer added one Exo --> about 70% on the dsp meter, I changed preset (randomly) and it sunk a little. I added two more Exo's and it: 1. Sunk some more (down to 58%) 2. It works. Heavy but 3 instances is pretty good.
I think I mentioned before… I still have an old Air 2 running 15.8.3… and 2-3 instances of ExoSphere seem to run just fine.
You did, it was only because the Air3 runs A12 processor like your (and his) mini I was curious. 512 in buffer also leaves room, if I gone to 2048 I think I could have added a fourth. LoopyPro however doesn't have the same buffer option AUM do (I think).
This is a waste of my time though, going to do something better with it now 😅 Cheers!