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
If things are stable for you then not too much.
Mix busses, aux sends, direct recording to audioshare, midi learn on au parameters, all those nice tidy little single purpose builtin FX, audio file looping, pre or post fader positioning of FX ... off the top of my head.
If you don't need those bells and whistles, and if your app stability with Modstep has been better than mine, then no need to involve any other app.
Automation of effects Aux. And to be honest the wackiness and stuck notes happen a lot less with the Aux hosted in Aum. Also mix busses to do things like parallel compression or effects and gluing multiple layers together using compression.
I'll see if I can make a tutorial video one if these days for you of my setup. But currently I'm actually working on something else. You asked In another thread if it's worth grabbing Redshrike if you already have other icegear synths. Since it's an Au I'm trying to make a track using only redshrike exclusively. I gotta say this synth can shriek and howl unlike all the other icegear apps.
Routing one track's MIDI to more than one app at a time for some great layering. Routing multiple tracks of midi to the same app, say for having a separate hi-hat clip that you can turn on and off, without having to have another instance. (Maybe you can do that in Modstep. I forget.)
Switching between Modstep Projects without having to reload apps.
OK, Redshrike in the quiver now.
And two minutes in (at work!), and I love it already.
Hmmm, sounds like you have Cubasis? i would say just get to know that for a little while and maybe throw in a few AUs.
wow. Plus @gonekrazy3000 : automation of AUX fx?
Ok. Sounds great. I'm sold.
So I just load up all my apps in AUM and then it modstep I just select the appropriate app in midi out? Or is there a special outing in AUM?
like in my template tutorial i like to keep automation in separate clips. i pretty much keep channel 16 for automation only. just pick a random cc number and send some modulation to Aum. inside aum i select the parameter i want to automate and just click midi learn. an alternate method is to manually select a midi cc number and channel 16 in aum first for the particular parameter and then select the same ones in modstep.
I recommend selec> @ExAsperis99 said:
Automation aside, which @gonekrazy3000 addressed, I like to not set up Modstep to point to each instrument, but rather, leverage AUM's midi routing abilities. So, I point each of Modstep's tracks to AUM, setting channels as appropriate. The select "AUM Destination" as the midi input and filter out all but the channel(s) you want.
In the example below, there are two tracks each pointed to channel one, is selected for RuisMaker in AUM. The first track has the main drum loop, while the second has just the hats so that I can toggle them in and out through Modstep.
The "Vikings" track points to middle channel two. In AUM there are two instances of Viking, each selected for channel 2 input. So, both Vikings play in unison, but with different patches for a thick layer. (Could be Viking plus one or more of any other synth as well).
The Redshrike channel simply points to midi channel 3.
Hope it helps!
Was about to make a tutorial for pretty much the same setup. Good tutorial @wim
not much musical creative juice tonight so I thought I'd put the effort into something else worthwhile.
That's good (and helpful) work. Here now in our human version of perpetuity, so your time was well spent.
Wow, that's terrifically helpful.
Is it a coincidence that these are all AU in AUM? There's no routing difference or voodoo required for an IAA app, correct?
For IAA just disable the core midi ports inside the app. Also set channel input to Omni for whichever apps have the setting. AUMs midi channel filters will work things out then.
If I were you I'd use AuX as much as possible since all theirs states save with the project. The preset name might show init but all the AUX usually keep all the settings you fiddled with last. Extremely useful when loading a project weeks or months later.
I recently went back and looked at the tutorial, and it's amazing what was once hopelessly above my paygrade now makes sense. Mostly! (I'm still kind of baffled by the whole concept of midi cc, and trying to avoid it for as long as possible.....)
Since the AUM update there is now a new way to do use AUM and Modstep.
So you can now host AUM IAA ports as instruments in Modstep, then select the individual IAA ports in AUM as the receiver and it'll receive midi notes and cc's to control the hosted apps in AUM.
I'll probably still go the usual way of sending from Modstep to AUMs midi port like Wim's post since state saving doesn't work as it does if you host the AUM IAA ports in Audiobus 3.
So there's not much advantage to this method but it works well in my brief test.
For the ultimate in state-saving, hosting everything, or at least all IAA's, in AB3, with AUM (or Cubasis, Auria, etc) in the output slot is the best route. But that's a whole 'nother level of complexity. It's probably best not to clutter up thinking about that here.
When more apps are AB3 compatible/optimized, that's what I plan to get back to.
Has anyone made a video featuring AIM with Modstep?
I'm reverse-engineering a Modstep project to host all the apps in AUM, and I have a question.
I've got StepPolyArp, Patterning, Model 15, Lorentz, and Ruismaker in my project.
I have loaded up all these in AUM, but the channels devoted to SPA and Patterning to not have those three little lines to the left of the icon, and therefore I cannot route their midi. Why is this?
EDIT: So I realize that SPA was loaded as a "generator," and not an "instrument." The routing option appears when it is loaded as an instrument. (Which I still don't understand, but whatever.)
And if it's germane, I'm using midi learn to trigger Patterning within Modstep.
If you have apps that'll only load as generators, you can still set up routing via the midi routes from the menu.
Great. Thanks, Wim.
Do I need to choose a channel in Modstep? Or leave it as omni? And while we're here: Better to have AU effects also loaded in AUM?
You need to set the channels in Modstep or you won't be able to filter them to different channels in AUM.
IMO better to have the AU's loaded in AUM. Hosting everything in AUM was the point of the exercise. Otherwise there's no need to add the complexity.
BTW, if things are working for you in Modstep ... maybe there's no need to fix what ain't broke?
Well, as GK3000 point out, there is wonkiness. I'd love to have smooth, rock-solid sessions, like, just once.
Also, it would be great to go from jamming in AUM to a quick setup in a sequencer.
Just save a default template in both Aum and modstep. That's what I do anyways
It'll be a work in progress.
Do I need to have an AUM channel with Modstep in it?
Only if you want to use modstep's delicious sampler for drums. Which is something I do.
If you do, I've found that Modstep doesn't always like being loaded in AUM directly. It seems to do better if loaded first outside, then added to a channel.
+1. Modstep has gotten a whole bunch more stable lately and I find several AU's I use to work without a hitch.