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.
Buttersynth hits critical DSP
Load a sample in Buttersynth, even a relatively small one, and you hit the wall. I have a 2019 iPad Pro and it can’t handle it. Otherwise, app is fantastic.
Comments
It crashes frequently. It's useless in the current version. iPad Pro 2022
If I remember correctly, the version upgrade including the iPhone version was suggested quite early in the pre-sale stage, but the impression is that it has not been updated even once.
I am considering a refund if possible.
Wow!
It is pretty stable for me on my iPad 6, though I don’t use it much with samples.
@RXQ02165 : under what circumstances is it crashing?
It probably happens when switching the WAVETABLE, soloing or muting each sound source, or editing. Since there is no autosave, I have lost patches many times.
I don't like it anymore so I don't touch it.
can you please elaborate more in detail in what conditions ot is crashing ? and eventually provide crashlog ? any detailed description may help to squash bug. Is it hapen8ng in standalone version or auv3 plugin . If plugin, what host app you use ? What is hour buffer size ? Can you provide some sequence of operation which crashes app always in 100% cases ?
there are already few crirical bugs addressed in beta (including low memory warning or crashes when host buffer size is too small, especially during switching presets, or crashes caused by granulator) - it’s just matter if time when this goes live (together with iphone version)
It's hard for me to pinpoint the circumstances under which it crashes. As I wrote earlier, when switching WAVETABLE, when switching solo mute, or when simply pressing the setting icon, there are times when it crashes randomly in any scene. It is not possible for me to explain the sequence of operations.
Again, if I knew that, I would have written that from the beginning...
This is the same whether used standalone or loaded on AUM. Also, when I was using it with AUM, it crashed just launching another auv3 audio plugin.
Is there a buffer size setting for standalone? (512freams when used with AUM)
So far, I'm using all the default settings. It's happening in both my environment (iPad Pro 2022 or mini6), so I think it's not just my environment.
It would be possible to provide a crash log, but I don't know how. And if you tell me that there are no bugs, I don't feel like I can be of much help, and it's troublesome, so I will refrain from doing so.
And are you saying that the crash when switching patches is expected?
I knew for sure that it would crash frequently when switching patches, but I'm talking about excluding that.
Settings / Privacy / Analytics and Improvements / Analytics Data
Here you’ll find a long list, but you should be able to identify the relevant one by name and date.
Yeah, I keep getting the memory error message, where it tells me to have fewer instances of BS open, ....and I only have one open!
Yes, in those items. While posting here today it seems to be creating these logs after a little experiment but it's a hassle so I'll leave that to someone else.
tap on file name to open it and then at top right corner of view is share icon... tap share to save the file somewhere (dropbox, icloud) and share here link to that file - developer needs to see content of that file
ideally save 2-3 files so it can be identified if it is same problem or mutltiple different problems..
issues you described are weird, it should not crash that much, especially not standalone version, that is quite stable
You can pick the last crashlog for each (stand-alone and AUv3), enter them and export via share (top right corner), zip and send here to dev or one of the beta testers in DM... probably that’s all you can do about it.
My situation is AUv3. Anytime I load up a sample, no matter the size, the app jumps over 100% DSP. As for everything else, normal operation.
in what host ? does it happen also in init preset ? does it stay at 100% or it is just spike ?
Yeah, I’m not a fan of this type of preset browser/preset saving system at all. (My only gripe)
And I’m kind of surprised that it only really came with 2 factory presets from the developer. (INIT and “FM Jag”) Yes, I see all of the 3rd party presets, and while they are included with ButterSynth, I don’t really see them as “factory presets”. (Maybe just me)
With what I feel like are true factory presets, you get the feeling that the developer created the preset to showcase the product’s capabilities and/or features. And that the preset was created by the only one person that knows the Ins and outs of the product better than anyone else; the developer. I think true factory presets also should be there to offer basic building blocks, or starting points to build upon.
Don’t get me wrong; a lot of the 3rd party presets that ship with ButterSynth sound amazing! I think it’s just the names though. I mean, I’m not going to publish a piece and say “Here’s my new song ‘blah blah’, made with a Jakob Haq preset in ButterSynth.”
I don’t know, I guess I just don’t believe in “factory presets” with artists names attached to them. Maybe it would seem better if they were all included without the artist names, and have all of the contributors listed in the credits/about section somewhere;
I suppose that’s a second gripe, and I reckon a second “maybe just me”!
This is totally fine though, as it encourages exploration and learning things on your own, which can be very rewarding (until it comes time to deal with that preset saving system!)
I haven’t had this problem at all. Just tried 4 instances in AUM with samples loaded in the sample and the granular slots. And never went over 42% DSP according to AUM. This is with my 12.9” M1 IPP w/1TB.
Sorry to hear you are having these difficulties @day_empire . ButterSynth is a fantastic AUv3 synth and I know for sure that Kirnu wants as many people to enjoy using it as possible (and crash/bug free too!).
Just remember, the host and buffer/latency settings you use are equally important as which iPad and OS version you own.
BS is a beast of a synth and if you turn on all oscillators, FX, polyphony, oversampling and play a complex chord you can easily cause stress for even the fastest iPad CPUs. Having said this, for more regular use I really wouldn't expect to see the kinds of issues and crashes you are experiencing on a 2019 pro.
Hopefully with a combination of details and crash reports - plus some input from Arto (Kirnu dev) - we can help resolve these issues for you.
Strange... it's not happening to me. I loaded a sample in my 4th G iPad Pro in apematrix, I'm seeing about 4%. See above.
( Only somewhat relevant, so feel free to ignore:
Also strange to me was I recently posted a question about another synth I was having problem with, and all of a sudden had people frothing at the mouth and trolling because they thought I was blaming the synth and should have mad it more clear the problem could be me.
I see no declaimer like that here, nor any of the same upset posters or chidlish reax. Can't figure out why I drew that kind of reaction, but I often do in real life also, so ain't no big thingy. Just weirdly odd and inconistent.)
More crashing and general instability here. 6th gen ipad, 2018 os 15.1.
It’s becoming very frustrating and I agree with @RXQ02165 that it’s unusable in current form.
A real shame
Can you provide a demonstration? It is enormously helpful to a developer if you demonstrate a where you show context and your settings.
Not everyone on iPad 6’s find it unstable…so knowing more can give the developer a sense of why your experience is different.