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
@Gavinski Reinstall hasn't worked. Yep, will email dev in a bit. Up to the eyeballs in work and home-schooling right now! Out of curiosity, why does Polyphase appear in the "audio" menu in AUM and not, as I expected in the "midi" bit? Sorry if that's a dumb noob question. Oh, and in terms of configuring it in AUM, presumably I use the usual AUM matrix to link Polyphase with various instruments, but what about Polyphase's own midi settings? I understand how to assign things when I use it standalone, but when I use it in AUM what should these settings be? Hope that makes sense?
Another thing, when I click one of the randomize buttons at the bottom of the screen, there's no apparent way of knowing that it's been pressed. I mean, the word I press doesn't momentarily flash, or change colour to indicate that it's been activated, like in other apps,.... which is a bit baffling. Am I doing something wrong?
No, it's just like that. You will see changes in either the parameters on the right of the screen, or in the piano rolls, though.
It appears in Audio because it is an IAA and the 'midi' channels in aum only accept audio units. But weird but that's the way it is.
The instructions for how to set up PolyPhase's midi settings for aum are in my video, and also at the end of the polyphase manual. It takes a little getting used to, but is worth it. Remember to pay attention to the clock off settings in polyphase if u want aum transport to be in control. Again, this is in the manual and in my vid so I won't repeat it here but ask again if u can't figure it out
FYI: after noticing this thread yesterday, I played with Polyphase in standalone, sending midi to external synths, app swapping, etc. for about a half hour. I did not experience any issues. Then this morning, I did the same, but I hosted Polyphase in apeMatrix and then AUM, sent midi to other apps, used the internal synth, added a variety of fx apps, and again... I did not experience any issues at all. No crashing. No lost sound. Everything worked as expected in both half-hour sessions. I also played with most of the Polyphase settings too. No problems. All good from here.
I’m running the latest iOS on an iPad Pro 10.5 and all my apps are up to date.
Well an update will be released soon with optimizations and other features. I've always used a 3rd party library for MIDI, and was told Apple messed up some stuff in iOS 14.2 with respect to CoreMIDI.
If you are on iOS 14.2, you will get crashes in all apps that use CoreMIDI...you should update to iOS 14.3
Yes, my issues have all been on iOS 13.7 though. Let's see if the update helps anyway. Thanks Marcos
Thnx for testing. I wonder if this is device related in any way? For example, I am also one of those unlucky iOS 13.7 users who recently often had the problem with Aum loading and being unable to find any AUv3s until after a restart, or getting sessions opening with those weird X-ed out app icons. Unfortunately this is the reality of iOS, different OS and different devices behaving differently, and it is certainly a nightmare to deal with.
I'm on 14.3, but I still get the disappearing AUv3s until after restart. Not as often or as bad as before though. And I think I don't have to actually do a full restart. That power, home button reset move works to restore them most of the time. It's definitely better with 14.3 than is was with the 13's.
I really love Polyphase by the way. I beta tested, but only briefly and didn't really offer much feedback other than feedback on the original GUI. So, I ended up buying it instead of redeem code.
I agree that it's probably the easiest to consistently get music generative stuff from. My other fav for generative that also sends midi out is Refraktions.
Crashing all over the place for me now sadly. This is starting standalone then loading into AUM. All sync settings set correctly. Press play. Polyphase doesn’t start. Switch to app. Crash.
ApeMatrix played ok initially. Stopped transport. Restarted transport. Crash.
Audiobus 3. - will not load. press info button, dialog panel comes up “cannot communicate with Polyphase”
Mini 5. 14.3
Yeah, I think I know why. Just hang tight for the next update :]
Thanks @mekohler - really looking forward to delving deep with this app. Despite the many problems I've had, I'm more excited about this than any other app I've bought for a while...
And thanks @Gavinski for your replies
Thank you 🙏
This is what we love to hear!
Update is out
@mekohler thanks for getting that out so quickly. Sadly it still has multiple problems on my platform.
Now if I boot stand-alone before starting AUM and loading Polyphase, I get an almost immediate crash.
If I boot AUM first & then instantiate Polyphase, things hold up for a little longer but I still get sync phase jumps when navigating around. If I stop everything , reset Polyphase play head to the start position and then press play in AUM, Polyphase doesn’t crash but it freezes. Only rebooting AUM and reloading Polyphase will get things going again.
I’ve deleted and re-installed Polyphase but it’s still not at all happy.
Mini 5 . 14.3
I can confirm that there is an issue if you try to load it in AUM when it's already open...not sure what that's about, I will investigate. I already reached out to the MIDIBUS developer to ask why there is a lag in MIDI processing when switching away from the app. There is no lag when switching TO the app :[
Damn, I also just updated, even after seeing this - major freezing and crashing problems. I would recommend anyone against installing this update. I have emailed @mekohler and would encourage anyone else having issues to do so too. 3rd gen Pro, 13.7
So Marcos, should it work OK if we don't open it standalone before opening in aum, according to your experience so far?
Well I figured out the crash that happens when you start the app before hosting in AUM. It's a bug on Apple's part bcs I enabled the ability to browse the app's documents. Will disable.
@mekohler nope, I just loaded it directly in aum, getting freezes every time after a minute or two. Please start a beta group before doing more updates would be my advice Marcos
And do you get any crashes when using it standalone?
Yes
Weird, I have none and Apple's dashboard says no crashes have been logged either. I'm submitting a version that fixes the AUM crash now.
Apple’s crash logs seem unreliable, Marcos, because I remember you mentioned that previously it was showing no or almost no crashes, but as soon as I started this thread, quite a few ppl reported them. Strange!
Well, I guess I can't figure out why loading from AUM / AB when the app is already open will cause it to time-out. Sometimes it doesn't happen (for me at least). No idea if it's an issue with IAA, Audio Kit Library, AB Library, or my code.
That being said, I can never get the app to crash when in standalone. I'm at a loss at the moment. Feel free to request a refund from Apple.
For now, load the app from within an IAA host first if you plan on using it that way.
Don’t know whether or not this might be a clue or an irrelevance....but is there a reason Polyphase seems to be unique in its absence from the iPad’s setting tab ?
That setting tab is useful to have toggles like "Background Audio On", but mine are always on, so I don't require a settings section at the moment.
I reached out to AB devs, MIDIBUS devs, and AudioKit devs.
The issues I can confirm are:
1) Opening PolyPhase before opening it in an IAA Host leads to a timeout (75%) of the time (can always relaunch within the host)
2) If you open it first within the host, there doesn't seem to be an issue
4) If I build / run the app from Xcode, I never get any timeouts even If I open PolyPhase before the IAA host...this is why I wasn't seeing any issues. The debugger being connected to the app is doing something that prevents the time outs
5) Switching AWAY from PolyPhase causes CoreMIDI to lag a little
6) Switching TO PolyPhase does not lag CoreMIDI
Using the app in standalone (That means no IAA, only sending / receiving normal MIDI Messages) I find it stable and have not had any issues. No Audio drops, no MIDI lag (apart from minimizing the app)
Everything was working fine many iOS's ago, so maybe I didn't do something required with all of Apple's new bullshit requirements
I'm about to submit an open beta for all, because I'm at a loss.
Version 2.9.1 addresses crashing due to IAA hosting. There was a regression with the Snapshots though, so they crash on load
I am submitting 2.9.2 now, and then after that the releases will follow an Open / Closed beta structure. Please be patient while this app goes through some growing pains :]
In the future I may have to transition away from MIDI Clock as that seems to be too jittery when minimizing / switching apps.