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
Sorry @Carnbot but I don't understand. The MOONs currently have an independent duration specified in beats that doesn't affect or relate to the PLANET orbit duration. There are no time divisions in the MOON because they don't have an event timeline (As I see it, the time division only affect the grid where the events can be placed). The speed is only related to the loop duration in beats. I'm trying to understand how adding time division on the MOON could affect the speed, but it seems that I can't
Strange... in theory the "TEACH" button on the CC controller list is acting as a SOLO for that orbit. But if another orbit is using the same channel, they won't be stopped. If it can be reproduced, it's a bug!
I already have it in the list as a new option in the MOON view.
Thanks!
Hi!
We've done some work related to this
LOVE THIS
You guys are amazing !!!!
Incredibly well thought out creative swimming pool.
I'm not sure if this is just the color it is supposed to be or if moon b is deactivated... But it appears to be "off"....


If so how do I activate it ?
@reasOne That also bothered me, i tried tons of taps on various places to ‚highlight‘ moon B or activate it somehow since it is only barely visible and looks „de-activated“
Then i read that both moons are always on (so it just seems a bad color choice) and found that one can assign controller modulations to that dark gray moon B.
Selecting a different color palette than the default didn‘t help, moon B is always the same dark color, and moon A is always white.
.
@JuanB Please choose a stronger color with more contrast to the background for moon B
Hey @Carnbot , andrés here (one of the devs). Is this still happening to you in 1.0.3? If it is, can you please send a screenshot of how it looks? I don't have a 12 inch ipad, and I can't reproduce it in the 9,7 ipad pro.
Thanks!
Here it is on 12.9, which is the same size as if on a 9.7 ipad I think. But yes when you hide the tab it can't be retrieved.
I think I was able to reproduce it. In the meantime, I think that a workaround is to open Aphelian before AB. I'll check it out. Thanks for the report.
Oh good, yeah it can be retrieved if you open Aphelian first, thanks for the info
Ahhhh!!! Well that's good to know then, I'll stop looking for ways to activate it now haha! Thanks man!
Love the mooons !
@anb @JuanB when you hit the random button for sequences and/or tone maps, is Aphelian truly generating random sequences/tone maps? Or, is it randomly choosing from the library of patterns & maps?
Hi!
I wasn't able to reproduce it. What iPad and iOS version you are using?
Thanks!
Hi!
We'll consider and independent app with the synth,
thanks!
Hi!
I understand. There's a functional conflict with our plan of using MIDI IN notes to control the notes of the map (like a classic arpeggiator), but we'll think if something could be done about this.
It make's a random sort of the selected notes using the current map layout.
And it saves the seed to maintain the selection in the future.
Interesting. So, the more you use it... the more saved seeds of random sort... and the more random results you get?
I’ve been getting this as well. iOS 12.1.1 and iPad mini 4.
Gen 6 (2017) iPad (128 GB) running 11.4.1.
I also frequently get a crash if I press the + button to add a scene while a scene is playing.
At least visually there is no indication that the key (like D has changed) or that the chord (like 3) has changed either. Even when reinstalled.
No, just the last seed is saved in the project file. And it's used to regenerate the selected random shape when the project is loaded.
@espiegel123 @Angie
The crash occurs when you are trying to change the note map from here?
Hi!!
The generator has 2 steps, the first sets the piano "buffer" in the middle, the second applies those notes to the pianos of the orbits. The key change is not changing the values of the "buffer piano"?
It changes with both visual and sonic feedback WHILE I’m on the page for both areas, the piano orbits and the buffer, but has no indication of what it was changed to after changing tabs/pages and the revisiting the generator page. And just to be clear the individual orbits while on other pages still shows the notes used. Hope that makes sense.
My assumption was that I can change keys in each scene as well as what notes are played like 3, 5 etc as well as custom “chords” and that they would be kept in each scene.
Yes
Yes had a crash last night trying to change the note from there in midi mode sending out to NS2.
IPhone version???
Ok, glad to hear! Thanks. 🙂
Are all the MIDI niggles sorted now?
Had Aphelian sending to 4 tracks inside NS2 yesterday no problem. Had one crash however after selecting a tone map change via the secondary panel.