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
Are you using loopy as a live functioning daw? Turn ado has to have play pressed and it doesn't really work well if you don't have the inter app clock sent from a daw. Idk if loopy has one. I just have it for some unknown reason. Probably bought it years ago.
I have my mind wrapped around stuff alrite, that is not the problem. I've been using my multi app Audiobus set up live for the last 2 years without a glitch. It's been tried and tested in front of live audience. Some things ain't working for me in AUM while they are working smooth in AB which I've reported above. I'm currently working with non- virtual musicians and have no need for bells and whistles aum does better than AB, in fact AB does it better for me because of Loopy's integration.
I'm extremely happy for your affection for AUM. Nothing's broken in my world, just sniffing around.
What is your niche sir?
Just a somewhat normal 25 year old audio engineer. I apologize if my passion comes across as biased opinions, but I was just trying to shoot the breeze with you about workflow. If it ain't broke don't fix it. Independent artist, studio engineer, some live under my belt, and I do soundtracks and film scores as well as some underground electronic/ hip hop. Not so much anymore. I will probably be pursuing a masters soon if the job market stays stagnant for us audiophiles. Cheers and I hope your world continuously stays that way brotha. Later
As far as the whole "captures settings in the whole chain" go, this hasn't been my experience with either. I do find that both have their own sets of issues when pulling up saved sessions, but I feel like I get stuck in a "bad save" state in audiobus more frequently and have to completely redo my chain to get out. And state saving, in my humble experience, seems like a White Elk. I've seen it. Like twice.
I do think you would dig AUM for what you do. It adds another layer of expression for me, but I do concede that everything I do with it comes from the safety of a nice comfy chair and a good pair of headphones. I'm not playing live and the rare times I have, I certainly stay away from complexity. Certainly get where you're coming from. My experience with AUM has been great stability wise, though. I'm pretty sure I use it in "minimalist" mode, though. I'm pushing a few tracks here and there through either korvpressor or Reverb. Not many "bells and whistles", but my tastes don't lean toward a lot of processing. Not the stuff I attempt to play anyway.
Meant to add, I use both AB and AUM. I don't think either is a replacement for the other. They compliment each other nicely for what I've figured I want to do with them.
@boone51 that is basically what I was getting at. I use hardware and have people come record some guitar I'll use AUM. Live sound is obviously a whole new ball game and you need something that will provide you with a consistent reliable signal flow. Whether that is an old analog board you mastered, or audio bus with loopy. Whatever you work with make it your own. I hardly ever reach the bells and whistles stage. I just stick to my mixer, sound library of takes, and a Kaos pro that I have had forever. I'll still make beats for people if they request them. I have been using maschine for 6 years plus, and it's my go to sampler. I'm always interested in hearing others workflow.
Well, maybe I'm just lucky, but I find state saving along the whole chain works flawlessly in AB, but not at all in AUM. I guess I'm the outlier....
@lukesleepwalker I wouldn't imagine you're the only one to experience success with state saving. I'm sure that would have bubbled up here in the forum if it was widespread. I should have added that due to the nature of my personal iPad, I can't blame audiobus for the problems I've experienced with that feature. I test serval apps for different developers and so my system is far from what I would consider "stable". But it works for me because I'm not relying on my rig up on stage. Still, I find AUM to be fairly stable, but I'm not saying that from a state saving perspective. Because my playground has proven to be "unstable" at times, I've gotten in the habit of saving "sets" instead of saving the entire project snapshot. As in, I have a setup in both AB and AUM for a default loopy workflow. I have another setup for vocal workflow, and so on and so on. I do still attempt the state save thing for testing purposes often, but usually I'll just dial up the "set" and go.
@boone51 gotcha, mate. That makes sense now that you describe how you work.
Loopy only takes input straight from hardware or from Audiobus. Michael could easily add IAA filter capture ports to allow sending stuff into it from IAA hosts like AUM, Auria or Cubasis. The cool thing with that is you could get the signal to be looped at any point in a channels effect chain in AUM, not only at the end of it. Let's hope Michael wants to implement it some day
AUM doesn't do anything special with the signal when passing them through effects, it just feeds it the signal in one end and grabs it at the other end. I would be very surprised if Audiobus did it in any different way. I'm pretty sure something else was the reason for your different sounds.
Many IAA apps has a common bug in that they can't load properly when launched in the background via IAA. The trick in those cases (except mailing the developer and ask them to fix it) is to launch the app manually first, and then connect it.
AUM allows connection of any single mono channel in a stereo pair. In the hardware input selector, it lists first the stereo pair and then its two mono channels underneath. Does it not look like that for you? If not, please send a screenshot
I have no EIE to test with..
AUM has no state saving for Inter-App Audio apps, only for AudioUnit extensions. The reasons for this is simple: There's no available technology to do state saving in IAA apps, but there is in AU extensions. Audiobus has their own proprietary state saving mechanism, which is only available in the Audiobus app itself. I could make a similar state saving technology too, and then try to convince every developer to support both Audiobus state saving and AUM state saving, etc.. I don't think I have the resources for that.
Yeah, I remember this from when AUM was first released and still understand why you can't do state saving etc. I'm fine to use AB for state saving and AUM for routing, mixing, etc. Thx!
I did request it but if I held my breath I wouldn't be writing this right now.
I found it strange too, especially because tonestack was plugged as an insert. The sound was as if I only heard wet signal and very faintly. So basically pretty much only reverb. The same thing sounded just fine in AB.
Seems like Samplr update is coming at some point so hopefully this will get sorted.
The individual inputs were greyed out. Could have been because I was using them in Audiobus but I'm not sure. I'll check it later tonight and send you a screenshot if there's something unusual.
There is no code in AUM to grey out those options. However, the individual mono outs has grey speaker icons while the stereo out has white. This is just a visual design decision to keep them visually separated, you can still tap them.
I had a recent iPad meltdown and had to recreate several of my workflows. I decided to see if I could replace MiMix with AUM because I love AUM UX and MiMix UX is fine but utilitarian. So, I set up AB as I normally do, but routed everything through AUM and then back to AB to go to Loopy.
I experienced the same issue that I think @supadom describes. That is, I set up a bus as an insert to control Turnado as an effect (as I used to do in MiMix). I purposely use a bus so that I can turn it on/off via MIDI CC. But when I turn on the bus channel, Turnado effects are very faint--like they are in the next room somehow. Tried both pre and post but nothing really changed.
I'm sure it's user error! Any thoughts @j_liljedahl ?
I run this same setup, only not back out to loopy. I had to tweak the level of send to the bus (knob to left of bus insert) and the volume of both the send track and the tornado track to get it just right. Also, there is a wet/dry mix slider at the top of turnado's preset window you can further tweak the mix. In my experience, that's typically set to 100 in the presets, but perhaps you e saved one of your own with this slider down more on the dry side. Just a thought.
Thanks. I fired it all up again and it is working as expected. I'm going to leave my other air 2 on 8.4 with Audiobus only rig but this certainly brings promise for the latest and greatest.
The two positive things I've noticed is that I no longer get conflicts between Turnado and other effect units (I have to plug it in last for it to work correctly in Audiobus) and I don't seem to be getting as many occasional random pops and clicks.
I've also noticed that ram usage has gone down from 90% to 70% but that might be just a coincidence. (Even with Safari, Ebay and a weather app opened in the background)
I wouldn't be at all surprised if Michael wouldn't want to add that functionality to Loopy. There is a clear conflict of interest and it is only his right to protect his patch, there's no need for him to spell it out to anybody. I'm sure most of us can live with that even if it complicates things a little.
Edit: I also love how when iPad is unplugged and then replugged to the interface all of the inputs get replugged automagically while in Audiobus one has to refresh the preset. Pure awesomeness. Great when leaving all the rig on stage and then just plugging the thing in when it's time to play.