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.
10 reasons Auria Pro is still my main music making tool
1 - Fab Filter Twin: very powerful, arguably among the best analogue-type synthesizers on iOS;
2 - My Auria Store purchases: some great libraries, and even while I know some of the plugins have AUv3 versions as of now, some of them have no similar outside of Auria (Microwarmer, Retune, Old Timer etc);
3 - The mixer: seriously, I became so used to it that I prefer it even to Desktop counterparts;
4 - The mixer’s built-in effects: they are actually PSP plugins without the GUIs, very lightweight and work really great. You can actually get decent results with them alone;
5 - Lyra sample player: I bet there are SFZ/EXS players in AUv3 format already, but I also bet Lyra is among the best. I use a lot of really huge sample libraries that work perfectly. Wish there were a way to customize folders for quicker access of the libraries though;
6 - No need of external plugins or tools, except occasionally Hokusai for noise profiling and reduction;
7 - I don’t have access to a desktop computer right now, so my mobile DAW must cover all bases, even if it’s a little cluttered or has a steep learning curve;
8 - I do believe audio editing on Auria Pro still has no real competition on iOS. MIDI editing is also powerful (but buggy, specially when you merge regions or change the tempo, but I learned to live with that);
9 - Habit: after a rather steep learning curve, I’m absolutely comfortable with the DAW so most of its UI shortcomings don’t really bother me anymore;
10 - those fantastic faders in portrait mode.
Things I wish the most that Auria Pro had (it would make my life much easier):
loop recording;
a Melodyne-style pitch correction tool (in fact, this is missing on iOS as a platform);
unlimited markers and the ability to assign names to it;
more plugin slots (workaround is using bus tracks) and reordering them at will;
the ability of duplicating tracks (with plugins, events etc).
Comments
It’s still the place where all my tracks end up, for vocal tracking and final mixing, and I still love using it, but I am concerned that development has slowed to a crawl and I fear for its future.
Wow, nice to hear from you again. Hope all is well. Auria sounds like a great tool, but for me, personally, the complexity even in Cubasis is unnecessary. I’m not saying the functionality is unnecessary... just for me.
Yeah, I don’t think WML had the profits they hoped from it (in fact, I once most DAWs across platforms struggle to become profitable so it’s always a risky endeavor). I think Auria could be saved (and improved) if some big player invested on it, which I doubt that will ever happen. So I enjoy it now, hoping it stays available for a long time, even if development completely stalls.
Of course, makes sense. I’m always lurking here, still keeping an eye for some groundbreaking tools, as the much-needed pitch correction app that keeps on not arriving. But all is well here, hope you are also.
Looks like shite that daw. But pro features for sure.
Hey I thought Rim was getting testers for a update in beta. Maybe I just dreamed that...
I worry that RIM has lost interest. For mixing, it is still the only iOS option with the sort of bussing options I expect/need for mixing. It really only needs a few MIDI tweaks and fixes to be something that I could use for every project, but I don’t know if they will ever happen.
It was indeed updated a couple weeks ago, minor fixes (issues with timing with 44.1 and so on)...
The GUI is uninspiring indeed IMO (not that it is bad per se, but it looks like a Desktop DAW and would be far easier on the eyes in a 20” screen). While is not as close as powerful as Pro Tools or Logic (I’d say it’s about as powerful as Sonar was 15 years ago, but with better stock plug-ins and mixer), it’s the only one I feel comfortable to do full mobile production on the platform. It’s my opinion and experience, of course.
The ui is pretty uninspiring in most iOS DAWs, imo. So, my focus is the features I need and stability...which currently means using different apps/DAWS and recorders for different aspects of a project. Annoying but a far sight better than when I start recording when there was only tape and hands.
I have been buying Auria IAP in hope that they don’t abandon it.
So how is it operating since the update? My main concern was from taking a long time to freeze a track, and general cpu overload stuff. If it’s smooth (er) then I’m back!
Since, I’ve never had those issues, I can’t say. What sort of CPU overload issues did you have? Those tend to be linked to particular plugins if it isn’t a matter of running more stuff than it could be expected to handle.
Actually this is fairly substantial update. My apogee jam plus was never recognized by Auria Pro as a usb device ( I use usbc iPad Pro) and when I wrote to them in May, Corey said it was a bug they were working to fix. Happy to report that it is now recognized and I can finally use this interface in AP. Opening the app today I did have more crashes than usual though, random and recurring all night, so maybe it’s not a perfect fix just yet. Another interesting thing I noticed is when I arm a mono track and load something like a Nembrini amp to record a guitar track, the AUv3 Nembrini sounds really off with a weird panning field and over-pronounced reverb. It just sounds wrong. But that same IAA Nembrini loaded in sounds just like it should. Go figure...
Please report these issues to them.
Of course, considering it’s still my main DAW. Crash logs with messages and fillable forms were already popping up on the screen, but AUv3 plugins sounding different than their IAA versions is definitely something worth reporting, and I wonder if others have experience this, or if this is somehow a new issue with the newly recognized interfaces like mine. Nevertheless I’ve been waiting for this specific fix for months and I’m glad it happened.
I haven't experienced it. It isn't likely that the interface is yhd issue. More likely that it is the particulars of the setup.
I_think_ I had something similar in apeMatrix when the Nembrini amps first came out. I’m pretty sure I was sending a stereo signal to the amp sim but just had the guitar plugged in so one side was guitar, other side was nothing.
@JoyceRoadStudios : if you can reproduce the issue, an effective way of demonstrating for the developer is to make a screen recording, post that to YouTube and post a link to it with the directions for reproducing the problem on the Auria forum. Posting a video helps the dev “get it”
Take a look to see if the sample rate is relevant. Make sure your project and interface are set to the same one. AP has had sample rate mismatch issues in the past.
I would also post reports of the crashes and not rely on the form that comes up after a crash.
Quite possibly, but there’s nothing actually changing in the setup. The only change is loading the amp AUv3 vs IAA. Cali Reverb “crystal clean” preset as AUv3 sounds really off, and the same as IAA sounds perfect. I will check later how both record to see if it’s just the headphone out on my interface or an actual difference. Let me know if you hear a difference AUv3 vs IAA on a reverby preset with something like Mrh810 or Cali.
My interface is a simple 1 channel guitar in and a stereo headphone out. Never have problems in any DAWs as the recorded track just shows two identical mono waves, so I’m assuming my signal is mono that’s being taken as mono l+r, and both the daw track and audioshare default to stereo image. But Auria Pro is different, arming a mono track my input is set at “input 1” and it sounds stereo in my phones. When I record it though it shows only one wave on the timeline but sounds stereo. If I arm a stereo track in AP, input shows 1/2 and only sounds in one side of my phones. But it shows up on the timeline as two waves and still sounds mono. I’ll figure out more soon on this...
Yes I was thinking it could be a sample rate issue. My interface switches sample rate automatically. So it’s plugged in and I open AP which begins a project at 48k. Then when I simply load up a Nembrini amp or the new 808 pedal into an fx slot on a mono track, it keeps crashing AP. So I wonder if the interface, the plugin, and the daw all calibrating sample rate makes it crash. I will check later at other sample rates. I’ve never had it crash like that until last night, which is why I thought it could possibly be the new recognized interfaces which have usbc as well as seemingly different interactions with the mic disable, as stated in AP’s updates fix list...
Have you tried it with a stereo track?
As soon as you know the answer, please post on the Auria forum. There have been mono/stereo tweaks In the last few AP versions.
@JoyceRoadStudios : an easy way to tell if it has to do with your interface is to create/record a mono sound file somewhere outside of Auria. Without your interface connected, create a new Auria Pro project. Create a mono track. Import your mono file. Add the AUv3 and see how it sounds through the headphones or speakers.
FWIW, on my iPad 6 running a project I just created that is just one mono track with the Nembrini 808 and Cali Reverb is fine. I tried at both 44k and 48k. I can upload the projects for you to try on your iPad.
Send it to me I’ll take a look now.
I will OM the link momentarily.