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 have both. If I had to uninstall one of them I'd say buh-bye to Gadget without hesitation.
@hellquist is that because you prefer Modstep as a sequencer , or because it lets you play with all your IOS synths ?
so , if gadget update dropped tomorrow with midi out to play external stuff , would you still keep modstep ?
Hmm, interesting! This wasn't apparent from poking around the app at all. It's so cryptic haha. I'll experiment tonight.
It is frustrating though that so many apps tend to favour the "clip" approach though. I understand how it's useful for live performance, totally. I have Cubasis but getting MIDI out of it and into synths/drum machines is really hit and miss for me. Don't know why. Some like it, some don't.
@Tones4Christ to add to what @syrupcore said you can reorder the 16 patterns within a clip. Just long press then drag.
I wasn't a cliplaunch type either but between Launchpad and now Modstep, it's definitely growing on me. It's just more fun, basically.
So in your opinion if you got modstep, would you still need launch pad or it depends?
Yes. Clip launch in modstep to me is real deal. Non linear, as in launch any clip in any column, perfect real for touch, and therefore more fluid even than Live, the coming following actions for clips makes it work as a clip sequencer along with being a launcher...
It's next level composing for me: time line is linear, clip launch can be linear or not, adds a second dimension...difference between ruler and a matrix
I thought I'd comment on my preferred way of working with ModStep, since I haven't seen that anyone else has mentioned much about it in conjunction with AudiBus.
One of the things that bothers me about using InterApp Audio plugins is that they don't save their state when you shut down the host. But AudioBus excels at saving all of that. So, I like to set up ModStep, and each of the apps I want to trigger with it as inputs in AudioBus, not in ModStep. I then set up AUM in the output slot so that I can adjust levels and add effects to each channel (also to add any AudioUnits apps I want to use).
As I add apps, AUM sets up a channel for each of them, I can take advantage of the easy AudioBus switching between apps, and I can save state for everything - including ModStep.
Restarting my project is as easy as starting AudioBus, loading the state, and starting each app to get back to where I left off. I usually start each instrument first, then ModStep, and finally AUM. If I ever get to the point of liking something enough to get serious with it, then I can either swap out AUM for Auria, or, since AUM can be added as an input and an output at the same time, I'll sometimes set up a second lane in AudioBus, adding AUM in the input and Auria Pro in the output, reassign the AUM outputs from phones to it's virtual ports, and viola, they show up in Auria for capturing.
The key to all this for me is leveraging AudioBus for state saving, and app switching. As for ModStep ... I'm starting to get my head around it finally after about a week. I'm one of those kind of people that just can't let go of trying to figure apps out. ModStep is definitely one of those apps where virtually nothing is intuitive!! But now that it's starting to settle in, I keep coming back to it. There are a few glaring missing things (time signatures, more grid steps than 16, and a keyboard, mostly). But I'm starting to dig AudioBus + ModStep + AUM it a little finally.
I'd only need Launchpad until Modstep gets proper file import. Then Modstep all the way.
Anybody getting some sort of corruption in Modstep that forces a delete and reinstall? Happened to me twice in the last three days, restarting the ipad didn't help, it kept crashing on launch.
Link activated in settings? Open IAA session activated in settings? Coming off a Link session maybe with AB in the scheme?
Above happened with me, pre- beta and the beta updates. One set up that had caused the above also involved a certain synth whose IAA midi is a bit of a mess...all of my suchlike crashes have cleaned up during beta testing.
@wim
Props to you for this scenario. I'm loathe to open anything but modstep and source instruments, parsimony in iOS schemes is a personal peccadillo, if I find myself opening more than a host and plugs to do my thing, I get itchy for Surface Pro and Bitwig. These new quasi DAWs (AUM w/AB, and Modstep) are what's keeping me on the platform. Even more so with AUM updates, and coming Modstep update...
Any IAA instruments loaded in ModStep before it crashed? I wonder if one might be crashing the host on load. Maybe try the trick someone mentioned in another thread (too lazy to look it up), where you hold down the power switch until the power off slider comes up, then let go and hold the home button until you get back to the home screen. I never knew about this way of clearing out zombie IAA crap, but it's been doing wonders for me. Stuff that can survive a reboot seems to get cleared out with this trick (or maybe it's just my imagination),
That's another reason why I prefer adding all instruments in AB rather than stuffing them inside hosts through IAA. I figure all one of those has do to is get twitchy and it could bring down the host on startup. I'd rather have them out in AB where I can start them one at a time and avoid offending apps if things blow up. IAA, and developer's understanding of how to write stable IAA support and apps, don't seem like they're fully baked sometimes to me.
Nice write up @wim. Thanks.
Wim, do you use AudioBus Remote in any of your setups you described?
No, not generally. I guess if I was performing, I might use it with a second device, but generally, just flipping back and forth between apps on the same device is easy enough just with AB. Remote is cool, but doesn't add much for what I do (which is burn up countless hours making little bits of songs and never finishing anything).
AudioBus + AUM ... Don't know what I would do without those two though!
Well, yeah, as it stands right now. I struggle to use the editor in Gadget. Not sure why, but it completely stops me creating and have me sitting around trying to work simple things out, only to only be able to use very limited sounds in a formulaic fashion. In comparison ModStep is open to pretty much everything including all my other apps, and after just a short learning period I have it making sounds in a controlled fashion with all my other apps. If I compare it to work (web development) Gadget feels like Frontpage/Dreamweaver where ModStep feels like VIM.
Gadget is probably some of my worst spent money on iOS if I compare usefulness (for me, personally) vs money spent (I obviously got all the IAP's etc). I have recently spent some more time with it though, just to give it another chance, but as the question was asked, and only one could be purchased (or in my case one to be un-installed) ModStep wins over Gadget.
Yeah,the second time was after activating Link between Modstep and Aum, my work-around until the fix arrives is to open a new empty non-link session before shutting it down (though I also turned off auto-open of IAA so maybe that will help too).
Love this comparison. I think it's pretty unfair to gadget but also think it might kinda nail Modstep. All the power in the world but the first few times you use it you won't even know how to exit it. At least that's been my experience with modstep's interface and what I'm hoping with regard to all of power lurking just atop the learning curve. And thanks for the inspiration; If I can take vim (all day, every day), I can take Modstep!
:w!
This thread and the one comparing Cream with Modstep has helped me realize something about the how and why of my relationship with certain tools: I'm willing to put in hours and hours learning certain (deep, idiosyncratic, at-first-obtuse, choose your adjective) applications. Comes down to what is offered, I think. I see Modstep in the class of MTS and Sunvox in this sense. They all three of them in their way offer it all, which is what I want. And the time I've put in to woo these elusive creatures probably explains my extra affection for them
Another inspirational post. Cheers @Littlewoodg.
Love it when people share from their hearts....
@syrupcore, @Tones4Christ, the feeling's mutual.
How Is Modstep's flow and immediacy regarding midi recording and looping? Is it easy to capture the moment, i.e. synced loops, with other sequencers and a keyboard pointed at it - and collect and play or overdub as well as 'position' and trigger them?
Seems pretty good from my playing with it.
Arm as many patterns in a clip as you want to record, turn on Chase if it's not, arm the track overall, and play via a keyboard. (mind you, I'm using an iRig Keys directly into the iPad vs my main piano controller into iConnect MIDI4+) But, with those patterns armed, the track armed, just play through the armed patterns, then the loop kicks in.
I haven't tried overdubbing yet, but moving the recorded MIDI for some timing fixes is fine as well, just as you would anything else in the piano roll. Again, chase is important here...
Little deviation from the topic:
someone said MS hasn't quantized input which is halfway true since you have have quantize function right there but my funny point is: we ask for quantized input and then everything sounds too machine-y so we will ask for a humanize function. Or, at least, is something I will be likely to do. The same thing happened to analog gear vs digital and now everyone is paying good amounts of money to get the "analog vibe" back into recordings with digital tools(definitely at a fraction of the real HW price, space and a lot of o\ther goodies)
Thanks @ImNotDedYet !
I'm really longing for some Undo as well as Undo Take functionality in ModStep...
1.) A simple Undo button that unsurprisingly undoes previous edit or command.
2.) Using said Undo button, also be able to clear anything recorded (take) since you last hit the Record button. This way you could easily perfect and redo recordings in a quick and intuitive fashion...
3.) While I'm at it, a "Capture Last Take as recording" as per Logic Pro X would also be super awesome...
Only way to go is Session Autosaves - at least you can go back in 15 second increments to 90 seconds by clicking one of those.
I request Undo type Matrix for apps - if you have a parameter modulation applied, even Undo is impractical, as many changes can pile up quickly. So Undo Matrix would allow you to Undo/Redo, but also by Device (Synth/Sequencer/modulation etc, and in the manner you refer to above).