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
Other than some settings not being saved properly all the time like scales and mpe settings, I'm not having any show stopping issues and I really like this app, have been using it a lot, great for soundtrack work. It's great with multiple instances too.
I did send an email about the settings and he's not responded yet, so that is disappointing yes. But I'm hoping he's committed to fixing at least those types of issues, others I can live with.
I'm having a lot of fun sequencing the app via midi, eg Poly
I don't really have an offical MPE hardware controller to test all those specific things, I have a Qunexus but's not offically mpe I don't think.
May I ask - how do you sequence it via midi?
If you set up the midi notes in Poly (or similar) as the ones in the manual you can sequence the different gains and also the trigger. Most things are midi learnable too so you can change the pitches in different ways. It's more experimental sequencing though and not like sequencing specific notes, but I like this process. It is one where you need to delve deep and it can be frustrating if you want it to do something exact. but i think it's more of an exploratory process and i really like the results.
Are you getting any of the crashes and going silent stuff that @Bon_Tempi mentioned? I am. But, only if I'm trying to externally control any of the gain stuff via external source or LFO. Not absolutely show-stopping, but fairly annoying.
Rarely or not often, I can't remember the last time I crashed but it has happened, not for a while though and I've been using it daily for hours. Seems to have improved stability since that update.
There does seem to be times when the midi notes in stops working though but then if I change some settings on the mpe area it gets it going again.
Hmmm... I get them somewhat often. I think I'll try exporting my presets to save, and then try re-installing. thx
I hate to do this but I’m still having trouble with it even loading as an audio unit and have emailed the developer to get no response and unfortunately I think I’m going to have to ask for a refund. I know my device is old but it’s advertised that it works on iOS 12.4 and I’ve just got crickets from the developer
Ok - thanks for the hints ... will give it another try and maybe try to dive a bit deeper - let’s see if I will change my mind by spending some more time ...
How do you midi learn with Fundamental without any midi settings?
Still having problems with crashing with multiple instances. I just tried to open a 2nd instance, it immediately killed the first and yet the 2nd refused to open. I also tried to use on a smaller iPad and saw for myself the sizing problem. This is really a very serious issue, I must agree. Both of these are extremely serious issues. Emailed dev...
I think, maybe, the problem is related to opening a second instance while the first is triggered.
@Gavinski Lots of problems with this app. Looks like a poor port of the PC/Mac version. Hope the developer replies to our emails and will fix all issues, the app is worth it.
Problems indeed. @Pierre118 hope so too. I had faith initially they would be sufficiently resolved, looking unlikely. Still usable but the workarounds are really annoying.
And no, after more experimenting I see that whether or not the first instance Is triggered cannot stop a second instance crashing on opening. It’s just buggy as hell.
The problem is that the developer was very responsive the first few days after releasing the IOS version but at this moment it's only silence. He doesn't reply at e-mail (anymore). You have the same experience?
This is the first email I’ve sent in more than a week, let’s see what happens. I guess they were flooded with emails and complaints probably. @Pierre118
I was also getting some very erratic behavior. I opened a 2nd instance to check whether it'd crash or not, and it didn't... but I got a new issue: I couldn't tune any of the oscillators below about 170hz. When I tuned below 170, then the pitch began to rise, as did the pointer graphic. Closing and reopening the session fixed it.
Best policy everyone is just to report all problems to dev immediately and follow up after several days if no reply, use app store ratings and review if necessary after first giving the dev ample time to fix things or at least respond
Now, I'm finding there are far too many clicks and pops in vintage mode. Adjusting oscillator gain settings with oscillators tuned from 1hz - 20hz produce artifacts that completely ruin any musicality of the app in this range. They occur when the envelope is moving osc gain, and when your finger manually adjusts it. I think this might have something to do with wavetable interpolation.
Will do. I really like this app.. but there's a number of things that need to be improved upon. First.. these audible artifacts are really not acceptable. 2nd, workflow and UX enhancements like drag left/right for fine tuning oscillators.
You can midi learn the AU parameters.
I've been using multiple instances without crashing so it's strange it's not so stable for others.
I'm currently on ipadOS 13.7 if that makes a difference. I'm also always at 1024 buffer.
Yeah he's probably not used to the surge of support requests, maybe he's taking a break...hopefully he'll be back online soon.
Yes, and it might be a somewhat depressing situation if some of the things are not fixable which seems a possibility.
I can manage with it as is, not ideal, but ok. I don’t regret the purchase, but then I’m not a performing musician, and grabbing loops from single instances in AUM is fine for me. I have used the contact form on the devs website to suggest, if he hasn’t already, that he check out this forum, and maybe even post something here in light of the well documented issues. We can but hope...
Yeah, I can also manage UX and UI issues. But those clicks and pops, even using the internal envelopes should be sorted out. Can't even grab a clean loop or sample with some settings.
Ah, I hadn’t thought of learning the AU parameters. Thx
I’m on iOS13.7 too, but I just checked apeMatrix and it’s set to 256. Will try 1024. I’ve never understood the buffer setting and when it should be set higher. Seems like I get the crashes and losing audio when I’m externally controlling the gain settings. I bet the solution is the buffer setting that you mentioned. Thx 🙏
@skiphunt
Buffer length is the amount of time you allow your cpu to do the required processing.
Shorter buffer means lower latency (which is what you as user want), so you can record audio/midi without detectable delay. The more complex the task becomes - lot of plugins, or cpu demanding plugins being used - the harder it gets for the cpu to deliver within timeframe. Once it can no longer deal with the task, audio dropouts, crackles will occur. To deal with the dropouts, you have to increase the buffer, giving your cpu more processing time.
Since it's always a balancing act, common practice is to use the least possible plugins when you are recording, so you can do it without noticeable delay, and increase the buffer for mixing, to give your cpu enough headroom for all the plugins you want to use.
Worth noting that this is critical for those who record stuff (midi or audio), because that's when you're the most sensitive to latency/delay (hit the key, hear the sound). If you're drawing midi or programming patterns it's hardly an issue. Also some people more sensitive than others. I'm good at 128 for recording, but I know many keyboard players who like it shorter. I rarely go above 512 even for mixing.
I think 1024 requirement is too high, but with this type of instrument it's not necessarily a dealbreaker because there are no sharp transients, well defined notes etc, so few milliseconds won't be noticeable.
After a couple of hours of intensive fiddling with Fundamental and a Sensel Morph with a custom Buchla overlay (the devs recommended MPE controller) I think I can categorically say that single note pitch bend (which equates to frequency changes in Fundamental language) DOESN'T work. No matter how I set up the MPE parameters in the app any movement on the x axis of a key that triggers an oscillator (assigned to pitch bend on the Morph) results in a change in frequency on multiple oscillators.
Still love the sounds that I can wring out of it, but the continuing instability, UI problems and preset structure (or lack of it!) is taking a bit of the shine off...
Thanks for the update @enkaytee confirms what I have been suspecting for a while
I can confirm the sound cutting out sometimes, on the vintage model. Then if I switch to pure engine the sound works, but switching back to vintage doesn't work and the vintage model won't sound again until I reload the AU.
@Carnbot are you also experiencing those pops and clicks when the osc gain is moving (manually or via envelope), with tunings from 1-20hz?
edit: more like dial-up tone actually.