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.
Is anyone having issues with Polyphase crashing?
I am often getting problems with Polyphase. It doesn’t see to handle app switching well. If i switch from it to others apps, it sometimes stops sending out audio, becomes unresponsive, or crashes in AUM - anyone else? Usually this only happens after a few minutes of playing and switching back and forth between AUM and other apps. It is driving me crazy. Dev has been informed but I want to see if this is a widespread problem. Is there anyone who is using the app in this way regularly - switching back and forth between other apps is an essential part of the diagnosis - who is not getting problems?
Comments
Yes. Far too often, really wishing for an auv3 update one day.
But yeah seems to happen every time I use it for more than 3 minutes or so.
@Gavinski
Thnx Uncle Dave. It does happen even after a reset. Could u interpret the analytics? If so I will send u. IOS version 13.7. I don't believe this app has any settings for choosing background audio, regardless, it can play in the background, just crashes sometimes when moving back and forth between it and aum. The dev is starting to look into it.
Please email the dev and tell him this! And ask him to add u to a beta - this app needs one
Done!
Hmmm... Not having a setting for Background Audio could be a problem, since iOS doesn't know it needs to keep running. If there are app crash logs (they'll be named for the app), you should send them to the dev; they're no use to me. If you do see a jetsam log at a time correlated with the failure, it might include a clue. You could PM me with one (only one, please), and I could see if it helps. Jetsam is basically a short-term memory shortage, and the system looks for ways to free up memory. One of those ways is to kill a process. If your app is the victim, then it could produce this result.
Thanks a lot Dave, its OK, I'll just pass on this info to the dev, that's very helpful
The beta already took place at the start of the app's lifetime. I haven't changed any core features or methodologies since then, so I'm not sure what the issue could be.
It's hard to diagnose these issues when there are so many failing points to an app (IAA, AudioKit, AudioBus, MIDIBUS, Apple's CoreMIDI implementation, etc)... We've seen Apple mess up IAA in iOS 13 and completely break CoreMIDI in iOS 14.2, so who knows what is going on. At this point the iOS ecosystem is becoming way too bloated / delicate and I don't even want to make any more apps for it.
This morning I had an AUM (iOS 14.3) session with PolyPhase, Tardigrain (AU), Ravenscroft 275 (AU), AniMoog, & Ableton Live. Constant switching between apps and the iOS home screen and I get no crashes (30 minutes and still running).
Yesterday I did change some code to lower the amount of DSP used when in the background, and fixed 1-2 bugs (nothing major). After this, there is nothing I can think of to address any issues people are having. I would need someone in NYC, in real life, to help me diagnose the code and tell me what I'm doing wrong (paid, of course) :[
Thanks for chiming in Marcos, as you know I love the app, so I hope you can figure it out.
Update: When using AUM to clock PolyPhase I did manage to get PolyPhase to become unresponsive after some time. After re-loading PolyPhase, the other instruments would not receive it's MIDI. However, Ableton Live was receiving the MIDI fine over WIFI. PolyPhase was also not able to receive clock from AUM until I restarted AUM.
So again, a CoreMIDI problem with AUM? iOS? PolyPhase?
Glad at least you had some success replicating this. Maybe someone will have some idea how to fix it. > @mekohler said:
I understand you.
Would you consider porting it to desktop (Mac)? I really like Polyphase but, as I am abandoning everything non AUv3 this will eventually be deleted from my iPad.
Yeah, sadly Polyphase jumps out of sync in AUM for me every time I app switch. Mini 5 iOS 14.3.
I wouldn’t mind a Mac / Max port either, if I remember right you had a Max device I used to use.
Crashed for me just using internal Synth in standalone after a min on iOS 14.2
Strange, I used Polyphase for a good while a couple days ago in AUM without any issues. Did a project with Ravenscroft, DRC, House Mark 1, and a handful of other apps and everything worked perfectly!
Today, I’m trying to create another new project, and can’t get Polyphase to stay alive for more than 15-20 seconds before it crashes. Same setup in AUM as before, disabling clock out in Polyphase, and enabling clock out of AUM to Polyphase. No luck, it works for a minute, then crashes.
I’m also trying to use the same instruments as my previous project that worked, so that rules out any of the instruments being the problem.
Then, I decided to try a new project, only this time using AudioBus 3.
This is the message I get:
I took a look in the settings app, and Polyphase is not listed anywhere. Maybe it just needs an update to work with these new iOS “network access” features and maybe thats why it’s crashing?
Hopefully @mekohler can chime in @Intrepolicious
I hope so, it’s an amazing app when it’s working!
Newly purchased - I love this app, I think.
My first few sessions I stayed in app and experimented with PolyPhases features. The multitrack experience is unique, responsive and inspiring.
As soon as I set the MIDI routing to Cubasis 3, and switched over to the DAW, Polyphase crashed. In fact, it seems to crash as soon as I move away from it. As a workaround, I’ll try routing midi over Bluetooth to another iOS device. But if there’s anything I can do to assist in the troubleshooting, bug reporting or beta testing: I’m in. Just let me know..
@Intrepolicious Those permissions only appear in Settings once the app has requested them, and been allowed or denied. You may need to open the app stand-alone to trigger the request popup, and allow it (if that is the problem).
Hmm, I don’t remember ever granting permission for this one. I’m going to delete it and reinstall and see what happens.
Well, when I get home later that is. Stuck at work..
The delete and reinstall didn’t work. No permission screens pop up at all upon install, and Polyphase doesn’t appear anywhere in settings.
I’ve got it running ok today by just launching Polyphase in standalone (without trying to load it into an AUM or AudioBus slot) and running AUM separately. I guess this is using “Core Midi”? Where the midi can be output in Polyphase’s midi settings set to “AUM” on each of the 1-4 channels. Then AUM accepts this midi and can be routed to each of the respective channels within.
It would be nice though, to have some AB/AUM support, and definitely would love to see this in an AUv3!
@Intrepolicious The permission popups, if any, would only appear when the app is first opened, not on install. So, it sounds like that was not the issue.
However, it's always recommended to open IAA apps stand-alone first, before connecting them to AB3 or AUM. That seems more reliable than letting the app start them. Once up, you should be able to use them in AUM in any normal way. Sounds like that's what you've done.
No problems to report from here yet. Been switching between apps and all is fine. I’m still on iOS13 and haven’t updated AUM or anything else for many months. Don’t know if that’s useful info or not.
Yes, constant crashing, in different contexts. Only bought it 2 days ago but it must’ve crashed 30 times...Really frustrating. The potential of the app is mind-blowing, but at the moment it’s unusable. Real shame.
@kashi I’m finding it totally stable when sending midi over wifi to desktop. Did you try not loading it in AUM but instead sending the midi from it to AUM from stand-alone as intrepolicious mentioned? The dev is definitely trying to work on those issues, I hope he can solve them.
Haven’t tried that yet @Gavinski - will give it a go later and report back. The main reason I got it was to use with external gear; I’ve got a Blofeld, an OP-1, an Axoloti and an Organelle. If I can get it to send midi to those bad boys and it stays stable, I’ll be in synth heaven
Just tried opening it standalone and doing what @Intrepolicious suggested. Played for 30 seconds then crashed when I touched the track 4 window. Quit everything that was open and tried it again...same thing.
Huh, if a reinstall doesn't fix that, you should definitely send the dev an email to investigate further