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
Yes, I don't think this is an issue of the amount of RAM (I've run this through my devices and many simulators and in all of them I see about 150mb used, similar to the desktop version of Beat Scholar).
It's more likely that this is a more nuanced problem I need to handle internally once I 'see' the crash. Probably just some feature or system call I added at some point that is failing at runtime where I didn't proper add a fallback for these devices in case the feature is not found.
Usually Apple's dev tools and sanitizers are good at warning you (me) that this might happen - but they don't always do that.
I appreciate you going so far to test @eyalamir
Alright, my 2018 device got here this morning, and yes - it definitely did crash here and I was able to figure it out. Version 1.6.9 should be out shortly on the App Store, let me know if it solves your issues!
Hi. I just updated to BS 1.6.9 on iPad 6, iPadOS 17.7.10. It's working fine both stand-alone and as AUv3 in AUM. Nice work and thank you.
(I'd love to know what the problem was, and why it affected different devices and iOS versions differently.)
Great to know it works!
The problem was indeed related to a few 'big' memory allocations (around 16mb each) that are happening during startup for the sampler voices.
For reasons I don't fully understand yet, iOS sees those allocations happening very quickly and decides to just stop giving the app the requested memory, even though the device itself has plenty of memory left.
I can see it very clearly happening on the iPad 6 but not in any other device or simulator - so my guess that it was some hardware or firmware safeguard in case apps are allocating uncontrollably that was removed in later devices.
The fix BTW was to make those preallocations a bit smaller which should only be problematic if the samples you load are really long, over 20 seconds.
Fixed. You rock bro
I wonder if this is what’s happening with ButterSynth @kirnu ?
Yay. The second update to fix startup crash has resolved the issue for me. iOS 17. 👊🏻
Fixed for me on 15.2!
Awesome, thank you for testing, and please let me know if any other issues come up.
There will also be an update coming soon to the older app, which is identical just with a message that tells users to switch to this version. Sorry about the inconvenience!
Now works fine in 15.8.2.
Thank you!
Perhaps we could all leave this app a nice review in the app store as a thank you to the dev who went to the trouble of fixing the problem. Only takes a few seconds...
Thank You @Simon, @eyalamir, @uncledave
.
Bug fixed, and now I’ve worked out what’s going on, it’s a blast! Great stuff.
Last update fixed the startup crash issue on my ipad 5th running 16.7.12. App sound and works great!
I’m super confused by the dual versions now on my ipad. I understand the going free part, but why create a completely separate app? Why not just make the original app free? Will this new app always be free? Is there any features/kits/presets added or subtracted in the new app? Will both apps be updated and maintained?
If you go back and read what @eyalamir said, they did not have a choice. It was because of the App Store rules. I would suggest you remove the old one from your device.
Here’s the comment: https://forum.loopypro.com/discussion/comment/1446018#Comment_1446018
Hi, ok…that’s cool. I somehow missed that. Why did the new app have bugs that the old app apparently didn’t have? Does the new version have features/fixes that aren’t in the deprecated version?
I dunno! Why don’t you ask him?