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.
Zeeon crashing in AUM
I’m still on iOS 13 and recently whenever I load Zeeon into AUM the synth crashes. Anyone else experiencing this?
Comments
All good here. iOS 13.7 Air 2 and iPhone 7.
Reboot?
Yup. No luck.
Have you tried starting it standalone?
Mines Fine - iPad 6 2018 - iOS 13.7
Delete and reinstall is another step after the first 2 already mentioned, however be sure to backup presets.
Didn’t work.
Are you perhaps on a Zeeon beta via testflight ? If a beta’s time-period runs out starting the app will just crash without further notice...
I‘m on IOS 13.6 and Zeeon AUv3 v1.54 loads fine in AUM v1.3.8 on my iPad Pro 10.5.
.
Edit: Now i realize, you already even tried to re-install, so it seems to be the App Store version. Who iPhone/iPad you are running AUM/Zeeon on ?
6th gen 9.7in with iOS 13.7.
When I try to load it in standalone, it says it's loading the Audio Unit (I guess that's normal as it's in a shell or wrapper?). In AUM, it loads for a second, then I open it and it crashes and says
BPST: Zeeon failed.
Audio Unit plugin invalidated.
Maybe @giku_beepstreet should have a look at the problem.
What is really strange, is that it seems to work for Poppadocrock using the same hardware (iPad 6) with the same IOS version (13.7).
Could you check for the AUM and Zeeon version numbers (in the app store, have a look at the version history) , even though i expect both to be current.
.
The standalone implements an AUv3 mapper, that loads the plugin.
.
Some more questions to narrow down the problem
I can confirm the "Loading Audio Unit" message in standalone.
Just another suggestion: If you've created any user presets, try loading one of them in standalone.
Loads fine on my iPad 6 iOS 13.7.1 both standalone and AU
It loads fine in AB3. I can load other AU in AUM.
I can load my own presets fine.
At this point, you might want to try over on the BeepStreet forum: https://forum.beepstreet.com/categories/zeeon
It sounds like something in the AUv3 loading process is incompatible between AUM and Zeeon. Do you have the current versions of both: AUM 1.3.8 and Zeeon 1.54?
@slicetwo : Zeeon is working fine for me in AUM on iPad 6 with iOS 13.7.1 -- have you power-cycled your iPad (fully powering down then starting it up)?
Many times.
Yup
Ugh. Do you get a crash log when this happens? Does it offer any hints? It might be helpful for the dev even if not for you. I'm not sure if these events get logged, just guessing. If you're not familiar, logs are at Settings –> Privacy –> Analytics & Improvements –> Analytics Data. Zeeon will be right at the end.
I don’t see any logs for Zeeon. Bah.
I updated to iPadOS 14.1 and now even standalone Zeeon crashes... ugh. My favorite iOS synth is now useless. It does still load in AB3, which is weird.
Zeeon isn't working in AUM for me tonight, for what I think is the first time ever.
As soon as a MIDI note gets sent in, it crashes AUM.
iPad 6th gen and iOS 14.1
The strange thing is, I thought I was using it in AUM with no problem either last night or earlier today... with the same iOS version, etc.
edit: I just figured out my issue and it's working again here. I had set my Buffer size in AUM to the max 2048 frames this afternoon while recording many tracks simultaneously. Setting it back to 512 frames where I had it before makes Zeeon play normally again. Maybe that's helpful information?
So that did fix it, but I’ve always used 2048. I wonder what the deal is.