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
I'm glad you like it. I was actually thinking quite a lot about how to make a GUI that works with nearly 300 parameters. In fact in the early stages of the synth engine development I used a simple GUI with hundreds of sliders and came to the conclusion that that's definitely not the way to go for the app.
So how do you tweak the filters and set the envelopes and stuff? I like VA synths and this looks unique enough but I was more sold before I saw the video and pics, left me a little confused to be honest. More info on the workflow would be appreciated.
I had the same question then bought it without asking (addict me)
It worked out well in this case. You tap the Module/box that you want to tweak and the box in the lower right fills in with the sliders/selections for parameters of that module, e.g. tap a wave table oscillator box, and you get the sliders for envelopes gain, skew, wave index, and selections for which table you want, "stone", "sync saw", "voice Eeh" etc etc.
Tap an envelope and you get the attack decay etc. some stuff is drawable...
I see. Cheers
I have a very intense Facebook allergy. It would be very nice - if possible - to upload the video to youtube or such.
I can see the video linked to in the original post. What devices or user-agents can't see it, and what do they see instead? Just the static screenshot?
I'm still on 9.3.5. Wouldn't let me buy. Ugh.
Please edit the app details page with technical details
IAA-MIDI?
Mappable controls?
Link?
etc...
That's nothing compared to how we used to have to lug pianos around.
I'll add iOS 9 support with the 1.1 update. There was a weird GUI bug on iOS 9 which I discovered shortly before submitting so I set the the required iOS to 10.
Did I miss something, I thought the introductory price was for the feb 16 & 17? It's appearing as $7.99 here in the U.S.
Thanks Fritz. I just bought it through iTunes. Can't wait to give it a go when you eventually update it.
The app is very straight forward to get going with for me so far without reading a manual. You can get some very clean sounds which can then be run through effects for developing your own vibe with them. Many synths have very overwhelming sonic textures which can be difficult to work around and what you've got going in a setup. It would definitely be very nice to have MIDI Learn for the controls.
@Fritz like the synth so far and look forward to the improvements you have planned. It would be very nice to be able to receive MIDI from more than one source simultaneously and if the app advertised it's MIDI in port so other apps could send MIDI to it.
Using the random button on the routing is a practical way to get variations of your current presets.
I live in US and I just bought it a couple minutes ago for $5.99
Nice work @Fritz Really like this synth, very easy to get new sounds without knowing what I'm doing. I echo all the feature requests and hope it gets an AU extension.
Please if possible make it an IAA instrument too so it has it's own port. Currently I'm connected to my audio midi interface and it can only see a maximum of 5 ports, but the one I want is off the list so more port options are needed.
many thanks![:) :)](https://forum.loopypro.com/resources/emoji/smile.png)
Bought this. Wasn't wild about the presets, but getting some cool stuff via random. Please add background audio.![:) :)](https://forum.loopypro.com/resources/emoji/smile.png)
I just added it to my to do list. Btw, what is the point of using multiple inputs simultaneously? DA ONE is not multitimbral.
The basics tutorial video is online now:![](https://img.youtube.com/vi/NzPpG_lKTME/0.jpg)
FB: https://www.facebook.com/mnsignalprocessing/videos/1092957390812581/
YouTube:
If you follow through on adding MIDI to controls, you can have one app sending note messages and another to send CC to operate the controls. In a live situation, someone may use a foot controller to switch between presets or use a sequencer for some aspects of the performance and a MIDI keyboard for others and would rather have all of the connections ready and tested at the beginning of the set rather than have to change it during the performance.
Sounds great and love the fact that putting it in record mode and then stopping it immediately opens the "Open In" menu so I can dump loops right into AS. MIDISTEPS is a good driver. Thanks!
1 use case is using multiple different appregiator apps running in different times sending midi to the same synth. you can create a ton of polyrhythmic material this way. and also a lot of happy accidents
sure. you could do this using an app like modstep to do the routing but being able to do it directly is useful as well ![:D :D](https://forum.loopypro.com/resources/emoji/lol.png)
Ok I see your points regarding multiple MIDI interfaces
Yeah, just makes things a whole lot easier when you have multiple midi controllers and apps, so you don't have to keep going into the DA One midi settings to select a different source each time.
Beautiful work, this synth is amazing @Fritz. I would like to also echo the request for an audio unit extension. I feel the design of the synth would be perfectly fit to becoming an AU. To further this point I made a mock up of what could be, if your up to it.![](https://forum.audiob.us/uploads/editor/un/5a4cku2shg4d.png)
Test
@Fritz
A fascinating synth with an innovative interface, I really like it. Very nice release!
I hope you can add a few things that I think are essential for a smooth user experience
-- background audio
-- IAA instrument
-- auto connect to external midi controller
I have to say, these I'd expect from a premium synth. (Of course, au would be nice as well -- but that would probably mean a different level of time committment)
Nice concept, I like it. :-) AU is not something for the next update but I'm definitely considering it (also because that would be a step towards a MacOS AU, too).
Thank you. :-)
Background audio is active when it's connected to Audiobus, but of course I can make it active all the time, too. IAA is something I'm looking into for the next update (so far it's just the Audiobus implementation that provides some IAA compatibility).
But what do you mean by auto connect? That the app should automatically connect to any MIDI source it can get a hold of? Or that it should automatically connect to a new interface that is plugged in / becomes available on the network?
yes, please do. this would be an essential feature. strangely enough, when I tried the AB workaround to get backround audio, I still got no sound out of DA ONE when it was not in the foreground.
Great to hear! hopefully not too hard to implement
no, just auto connect if the synth detects that a midi keyboard is connected. virtually every iOS instrument does that so it is a kind of expected behaviour. So if a midi keyboard is already plugged in when the app starts, automatically connect to it. And when a midi keyboard gets plugged in while app is running, connect to it automatically.
Should this happen only for hardware MIDI interfaces or also the Network ones?
For virtual connections, I don't know exactly how it works technically, if the synth would actively connect to a virtual midi controller or rather give a message to the controller that it is there and then the midi app does the connection,
But from a user perspective, SoundPrism pro for example sends out notes and the instrument apps simply receive it, generally speaking. It is then in the SPP settings, in this example, that user can filter who receives the midi and who doesn't.