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
/
One crucial piece of the plan is the reset technique offered on another thread hereabouts...Modstep and 4 or 5 big boy synths is a pretty demanding load so I clear stuff by: holding down power button (the one on the edge), the screen changes to that slider screen, keep holding for 10 sec, then hold the round function button till the screen resets to regular start screen...another piece is (probably) current iOS, Air 2.
@Sebastian That's cool that AudioBus 3 is coming out. Will it have some of the same features of AUM?
Scary, these two.
BS
I run an iPad Air 1 with up to 5 synth apps at once in AUM with insert and send effects on all the channels all sequenced from external sequencers (mpc or live) and it runs fine without glitching, modstep is the fing problem! When I try to host 3 synth apps in modstep they all randomly stop working, no effects or anything else! It just isn't viable as a IIA host or even a sequencer. Maybe it isn't modstep, maybe it's iOS midi implementation, which I also believe, but either way, I for one am done with modstep for now at least.
One way I am looking into is the IIA sampling in impc pro, and running 2 MPCs, my 1k and impc pro with element together, but I am not really convinced of that either.
Seriously external sequencer, 5 or 6 good synth apps (nave, iSEM, iProphet, Thor, animoog and borderlands granular from my experience are the best and most useable, lots of others got deleted from my iPad) AUM and the AUFX series makes for an incredible sound module! Sold my blofeld recently because of that and an Alesis io dock 2 actually sounded better. Add flux fx and effectrix and the sonic possibilities are supper deep!
I want an individual track outputs version of gadget, sequence and synths in gadget, mixing and fx in AUM, both the most stable apps IMHO
@jbvdb From what I'm seeing in this thread, Air 1 users are reporting Modstep fails. (This is assuming that Air 1 users are on latest iOS, though not every one with Air 1 fail reports have noted their iOS).
Modstep, midi sequencing, (and recording) multiple synths and fx is more analogous to the processing demands of Auria Pro than AUM or Gadget. I personally had no joy with Auria Pro until I upgraded to Air 2. Same deal with Modstep it seems. iPad Pro would probably improve things yet again, though not needed in the case of AP or Modstep (yet)
Only 31.25% BS.
Original post spec'ed 16 synths simulatenously. You mention up to 5. If you find a host that's stable controlling 16 separate synths at a time without choking, then I stand corrected.
But yeah, probably the fact that you're controlling them from external sequencers probably helps a lot.
BTW, I'm not defending ModStep's performance. I normally use it just as a sequencer and generally don't use the internal instruments, IAA, or AU hosting. It's stable enough for me as just a sequencer but I have run into problems with it as a host.
I personally wish the ModStep devs would just focus only on making it a feature-rich, stable MIDI sequencer. Seems to me if all that effort spent on the internal synths and sampler, IAA and AU hosting, the mixer, etc. was put into it's original purpose and focus, it would be fabulous. The devs don't believe that's a productive direction though, and who am I to argue?
Peace!
I hear yah, and Modstep as a sequencer for external gear is all I use it for now so 100% effort in just that area would have been great but things like IAA, AU, internal sounds etc. make it more popular and I assume mo money comes in which is likely a factor in this effort, but honestly I have no idea of the economics at play.
I am. I've been using MS alone(opposed to AB to AUM for audio and MS just for midi) in these days and it worked perfectly. The only things I'm really missing is a undo button and a latch/write option for automations recordings/editing. For me it's like working with gadget but with much wider/intriguing sound palette
Just to be clear...
I said "I'd like to see" not "I'd like to see this run on my Air 1".
My point is not performance but the tedium of trying to make it all work as things stand. There is a certain level of expectation. In this case, modstep controlling a synth that is loaded in AUM. The apps are not consistent.
Can't argue the math!
But I do run lots of effects bringing the numbers closer to those mentioned, now I don't know much about computing but I figure an effect probably uses a lot less cpu, so you are still correct
My MacBook Pro can run 16 sound generators at once if I am careful which ones I use
That's great. I haven't been so lucky, even with the latest release. But, I also don't lay the blame on ModStep - it could be any one or more of the apps. I don't do a lot of testing, and (worse) have been too lazy to submit bug reports to help the devs out. So I really can't complain!
The main reason though is it just feels better to me to keep ModStep single-purpose. The mixer is really basic. There are no sends, which I make use of a lot, and no panning. There's no file player. I never use the internal instruments. Other than developing a few quick ideas, I always find myself reaching over to AudioBus and AUM or Auria Pro. So then I have stuff scattered around. I just don't like it. I prefer to leave the audio processing in the apps that are really good at it and the sequencing in ModStep, which does the best at that of anything I have.
Also, if I run out of processing power and want to offload some to another device like my phone or older iPad, it's a simple switch of IO settings, not a restructuring of the ModStep project.
Lastly - switching projects. If all those IAA's and AUs are loaded in ModStep, they're going to unload and re-load between projects. As I don't perform, that isn't a real concern to me, but if I did, I think I'd worry about the reliability and load time of that a lot.
+1
Exactly, and like Gadget, I send raw stems to a DAW for mixing niceties that Gadget and Modstep lack (so far).
I honestly don't understand some of you. Sure. It's hard to understand midi. Sure. There isnt one app that does it all. And getting all the apps running together is also complicated. But it's literally nothing compared to getting this to work together:-
Once you add analog hardware midi to the mix it's literally a whole other universe in frustration. Compared to that iOS is calming. Like a warm bath.
Here's a way to have up to 16 apps all pre-configured and ready to go in what - so far - seems like a stable configuration. The basics are:
1. Load every app you'll need in an AudioBus input slot, even if you don't need it right now.
2. Load AUM as the AB output. Each loaded synth will automatically show up as a separate track in AUM
3. Load ModStep.
4. Add a track for each app you loaded into AudioBus
5. Configure each track in ModStep and test that each app plays.
6. Save the ModStep project as your starting template
7. Save the AUM Session
8. Save the AudioBus session.
Starting back up:
1. Open AudioBus and load the saved session
2. Activate AUM in AudioBus and load the saved session
3. Activate ModStep in AudioBus and load the saved project
4. Save the ModStep project as a new file before making any changes so your original template stays unchanged.
5. Activate the apps in AudioBus as you need them.
I like this a lot because everything is pre-set, but you don't have to actually activate any apps until you need them. Likewise if you no longer need them, you can de-activate at will and everything remains set up.
For example:
Load all the apps you want into AudioBus input slots:
Load AUM as the AB output:
Set up and test your tracks in ModStep
Save the ModStep project, AUM Session, and AudioBus Session
Close all apps and AudioBus, AUM, and ModStep
Open the session in AudioBus. Load AUM and restore the session. Load ModStep and open the project.
SAVE the ModStep project under a new name before making changes!
You can now remove any tracks you don't need, or just re-order them to get the ones you don't need out of the way. They do no harm since they don't load any apps.
At first AUM and ModStep will look odd because the apps haven't been activated in AudioBus. This is a good thing though since now you can activate only what you'll be using. As you open them they will show up in the right tracks in AUM and ModStep will be able to see them (the output designation will turn from Red to White).
Fantastic tutorial. Was halfway through making my own till I saw your post. Good job
Please add the same mixtable of AUM with subgroups, and clever insert of gain, pans etc...Thanks...
@wim I do the exact same things
That is part of my frustration. When I was using strictly hardware MIDI it was actually easy. It's the iOS way of doing MIDI with all of its complications that drives me nuts.
So wierd that you find the opposite frustrating lol. my main issue is getting the audio to be perfectly on time is much easier with ios synths and vsts than with hardware synths....
How much longer will the wait be?
I think that if you gave an infinite number of monkeys an infinite number of iPads and an infinite number of AudioBus-compatible apps, you'd still be more likely to get the collected works of Shakespeare than this setup.
I stand in awe.
Dumb question: You're using AB for state saving and easy switching between apps, yes? And [ winces; braces for impact ] AUM is necessary ... because?
It doesn't really matter. I'll just do this and learn by doing. Thank you forever, sir.
100% agree! Theres virtual midi session midi inputs and outputs are different in each app etc. In hardware if the channels are set right shit works!
Not a dumb questions at all.
It all seems very complicated, but the basic idea is simple: set up and get working everything you think you'll ever need once. Save the templates. Recall them as a starting point for the next project, but only use what you need. Like setting up and connecting hardware, but only powering up what you're going to use.
Yes, AB for state saving, easy switching between apps, and AB Remote. However, the biggest reason is to have everything I think I'll ever use already set up and ready to go, but not active until I need it. When the saved AB session is started, all the apps are there snoozing until I "turn on" the ones I need. They then pipe nicely over to AUM without any further configuration.
AUM is there for three main reasons: Mixing, Recording, and AU hosting.
I wish AudioBus could host AUs but it doesn't, which muddies the waters a little. It doesn't appear that @Sebastian is planning AU support for AudioBus 3, so that isn't likely to change unfortunately.
Thanks. I hope you still do yours. I'm sure it'll more clear on some points and bring more to the table.
You're smarter than me then! I can't believe I fumbled around setting things up over and over until now. This idea just (finally) popped into my head while driving home from work. I just had to get it out of my head and tested.
BTW, I guess those who like to host the IAAs and AUs in ModStep could follow the same approach - set everything up all within ModStep and then only use what you need. But right now there's a bug in ModStep - it ignores the setting that tells it not to auto-start IAA apps. That could lead to a big meltdown until they fix that one.