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 Store

Loopy Pro is your all-in-one musical toolkit. Try it for free today.

Auria Pro + Fab Filters

2»

Comments

  • @JRSIV said:
    @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.

    >

    Indeed. I am kind of getting converted from Cubasis. It is because I'm getting more into Auria Pro, that I'm so keen for it - and the filters associated - to work as they should. Just asking for descriptions of presets to stay visible should not really be considered a major request, or be met by the Rim defense brigade.

  • edited January 2017

    @richardyot said:
    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.

    Of course, you are correct.

    However, I balance that against the many developers we have for IOS, who do respond much faster to bug reports. Okay, there will always have to be stuff that takes priority. But surely something reported well over a year ago, that looks to be a relatively easy thing to address, ought to have been fixed?

  • @Nkersov said:

    @richardyot said:
    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.

    Of course, you are correct.

    However, I balance that against the many developers we have for IOS, who do respond much faster to bug reports. Okay, there will always have to be stuff that takes priority. But surely something reported well over a year ago, that looks to be a relatively easy thing to address, ought to have been fixed?

    Honestly, I can't speak for Rim and don't pretend to. My own experience of beta testing Auria Pro was that critical bugs were fixed very quickly, and less critical bugs weren't - and this is exactly my experience with beta testing professional GFX apps on the desktop.

    When you have a long list of bugs there is no choice but to prioritise, and complex apps always have lots of bugs (always!).

    A soft synth (for example) is a considerably simpler app than a DAW that performs many functions (and contains two soft synths of its own as well as a sample player). My guess is that Auria is more complex than the average app and simply contains a larger list of bugs as a result, which means that less critical bugs may get ignored because there is a long list of more important issues to fix ahead of them.

    The best approach would be to file a bug report on the Auria forum (there is a sub-forum just for bug reports) and hope it gets fixed in time. As I said previously everyone has different views on bugs, and what may be a minor bug to me can be much more annoying to other users, and vice-versa. If enough users complain the bug may get given higher priority.

  • @richardyot said:
    The best approach would be to file a bug report on the Auria forum (there is a sub-forum just for bug reports) and hope it gets fixed in time. As I said previously everyone has different views on bugs, and what may be a minor bug to me can be much more annoying to other users, and vice-versa. If enough users complain the bug may get given higher priority.

    >

    Fair enough. :)

  • @Nkersov said:

    @lovadamusic said:
    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.

    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.

    Seems any answer to the critics of Auria Pro gets this defensive "Cult of Rim" response. I would defend any app like AP the same. I was really responding to the notion that "For The price that they are charging, I would expect 100% functionality," and some of the expectations here. Richardydot's explanation of "the reality of software development" is how I see it as well.

    "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."

    I merely asked if that refers to Rim. If not, then what's the statement's relevance to this thread?

  • edited January 2017

    @lovadamusic said:
    I merely asked if that refers to Rim. If not, then what's the statement's relevance to this thread?

    No. As usual, you're attempting to create a problem that doesn't exist. Not biting.

  • At the end of the day people and companies do whatever the hell they want. Even devs that are usually responsive ignore some things that should ne easy and work on things they want to work on. Some devs don't even respond. I've asked one dev something multiple times and he seems to ignore me. Whatever. Be grateful for what you have and support or wait 10 years until it's all sorted out and then jump in.

  • @vpich said:
    At the end of the day people and companies do whatever the hell they want. Even devs that are usually responsive ignore some things that should ne easy and work on things they want to work on. Some devs don't even respond. I've asked one dev something multiple times and he seems to ignore me. Whatever. Be grateful for what you have and support or wait 10 years until it's all sorted out and then jump in.

    >

    I have jumped in, with both feet, and generally am VERY happy with both AP and Fab Filters. But if no one ever said a word about things that didn't work, not even the most dedicated developer could fix them.

  • edited January 2017

    I concur.

  • I'm commited. ios is the most exciting music period for me in ages. Right now i am second in line at a carwash with both kids in the backseat, checking levels on a gadget song i am working on, in the car speakers. This is the future. So i make what works work (or i try to) and am way more prolific than i have been in a while.
    But yeah. I would like stuff to work as advertised. Hopefully friendly, gentle nudging is what it takes to get it done.

  • @Nkersov said:

    @lovadamusic said:
    I merely asked if that refers to Rim. If not, then what's the statement's relevance to this thread?

    No. As usual, you're attempting to create a problem that doesn't exist. Not biting.

    You post statements and then don't want to explain or back them up. That's okay. You don't even have to waste time with answers like the one above, as it adds nothing.

  • @Nkersov said:

    @vpich said:
    At the end of the day people and companies do whatever the hell they want. Even devs that are usually responsive ignore some things that should ne easy and work on things they want to work on. Some devs don't even respond. I've asked one dev something multiple times and he seems to ignore me. Whatever. Be grateful for what you have and support or wait 10 years until it's all sorted out and then jump in.

    >

    I have jumped in, with both feet, and generally am VERY happy with both AP and Fab Filters. But if no one ever said a word about things that didn't work, not even the most dedicated developer could fix them.

    I don't remember anyone suggesting that people shouldn't post about what they think needs fixing.

  • @richardyot said:
    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.

    As you said, bugs in apps/program always exist, but, we all have to remember that there's bugs that crashes the whole app, or, in the aboved mentioned thread, a old bug that we can get to workaround...

    Auria Pros weakest section that needs to be updated/bugfixed is the Midi-handling, not small things around...
    Auria Pro is however an fabolous amount of fantastic coding... Thanks Rim, keep up the good work...

  • While I find it annoying that the presets don't stay, the quality of the plugins is such that its pretty silly to not buy them if that's the only reason. As to the "cult of auria", the level of posturing in this thread over something so minor is bordering on the ridiculous.

  • @vpich said:
    I'm commited. ios is the most exciting music period for me in ages. Right now i am second in line at a carwash with both kids in the backseat, checking levels on a gadget song i am working on, in the car speakers. This is the future. So i make what works work (or i try to) and am way more prolific than i have been in a while.
    But yeah. I would like stuff to work as advertised. Hopefully friendly, gentle nudging is what it takes to get it done.

    We are in full agreement. IOS is the future of music making. Apps such as Auria Pro, Fab Filters, Blocs Wave, Gadget, the Brambos and VirSyn products, to name but a few, make it a very exciting time. Onwards!

  • edited January 2017

    @rickwaugh said:
    While I find it annoying that the presets don't stay, the quality of the plugins is such that its pretty silly to not buy them if that's the only reason. As to the "cult of auria", the level of posturing in this thread over something so minor is bordering on the ridiculous.

    >

    Absolutely. I've always tried to make it abundantly clear how good these products are. Unfortunately, there is an element that will not accept any criticism, even when it it intended to help the product be even better. ;)

Sign In or Register to comment.