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 2.06: AU support, IOS10 & MIDI keyboard! (EDIT: 2.07 and 2.08 updates with bug fixes!)

1…78101213…15

Comments

  • WaveMachineLabsWaveMachineLabs
    edited October 2016

    Auria supports full AU parameter automation, but just not from within an AU's GUI. This is a limitation with the way Apple implemented AU in iOS. Hopefully they'll fix this at some point. But for now, you can automate any AU parameter by drawing a curve in the editor, like you would with any of Auria's own parameters.

    Es ist Klar?

  • theconnactictheconnactic

    Lol at the german in the end.

  • [Deleted User][Deleted User]

    @WaveMachineLabs said:

    Es ist Klar?

    See we knew it! :p ;)

  • excesseyeexcesseye

    @WaveMachineLabs said:
    Auria supports full AU parameter automation, but just not from within an AU's GUI. This is a limitation with the way Apple implemented AU in iOS. Hopefully they'll fix this at some point. But for now, you can automate any AU parameter by drawing a curve in the editor, like you would with any of Auria's own parameters.

    Es ist Klar?

    Great, thanks for clarifying!

  • wimwim

    @brambos said:
    Reports are 50/50 at this point ;) At least on @wim 's system it looks sample accurate.

    Well ... sample accurate for RuisMaker in my tests. iSEM was just under 2ms delayed. Now I'm seriously debating with myself if I want to make myself a lab rat and upgrade from iOS 9.35 to 10 to see if I get the inconsistent results reported by others. Nah. Think I'm gonna enjoy a stable and predictable environment for a few more weeks.

  • JohnnyGoodyearJohnnyGoodyear

    @WaveMachineLabs said:
    Auria supports full AU parameter automation, but just not from within an AU's GUI. This is a limitation with the way Apple implemented AU in iOS. Hopefully they'll fix this at some point. But for now, you can automate any AU parameter by drawing a curve in the editor, like you would with any of Auria's own parameters.

    Es ist Klar?

    Geistreich with a dash of hervorragend mate...

  • theconnactictheconnactic

    Lol!

  • AndyPlanktonAndyPlankton

    @Nkersov said:

    @theconnactic said:
    @Nkersov, you have to arm the track to hear the notes you play. I don't have your particular AU to try, but iSem, Ruismaker and FM Essentials appear just fine. AUs appear in the same list as IAA instruments, but with a different color - green, I think.

    >

    Yep. Edited my post as I'd already discovered the green section. Would be helpful if these were listed under AU section, and IAA under their own section, etc. Cubasis makes this more intuitive. Thanks for the reminder about arming tracks to hear anything.

    I quite like the fact they are in one list, All instruments in the same place

  • theconnactictheconnactic

    [2]

  • brambosbrambos

    @WaveMachineLabs said:
    This is a limitation with the way Apple implemented AU in iOS. Hopefully they'll fix this at some point.

    I haven't looked into it from the host's side, but you should be able to put a Key-Value-Observer on the ParameterTree, right? Or does that not work in the current implementation? I can see at the plugin's end whether a Host-KVO is added to the tree. But so far I'm a lonely panda :|

  • crouchiecrouchie

    @Fruitbat1919 said:

    @theconnactic said:

    @Fruitbat1919 said:
    Yeah it's a pain, I've just learnt to live with it. I just add midi notes in on a pass and then 'rewind' and do it again. Suppose it's from my tape days?

    You don't need to rewind: just activate aito-return and it will auto-rewind when you stop the record.

    Where's the fun in that? :p

    Made me laugh a lot that did....

  • skiphuntskiphunt

    @pierre said:
    Loving the update too, found a not compelling AU though, apefilter makes the whole thing crash as soon as you load it, anybody has the same issue ?

    I've occasionally had that issue with the Ape AUs in AUM too.

  • skiphuntskiphunt

    @WaveMachineLabs Never thought you were German... but when I'd read others say that, I'd free-associate the name "Rim" with "Wim" Wenders (German director). I wonder if there's some glitch group free-association going on between the unusual name "Rim" and "Wim"?

  • excesseyeexcesseye
    edited October 2016

    @WaveMachineLabs said:
    Auria supports full AU parameter automation, but just not from within an AU's GUI. This is a limitation with the way Apple implemented AU in iOS. Hopefully they'll fix this at some point. But for now, you can automate any AU parameter by drawing a curve in the editor, like you would with any of Auria's own parameters.

    Es ist Klar?

    edit - Never mind, figured it out. Thanks!

  • High5deniedHigh5denied

    I thought I was the only one that thought Rim was from Germany. And then learned he was not. lol

    Die Toten Hosen! Is the only German I know.

  • WaveMachineLabsWaveMachineLabs

    @brambos, the issue is there's no way the host can tell when the user touches the screen of an AU (to begin moving a control), and when it's released. That's an important requirement for knowing when to start storing automation parameters. The problem with using only KVO is you also get a notification whenever the host itself writes a parameter back to the AU. So it works fine if you only playback or only record automation (you can ignore KVO notifications when you're playing back), but if you need to overdub (record and playback) automation, it gets really tricky. Apple needs a better approach to automation other than KVO in my opinion.

    tldr; I ended up leaving the code in place for GUI-based automation, but it's not reliable when playback and recording needs to be done (overdubbing automation) .

    Rim

  • brambosbrambos

    @WaveMachineLabs said:
    @brambos, the issue is there's no way the host can tell when the user touches the screen of an AU (to begin moving a control), and when it's released. That's an important requirement for knowing when to start storing automation parameters. The problem with using only KVO is you also get a notification whenever the host itself writes a parameter back to the AU. So it works fine if you only playback or only record automation (you can ignore KVO notifications when you're playing back), but if you need to overdub (record and playback) automation, it gets really tricky. Apple needs a better approach to automation other than KVO in my opinion.

    Clear story. Thanks for clearing that up. I was wondering what the difficulty was, but I remember having to solve similar issues back in my VST host on Windows. The solution I had back then would not work in a multi-touch environment.

    Cheers!

  • [Deleted User][Deleted User]
    edited October 2016

    Not me, Cubasis has its very own special strengths and it's a whole lot easier on midi and way less CPU intensive IMHO for me. I think having both is the best of both worlds!

    @Fruitbat1919 said:
    The keyboard and AU have made that much of a difference, I've deleted Cubasis as well as GarageBand :o

  • theconnactictheconnactic

    I won't delete Cubasis our Garageband either, for sometimes I need that bridge for Cubase and Logic Pro X. But this update killed the need for any of them. Still on iOS9: when I uptade to 10, perhaps I'll be back a litle to Garageband, because of Music Memos.

  • theconnactictheconnactic
    edited October 2016

    Double post!

  • richardyotrichardyot

    Music Memos are available on iOS 9.

  • theconnactictheconnactic

    The app store won't let me download on the iPad: it's says iOS10 is required!

  • studioABstudioAB
    edited October 2016

    @theconnactic said:
    The app store won't let me download on the iPad: it's says iOS10 is required!

    re. Music Memos,
    When I tried to download on an iOS 9 device it gives a message that the current version requires iOS 10 then asks me if I want to download the last compatible version. Of course I had the app on my device a while ago and had deleted it so I don't know if that makes a difference in giving me that option to get the older version.

  • theconnactictheconnactic

    I never got the option of instaling the latest compatible version.

  • [Deleted User][Deleted User]

    Is there a trick to getting the midi keyboard working? Can't get it to trigger au, iaa, or sampler. Tried several of them. However the piano roll keyboard is working. Then I rebooted and same thing. 12.9 pro on ios10

  • wimwim
    edited October 2016

    @jenkweb said:
    Is there a trick to getting the midi keyboard working? Can't get it to trigger au, iaa, or sampler. Tried several of them. However the piano roll keyboard is working. Then I rebooted and same thing. 12.9 pro on ios10

    In the FX / Port settings for the channel, you need to set Input: All, and either pick a channel number or All. If you pick a channel, then when you bring up the keyboard, it needs to match. You also need to arm the track to hear anything.

  • theconnactictheconnactic

    @jenkweb said:
    Is there a trick to getting the midi keyboard working? Can't get it to trigger au, iaa, or sampler. Tried several of them. However the piano roll keyboard is working. Then I rebooted and same thing. 12.9 pro on ios10

    Arm the track! The keyboard only works with the track is armed!

  • MusicInclusiveMusicInclusive
    edited October 2016

    @Fruitbat1919 said:

    @WaveMachineLabs said:

    Es ist Klar?

    See we knew it! :p ;)

    Es ist Vorsprung durch Technik :wink: ( aber das ist Audi pro nicht Auria Pro. Hmmmm... :flushed: )

    Hmmmm.... oder vielleicht,

    hervorragende Musik durch Technik

    :wink:

    ("... as we observe that people have now begun to say" (or will do :wink: perhaps ) )

  • MusicInclusiveMusicInclusive
    edited October 2016

    @WaveMachineLabs said:
    Not sure why everyone thinks I'm German, but maybe I should start learning Deutsch ;)

    Rim

    Maybe you should just give in and learn Welsh, Yr ymyl, since it is the land of song! :smiley: Then you'd have an edge over everyone else (look it up :wink: )

  • theconnactictheconnactic
    edited October 2016

    Lol!

    Folks, I seem to have found a bug, can someone confirm it? It's the following: in a project that we input the tempo by tapping, sometimes we get tempos like 115,43 or others like that. Well, after creating a new project and inputing the tempo by tapping, getting the said value, I noticed that every time I tried to record with the keyboard, I'd have really bad MIDI dropouts. Not when jamming while playing the song though: **only when I tried to record something. ** Changing the tempo to a value without decimals - in this case, 115 - solves the issue immediately.

    Is someone else also experiencing this?

Sign In or Register to comment.

© Vanilla Keystone Theme 2025