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.
Auria Pro + Fab Filters
Being relatively new to the wonderful world of Fab Filters, I am very impressed at the difference what I bought has made. PRO-MB, PRO-L and MicroWarmer are working well for me to shape end results, and the Timeless 2, Volcano 2 and Saturn effects are lovely. In all cases, the presets are proving to be a great place to start.
But what is not so good is a problem a forum member - I forget who - said had been reported over a year ago, and is still not fixed. That being the way these filters lose the description of what setting is in use. Even though the setting is still applied, what is shown reverts to Default Setting. Sometimes, in the creative blur we all experience, remembering what was set isn't easy. So I really wish the developers would extract the digit and sort this out. Can't understand why they haven't bothered.
Other features, which I hope Auria Pro development can add, are the ability to reorder filters on-the-fly in the channel strip, and duplicate filter combos /settings across different tracks. Is the latter already possible? If so, then I've missed how to achieve it.
Comments
Yes, this is annoying and unhelpful. It has been reported on longer than I year I'm pretty sure. Several I think. I'm not sure with these being plugins if it is a Auria issue or FabFilter one.?
>
Perhaps someone else knows for sure? AP development seems to get around to things, eventually. FF development, not so much, judging by when these filters first appeared and what has happened since.
If it is down to AP development, then I would be most grateful for a Filter fix. Also, the ability to reorder filters as I was saying above. So many times I've had an idea to do something only to realise it needs to be before another filter. Being able to slide them up and down in place would be a real time saver.
I'm not one to harp on developers to fix something that I can easily fix myself with a tiny extra step, i.e. in this case saving my patch or preset to custom so I know where it is and what it's called.
The two improvements in the quoted part, however, I'd love to have. A track template and re-ording the channel strip effects would go a long way towards making setup a breeze considering I have a synth setting for each of my three hardware synths and two or three classic guitar setups.
Sure saving our own presets is easy enough, but not what I meant. I was thinking more of rifling through factory presets and categories, coming upon something we like, then moving on to the next stage. Then, in another track wanting to use the same preset we happened upon, and not knowing which it was among several similar names. Fixing the preset bug would sort that out.
Being able to shift around the order in the Chanel Strip would also allow for some highly creative and serendipitous accidents of sound.
Was gonna purchase the iap's until I read this thread. For The price that they are charging, I would expect 100% functionality. It's a no go for me.
@WaveMachineLabs patch ur app dawg
You're always just about to purchase an Auria product...
>
FWIW, I waited for the sales on all but one of the filters I bought. But despite the on-going issues mentioned, I am very pleased with all the filters, in terms of what they offer, and don't regret buying them for a second.
Yes, products that are expensive by IOS standards should hold themselves to a higher standard, but not buying due to a minor irritation is denying yourself more than it is punishing the tardiness of the developer.
For as much of a mark I am for Auria, and I do really love it, I admit there are some bugs & quirks that remain that are irritating.
This FabFilter preset issue is one. Another is how the in app convolution reverb responds to some IR files. I've tried different files of chambers, plates & halls that will have three versions, for example:
hall_r.wav
hall_l.wav
hall_ m-s.wav
These files cause an awful distorted sound to erupt at ear drum damage levels. Then some files that are labeled straight (largehall.wav) will produce the reverb but then another delayed repeat of the dry signal a second later, extremely unusable. I've tried all the files that make the Auria convolution reverb bug out on two convolution reverb apps available on the app store that I have (AltiSpace & Mobile Convolution Reverb) and they worked no problem.
I realize Rim and the WaveMachine guys are busy getting the next update ready and perhaps working on a totally new project, but the preset labeling & convolution reverb issues have been reported months ago.
And I realize someone may think "If the other convolution reverb apps work, just use them". Well, it's for the same reason AU's are so exciting and we all want our favs to get AU functionality; I want as many of my effects and processes to be self contained within my DAW Auria as possible AND that way can use them in multiple instances. That's what makes the Auria plugins so badass, you can use them on different tracks simultaneously.
Yeah, the one thing that comes up again and again with AP is what I think of as the 'Cult of Auria' where constructive criticism seems to vanish into a long to do list, well behind the priorities of what development wants. I can see how, if they have a great idea for something big, that would seem like the thing which should take poll position. But from a user POV, as your example proves, there is frustration when what is already there doesn't work properly and doesn't get fixed fast. Smaller devs, such as the excellent Brambos, are on to bugs much quicker, ISTM.
Auria Pro is a fantastic app. It could be even better, and is in everyone's interest to make it so. Especially the small things that could surely be addressed without waiting months. For example, the issue with Dropbox. As I've spoken about in other threads, AP has to be manually redirected every single time I want to import a .wav file from my Dropbox, even within the same session. If it could just remember where it was looking that would save such a lot of time. Also, although AP is supposed to be able to import multiple files, I've never got this to work as I'd like. I'd like a command that allows me to choose files from any location, and then import them at the same time, positioned on a track or tracks, sequentially in the order chosen.
Agree 100% @Nkersov
I can't just blow smoke about something just because I love it. It's like relationships in life, if you care enough about someone, be honest. Same goes here.
If WaveMachine is prepping some other big app or project then let it be known and then maybe slow responses to bugs in their existing centerpiece app could be understood.
I feel that great secret we all think we're in on about iOS music production being so convenient and revolutionary on so many levels is about to get exposed bigger than we can imagine. Who knows if AVID, Ableton, or even a Pro Garage Band or iOS Logic version by Apple would be introduced to capitalize on the popularity.
Auria needs to maintain it's reputation of quality if it wants to compete in a possible expanded iOS music production scene AND if it wants to maintain the user base it currently enjoys...
Indeed. There is a saying, 'don't sweat the small stuff' but in this case it is the small stuff that will inform existing customers descision as to what to add, and potential new customers given the kind if choices you suggest.
Glad your paying attention
If you use a factory preset, and need the plug to remember the name of that preset next time you open a project, just save that preset to Aurias preset system, and the project will open using that preset. It's a workaround, but it works. I don't think we'll ever see this one sorted out (contact fabfilter, make them aware of the issue, it's their product)
I think you mean yore.
>
Okay, thanks for that.
As for not getting it sorted out, it's a pretty poor show if what is touted as premier tools can't work up the enthusiasm to fix what must be a small bug,
They do keep the plugs up to date, fix issues etc. But this particular preset-list issue, I just dunno what's up with that
>
Well, what appears to be up with it, is that it hasn't been fixed in a very long time. Why is turning into one of those mysteries that may never be answered.
your > @johnn said:
lol go look how much the desktop app is and Ive never had this problem. Not saying it doesn't happen. Maybe you should try fabfilter.
I already own the desktop versions. That's not the point.
>
Agreed. Either these apps work as advertised, or they don't. In which case a fix is required.
Implying that if we want proper working versions we should buy the desktop model turns IOS into little more than cheap advertising.
It is a mystery. But at the end of the day they work as advertised, which is all that matters :-)
>
Well, I'd agree that these filters do a fantastic job. They are the killer feature that is making me use Auria Pro more often than the alternatives.
But any on-going problem reported well over a year ago has zero excuse for not being fixed. The impression being given is that no one at Fab Filters is all that concerned with the cheap cousins. Ultimately, ignoring customer concerns will backfire and cost sales.
Expect all you like with Auria; the reality is it’s one guy coding a very complex app on a quirky, evolving OS. Then FabFilter offers their stuff cheap for Auria and, like it or not, they aren’t putting much into it after that.
I see what works and what doesn’t—which changes over time—and try to make the best of it. I think the bottom line is that, if someone puts out an iOS DAW that has what Auria has and works better, then go for it. I’d be happy to join the cult of any app that can do it, but all the ones I’ve tried have their strengths, weaknesses, and annoying things that don’t exist or don’t work. For the price of iOS apps, I feel it makes sense to focus on the positives.
I think all of us who have bought AP and FF apps are focusing on the positive. We regularly sing the praises of what is good, and there is is a LOT that is good about AP and FF. But this is commerce, not a charity.
Anyone selling apps has a relationship with their customers. The majority of developers are conscientious and keen to iron out bugs. Any company that simply can't be bothered to fix something broken, and adopts an attitude that we should be grateful they even bother, is getting it wrong.
Are you referring to Rim? As far as I can tell, he works hard on an app that requires a huge amount of upkeep. He has to pick and choose what to tackle first, and what is or isn't practical.
Customers can complain all they like. And those who expect "100% functionality" are probably smart to stay away from complex apps on iOS. My point was what I expect and how I deal with the situation.
The reality of software development is that bugs always exist, and it's very common for bugs that are considered low priority to go unfixed for a long time - this isn't unique to Auria.
In my real job (3D graphics and illustration) I beta test professional products with high price tags, and believe me they all have bug databases with thousands of reproducible bugs in them. Typically the dev teams have to prioritise according to the severity of the bug. Unfortunately that means that many bugs go into low priority lists and simply never get fixed. This isn't because the company doesn't care or that the devs are lazy, it's simply because time constraints mean that it's impossible to fix every bug that crops up in a complex app.
And most of the time this is OK, and users accept it as the reality of software development, even if they've forked out thousands for a pro package. The problem only really becomes an issue if you personally encounter a bug that is deemed low-priority that happens to impact on your workflow, in which case of course it becomes annoying. I've encountered this a few times, and generally the best approach is to explain directly to the company or devs why the issue matters to you, and hope that it gets fixed. Sometimes it does, sometimes it doesn't, in my experience anyway.
I agree. I dealt with the situation by just deleting Auria Pro. I'm sorry to say but AP felt like an unfinished product. Maybe when its a bit more stable I'll try again. Lucky it was on sale for 50% otherwise I would have asked for a refund.
Now I agee wholeheartedly with that, but I'm not trying to shit on the app or expect miracles. I'm not a big sports guy but situations like these are like what I saw in that Football thread yesterday. These guys who have so much passion & love their team will be brutally honest on how the QB is performing. Doesn't mean they don't like their team anymore, to the contrary, they get so unnerved by the bad plays because they DO love the team so much.
I have actually had some musician friends bust my balls for how much I go on about Auria. I evangelized how much Auria Pro is a for real, great quality DAW, and I still do. I realize I'm spoiled with the quantity & quality of these apps and I do overlook most non project life threatening bugs.
@Nkersov started the thread saying as much, he loves Auria, spent some larger than normal dough on the FabFilter apps, and just was curious about a seemingly easy fix. I know how hard Rim works and am amazed that Auria is as smooth and trouble free as it is. Nothing but good joojoo from me towards Auria.
See, this is what irritates me about anything to do with AP; the cult of Rim. _Nobody _is suggesting for a second that the man is not hard working, dedicated and able to produce fabulous apps.
At the same time, no individual or product is above criticism, especially from customers. Simply asking that a bug is fixed should not result in a post that pretends the developer is under attack. He is not, nor is AP.