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
Gonna go ahead and add one more shameless plug for Droneo!
Is this an evolving synth for an EP noodle?
Still no-one testing if they can get per note pitch bends on mpe? I have one other seaboard user who confirmed they can't either. Anyone else?
I'm at the point where I'm thinking I'll have to abandon the idea of an mpe video altogether....
@oat_phipps Can I clarify what your point is: U don't regret buying it but it doesn't do what you expected, and you prefer Droneo, is that right? What were you expecting it to do btw?
No luck with my seaboard but maybe I am doing something wrong.
I bought this last night. Kinda surprised the layout stuff isn't fixed yet. But, I knew that going in.
I played with Droneo again for a little while to see if that need was already met. Very similar, but I like the interface control better in Fundamental, it's a little more intuitive.
I can't for the life of me figure out how to use mpe controllers like KB-1 and Mononoke Pads with it. Any suggestions? Is this described well in one of the current videos? I can't seem to control it from any external controller. I must be doing something wrong. This actually works right?
I tried to get it to work with kb-1, I can't. I got it to work with Velocity kb but not with per note pitch bends. Same problem on seaboard. I'm. It that familiar with kb1, maybe I'm doing sth wrong but I don't think so.
In Velocity kb I have to send channel aftertouch to y axis, otherwise I get no sound. This should be triggered by activating 'press' in kb-1 I think, but it's not working.
I'm not willing to waste any more time on this, sadly.... someone else can figure out how to get proper per note pitch bends. It has taken up far too much of my time already and is frankly just getting annoying...
Thanks for trying. I don't believe you are, but the dev would disagree
I thought I saw someone controlling it with Mononoke Pads, but I could be mistaken. That's what I tried first. KB-1 is fairly refined at this point, so if that's not working I'm going to have to assume there's something wrong with Fundamental.
No regrets (yet)
In case it might help I reverse engineered the Buchla Fundamental overlay map for the Sensel and these are the main notes / cc numbers which can be used in Midi control apps to drive Fundamental at least a bit! Full MPE is another matter and I think it's likely that the implementation is flaky to say the least....
Fundamental mapping
A2 = osc 1
B2 = osc 2
C3 = osc 3
D3 = osc 4
E3 = osc 5
F3 = osc 6
G3 = osc 7
A3 = osc 8
A1 = preset 1
A#1 = preset 2
B1 = preset 3
C0 = preset 4
C#0 = preset 5
D0 = preset 6
D#0 = preset 7
E0 = preset 8
F0 = preset 9
F#0 = preset 10
C4 = trigger
cc 28 = MPE Pressure scale
cc 30 = MPE X scale
cc 31 = Harmonic ratio
If you want it to work with mononoke pads you a) have to set up the pads to trigger the notes enkaytee mentioned above. Secondly you need to, in fundamental default mpe patch, assign y axis to gain. But you still won't get per note pitch bends, so it is not really worth doing imo unless you are OK with mpe with no proper pitch bend control
Again, the only reliable way to check if you are getting per not epitch bend is to set pitch bend in fundamental to 6, so it is noticeable. Then play two notes on your controller, and try to bend only one while keeping the other at original pitch. If it doesn't pass this test, it is not working, whatever anyone says to the contrary
Same trick of assigning y axis to gain in Fundamental applies if you want to get kb-1 to work. But still no per note pitch bend, and I'm getting stuck notes now too.... Yup, definitely giving up on this
Anyone have trouble getting it to load as an audio unit? I just got it and have been trying to get it to load in AUM but it just keeps crashing. I’ve restarted my iPad, opened it in standalone first, and have deleted and redownloaded but no luck. Same in apeMatrix too
I had this problem when I first downloaded it, a reinstall fixed it. So maybe just try reinstalling again, a few times if necessary.
I’ve tried it a few times with no luck, I ended up sending them an email though. My iPad is stuck on 12.4 so it may have something to do with that. Either that or it uses more memory than my ancient relic can handle
Well I made a video with it in standalone in AUM but my piece of shit iPad could barely handle everything and the sound cut out of everything I recorded within about a minute but for some fun, run it through scatter brain and then put Kosmonaut on every output, run two of the outputs into a bus with another Kosmonaut, then do the same for the other two, and run everything into a masterbus with Shimmerverb and enjoy the madness
I had to update my air2 from 12.4 because it was nothing but trouble with number of apps.
I have Fundamental and like it for the most part. I've been able to control it via external controller... not pitch or anything, but enough to satisfy.
I only have a couple issues with the app. The part that's cut off at the bottom when used as AUv3... a few crackle/pops here and there... and it seems like it crashes more than it should.
I realize this a brand new iOS app, but I get the impression from a few here that the dev isn't so keen to really flesh out the iOS Fundamental issues. As if the iOS version is really an after-thought and not worth the time to iron out the kinks.
Is this the case? I could probably live with the issues I've cited, but if the dev isn't really responsive, and it stops working after the next iOS update, I'd like to feel confident this dev would be maintaining the app enough to fix show-stopper issues. Based on the comments of those who've been in contact with this developer, I'm not very confident he's that committed. Is this an accurate assessment?
Great thread. Love the app but dislike the layout and sliders for sure.
Has anyone made any infinite tones, like the illusion that the pitch is constantly moving. Ala 'endless' Mac or even the infinity tones in some synth apps? Tips for that are hard! Thanks..
@oceansinspace easy to do this, if I understand correctly what you are asking. You just use the loop envelope setting, then tap gain sliders to get them moving, play with the envelope time and the envelope random button.
@skiphunt this dev, Sinan, is a really hard working guy, but there are definitely problems in that things that are important to us, like getting a better preset menu, or setting up a beta group are things that he discounts as not important. All I can suggest is for anyone who has issues with the app to be firm when corresponding about how important your concerns actually are. App store review comments are likely to carry some weight too, of course.
I will not be able to make a video on mpe unless this app's mpe implementation is fixed. Sinan insists it is working, but it is not. Still waiting for him, or anyone else for that matter, to send me a video of one finger holding a sustained note on a seaboard while a second finger does a long bend.
Hey, thanks gav! You are a gemstone of knowledge. I just realized that I am re rewriting over the presets, but that's ok In the end but I just need to make me a dope 'endless' pitch illusion to warp the tosco lab lsd chemistry set proper to midi trip. Thanks!!!
Writing over the presets, yes, that's a danger 😂. The preset management implementation is a real headscratcher.
Which weird because Hainbach specifically wanted to get more into iOS. It’s quite possible though that he uses the app like his hardware units, i.e. IAA so perhaps AUv3 really is just an afterthought.
Was on the fence about this one - and finally grabbed it today ...
And I must say that my concerns after reading all this posts here in the forum got proven right ...
This app sounds great and quite unique in its sonic potential - but the problems of the GUI for IPad usage are immense and almost not tolerable:
not getting a full-screen GUI on an IPad Pro 12,9 - neither in the standalone nor the AUV3 - which makes the whole GUI much too small to use in a „relaxed“ way ...
some sliders are almost impossible to get picked without a pencil and/or 5 or more attempts to do so with your finger
super clumsy „knobs“ for the 8 oscillators ... impossible to „adjust“ them while having the app making sound without making unwanted jumps in the frequency of the oscillator
only rotational - instead of horizontal adjustment movement for the oscillators - making it even more clumsy to use them
preset system crazyness
no connectivity to an external sequenzer or keyboard via midi .,, to drive it from „outside“
several and unpredictable crashes and „falling silent“ moments ,,
So - all of this together makes me almost wanting to ask for a refund ... and I must say that I almost never do this - but in this case this app really feels Just like an appendix to a desktop plugin - without any thought about the basic needs and conditions of iOS music making ,,,
But since - at the same time - I do see (and hear) the sonic potential of this app ... I wanted to first ask the forum - before I will take this path ..,
Is anybody in contact with the developer .,. knowing if these GUI issues will get addressed or is the common sense that there won’t be any further IOS specific development for this app?
@Gavinski do you know more about what to expect or not to expect?
At this point I don't expect much, sadly. I was in constant correspondence with the developer for days. He either can't or won't fix these things. I would advise you and anyone else who cares about these things to contact the dev through his website. I love the app very much, and for me it would still be worth keeping even with its many serious flaws. But I fully agree that these things are not acceptable. When I made my first video I had confidence they would be dealt with but I saw later that was starting to look less and less likely. Who knows, if enough people complain maybe it will be finally taken seriously.
You also forgot to mention that the mpe is not working properly by the way. Unless anyone can show me a video of two notes held on any controller other than a sensel morph, with one finger holding one pitch while the other clearly does one large pitch bend up and then down. @Bon_Tempi
Ok - thanks for your honest perspective about this situation -
And yes, I do agree with you - itˋs quite sad to see such an app not getting at least a bit more „iPad-specific“ love and attention in its development .,,
But yes, I will contact the developer about his website - maybe more people complaining might change the situation ...
Yeah, I feel you on the midi. I am just changing patching and then having like one octave of pitch and I am used to iPad midi and this is goofy. I just want normal midi notes with the MPE stuff and not a hyper controller either.
@Bon_Tempi I pretty much agree with all your cited issues. And, am in the same boat. I rarely do a refund unless there are show-stopping flaws and the dev isn't responsive.
This one is in a grey area for me. I REALLY love the app and the more I play with it and learn it's quirks, the more I like it. I could enjoy the app with it's many short comings I think. I mostly use it in standalone to create my patches, then load them up in apeMatrix without messing with the AU controls much further. Minimal control and cautious LFOs on minimal parameters.
I'm just concerned that if an iOS update breaks it... will the dev even bother fixing it? Who knows.
I get that it's sooo niche that the dev isn't likely going to sell a lot of iOS versions even with the issues fixed. So, he probably doesn't feel like it's worth his time when the VST version sells for much more.
I'm torn though. It nearly meets my criteria for the rare case that I ask for a refund, but on the other hand... I think I'd really miss not having it.
I emailed the developer again, hope he will reply this time.
It will definitely never get regular midi in. The manual explains that Sinan and Hainbach never intended it to be just a normal synth and it would be very vanilla as that. I agree on this point.