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
In AUM in your case.
Same here. iPad 7 as well as 6.
Ah - so i’m not alone with the OneShot! crash on preset change in AUM (IOS 16.2, iPad Pro 10.5). It could be a memory issue, but only partly.
If AUM is playing and some notes (from Octagon) arrive to trigger sounds in OneShot, then changing the preset will 100% crash. But if i stop the incomming notes and wait another 15secs after OneShot got silent i am able to change presets without the 100% crash. There might be an additional low memory restriction, since it might crash after the 5th to 8th preset change.
Another hint migth be that this crash only happens in AUM - if i build the same setting in apeMatrix or Cubasis, i am able to change OneShot! presets, even the its playing the incoming notes.
I also found a second mystery with OneShot and AUM. After preset loading with the above wait-work-around, AUM is inresponsive for about 5 to 10seconds. I can‘t move the window, press transport icons, the keyboard etc - but while AUM kind of hangs, i can interact with oneshot and turn its knobs and even preview the slots… I assume that there is some miss-alighment with the threads and something OneShot is calculating after loading a preset runs in AUMs context and thereby blocks it until finished… This also does not happen in apeMatrix or Cubasis.
I didn‘t yet have the time to send these bug-reports. My first bug-report for OneShot v1.0.4 is still in stasis (got their reply that didn‘t fit my report. Therefore i re-stated the problem but didn’t get any feedback) .
Thanks. Increased it to 1024, same thing happens
This app is unusable for me, in its current state
@Kashi Can you try to simply wait 10-15sec after the last sound was played by OneShot and then issue the preset load ?
That‘s what works for my AUM / OS! crash-problematic as described in my post above
Contact Klevgrand and send the crashlogs. which can be found in the IOS settings app (search for Analytics)
Send in a bug report on the Klevgrand support page. We need to get a fix prioritized.
I can easily get the standalone to stop working while changing preset, after a few successful preset switches before this happens. The preset window box does not respond when I tap on a name, nothing happens, I wait for some seconds, still nothing. I then tap on the bottom keyboard, and the screen just goes black. I can only see the top row menu (midi settings etc) - I can even tap here and get some dialog window, but the rest stays black.
I also experienced that AUM unresponsive behavior.
It is puzzling if this has not been a problem for many others since launch?
Thanks @espiegel123, I found 6 OneShot reports there and added them to my support request now.
I could see the report mentioning sigsegv Kernel invalid address, that sounds like a memory bug. I could also see in the stack trace many calls to Juce:paintComponent, that is likely related to my black screen behavior, but unsure whether it is cause or effect. Let’s hope Klevgrand can fix this without having to rely on an update to the Juce library.
Will give this a go, thanks
However, it’s still freezing in standalone mode, exactly the same thing described by @bleep in post above.
Done 👍🏼
My experience has been that hosted in AUM, OneShot crashes somewhat less often (iOS 18) while standalone it removes the central window every time when doing anything to move off the default empty preset.
iOS 18 aside, on an iPad 6 running the last release of 17.6.x I can’t change a preset more than one without it crashing both hosted and standalone. Latency settings are at the highest in host, it took out Loopy Pro entirely regardless.
I’ll send an email to Klevgrand about it, it’s nice to see that I’m not the only one seeing crashing
If only the desktop version could export to a .ospack file.
You might try buffer settings below 1024. Some apps puke on 1024 or 2048 buffer sizes. Developers actually have to remember to add support for these buffer sizes as the libraries don't support higher buffer sizes by default.
Is there a recommended range of buffer sizes to test for a generally stable setup? Or should defaults suffice?
(Unfamiliar with buffer sizes other than seeing them talked about. Never touched em, don't know if I should/why I would. So just a general 'testing range' would get me started)
If you have Mela 5 it also has midi curves for velocity and another module with knobs for the same. And that’s on top of all the other midi modules, recorder, and synth.
There's no rule or set testing range range, as what ultimately works depends on how powerful each device is and how much else is going on. The only exception is as I noted above - sometimes (thankfully more and more rarely) apps puke on 2048 or even 1024 buffer size. Sometimes that turns out to be the reason for otherwise mysterious crashes.
Other than that, it's straightforward. Lower buffer means less latency at the cost of higher CPU. If you start to get dropouts (crackling audio) it means your CPU is overloaded and you need to raise the buffer level to keep the current app load. The actual CPU % isn't a reliable indicator on the iOS/iPadOS platform, and there's no way to predict how much a device can handle. Trial and error is the only way.
Testing specific buffer sizes can be helpful for getting an idea of how it affects your work, but your numbers will rarely be directly applicable to someone else's projects.
Ahh thanks for this, I do have Mela 5. Stupid question but which module do I find this in? Sorry I’ve hardly touched Mela. Still on the lists of apps to learn
Ooohhhh ok wonderful thank you! All makes perfect sense!
Should you not expect to be able to play notes and change presets at the same time? please excuse my music production ignorance.
create an initialized instance.
click on the + button on a lane.
select midi processor
and select velocity
hope that helps
Thnaks so much for that! Yes this is what I was trying, with a modulator targeting the Velocity module however I'm not sure I could hear much of a difference. I may be a bit out of my depth with the midi stuff so no doubt it's me!
You just need to route midi from your sequencer into the Mela velocity module and then out to OneShot. Twiddle the dials. It works I use it all the time for other stuff.
You should expect to be able to do that. I believe @_ki is simply trying to walk through methodical troubleshooting steps to gather data in order to help narrow the issue down.
I first load the empty preset to clear the memory. This helps but it still crashes less often.
There is clearly an error that it does not flush the memory before loading a new drumkit.
Yes, that‘s how it should work.
For OneShot Auv3 and on my specific iPad/IOS i tested that changing presets while playing incoming notes works without any problem when hosted in Cubasis or apeMatrix. Even for fast preset changes, one right after the other. As expected, the UI of the host is responsive after changing OneShots preset.
But (on my specifix iPad/IOS) for OneShot auv3 hosted in AUM it crashes with a much, much higher probability when OneShot is still playing sounds. If no more notes are playing plus an additional wait time and then changing the preset, the crash probability is low.
The additional effect (on my specific iPad/IOS) i am experiencing is that AUMs UI is unresponsive for about 5 to 10 seconds after issuing a preset change without crash. The only UI elements working are the ones of OneShot - it seems as if the main UI tread of OneShot is blocked while OneShot computes stuff based on the newly loaded samples.
.
Since i had found a work-around to the crashes, i did not bother as noone else mentioned crashes or inresponsible AUM host after preset-change. I really like OS and use it in many of my AUM sessions.
Thanks @audiblevideo I’ll play a bit more. Maybe I’m not exactly sure what it’s doing or what I should be hearing.
I changed the file extension from .ospack to zip, the file could actually be unpacked.
The file structure in the UNHOLYDRUMS folder looks like this:
I don't have the desktop version and don't know what the file structure of your export looks like, but creating a zip and changing the extension to .ospack should work (assuming the file structure is correct. Maybe the "30_" in front of the folder in the patches folder is important!)
That's very interesting. I'll look into that. I emailed Klev a couple of weeks ago but still waiting for an answer. This might just work.
Just got an email from Klevgrand saying that they've fixed the constant crashing thing and an update should be out soon...
I bought OneShot on sale, mostly because of the jazz brush kits. What velocity pads are you using to play it with? So far if had the good sounding results using ThumbJam. Also KB-1 and Xequence AU Pads/keys work well. What are some other options for velocity pads to play this with?
I haven’t had any crashing at all. iOS 16.6 here.
So, @ 12.99 it seems almost like a responsibility to purchase.
Love the acoustic/brush sounds a lot. Works beautifully in Octochron too