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.
Cykle broken after update (OS13.3) - but now fixed!
Cykle won't open in AUM or Drambo after Cykle update. In AUM "failed to communicate with helper app" and in Drambo just "error". I'm pretty pissed off as I had a number of sequences in AUM I put many hours into. I saved most of them, but that's no help if the app won't open. If the update is not compatible with earlier OS', the dev should efin say so.
Comments
If the dev is even efin aware of the problem. Have you reported it?
Developers aren't able to keep a pile of devices around with older operating systems on them to test. They only have the simulator, which may not behave exactly like the real thing.
After Cykle update or after your iOS update? If iOS update it’s likely got nothing to do with the dev and more to do with apple. So no reason to be pissed at them.
I’ll check on my iPad in just a bit but I’m assuming you’ve already contacted the dev about it?
I found an email for the dev and informed him. No one else experienced this failure?
Has to be the app update. You can't update to iOS 13.3.
Apologies if it wasn't clear: after updating Cykle.
The odds of anyone still being on iOS 13 and using Cycle are pretty low. Maybe someone will pop up, but it might take time.
I admit my initial reaction was a little harsh. As I wrote above - reported to dev
That's understandable. It's frustrating when things break from an update and iOS provides no way to roll back.
I was mainly trying to point out that it's likely the developer isn't aware of the issue. I should have done it without the snark though.
I assume there's a reason why you're not updating iOS. Unfortunately that's going to lead to more and more of this kind of issue as time goes on. If you're going to freeze the OS then it might be wise to stop updating apps as well. Keeping the device off of the internet might be a good idea as well since there could be security issues with such an old and unsupported version of iOS.
Thanks and please do!
Wise words and I've mostly stopped updating apps, but with quite a few new features, I couldn't resist the Cykles update.
My ipad is 5th gen and mostly works smoothly - obviously with more CPU limits with newer apps - so that's why I haven't updated from 13.3. I use it pretty much only for iOS music making apps.
Cykle was released in 2019. My iPad was 2 years old at the time. I'm sure there were quite a few folks with older devices who purchased Cykles upon release. The implication here is you have to buy a new device every 5 to 6 years to maintain functionality of apps released 4 years ago. My desktop DAW on Windows 7 is now 10 years old and runs some 4 year old plugins with no problems.
I'm running an iPad Air 2 purchased in 2015. I'm running iOS 15.7.6 and it performs as well or better than it did on iOS 13. So, I don't fall in the category of people you're implying update hardware regularly.
But neither of us has data on how many people are out there with the combination that you have and neither of us know how many of those belong to this forum and would notice your post.
Time will tell. I hope you get your answer and a fix.
I’m on an Air 5 (the 2022 one with M1) and on both the latest OS and Cykle update and all is well on my end.
I can confirm that it’s not working on 13.7 either as an AUv3 (AUM and Drambo). Seems to be launching fine standalone.
@ElectroHead
Try restarting your device - after reboot it’s loading fine here in both AUM and Drambo (13.7).
Restart didn't fix the problem on my device. Again: "Couldn't communicate with helper app." in AUM, and "Error" in Drambo. Opens standalone.
Still no response from the dev
Dev got back to me with a very informative response. Now communicating with him to help him find the issue.
also broken for me on 13.7
Did you try a reboot?
unfortunately, I'm not able to reproduce the issue since I don't have access to an iOS 13 device and Apple already deprecated the iOS 13 runtimes in Xcode. is there anyone encountering this problem who would be willing to reproduce and send a crash log my way? (I don't see the issue pop up in my crash logs, so I guess affected users have their App Analytics settings disabled)
The issue was fixed with the latest update, which is great. Big thanks and Kudos to the dev @cp3, not only for this great app and fixes, but for a quick response when I got in touch with him.