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.

Coming AUM update (now live, and on easter sale!)

245

Comments

  • My app of the year just got even better. Essential and with first class support.

  • @carol said:
    My app of the year just got even better. Essential and with first class support.

    I couldn't agree more B) Not only is @j_liljedahl doing all this, he is also trying to educate other developers in the black art of IAA implementation.

    He obviously has some magic that gives him 36 hours per day

  • @AndyPlankton said:

    @carol said:
    My app of the year just got even better. Essential and with first class support.

    I couldn't agree more B) Not only is @j_liljedahl doing all this, he is also trying to educate other developers in the black art of IAA implementation.

    He obviously has some magic that gives him 36 hours per day

    I think he has clones B)

  • @Fruitbat1919 said:

    @AndyPlankton said:

    @carol said:
    My app of the year just got even better. Essential and with first class support.

    I couldn't agree more B) Not only is @j_liljedahl doing all this, he is also trying to educate other developers in the black art of IAA implementation.

    He obviously has some magic that gives him 36 hours per day

    I think he has clones B)

    Ahhh, so he has been to Kamino, that explains it :D

  • @Wally said:
    Amazing work .
    I notice AU presets will be saved , but my biggest problem trying to integrate AUM is indeed saving presets , but for IAA & AB . IAA apps dont seem to save their settings when saved in Aum , & if Aum is loaded in AB for statesaving ,the apps in Aum are not statesaved ,even if SS compatible .
    I have been loading generators in AB to be able to StateSave them , then using their AB input into Aum , but this still leaves the problem of FX apps .
    Hopefully the problem of saving apps settings can be solved , either by Kymatica in Aum ,or AB by having StateSave function through different layers of hosts . e.g AB>Aum>app.

    Yes, if Audiobus would decide to let me in on their state saving mechanism that would probably be possible, if not then there's these options:

    • Try to use AU apps instead, they support state saving in AUM out of the box.
    • I'd need to invent my own mechanism for IAA state saving (doable), just like Audiobus did, and then try to get every other developer on board (less doable)
    • Live with the fact that Apple doesn't have state saving for IAA apps, complain to Apple about it, save presets locally in each IAA app and take notes.
  • There once was a channel on Aumy

    Who felt rather naked and lonely

    So she dressed up with inputs
    And thingies and outputs

    And sang with her friends in their homey.

  • @Cliffy said:

    I love the fact (weirdly) that I have absolutely NO idea what nodes: MIDI filter with channel mask and note range means.

    I'm with you on that. I probably understand about 6% of the update's listed details, yet I'm still abnormally excited about it.

    I should hire someone to write more friendly release notes.. :)

    MIDI filter means for example that you can select on what MIDI channel an AudioUnit synth like iSEM or Viking should receive on. And also which note range, so you can make part of your keyboard play one synth, another part plays the other synth, and a third synth responding to all keys at the same time, etc.

  • edited March 2016

    @audiblevideo said:
    @j_liljedahl if it weren't so good (already) I'd hate you like that "ok guy" in high school who is jealous of the jock who's also a nerd and dating the girl he's always had a crush on. Who you end up being best friends with in the end because he's that awesome. :)

    Haha :) I was that nerd who didn't get to date the girl, but my best friend did (and I hated him).. So instead I stayed at home and learned coding ;)

  • @AndyPlankton said:
    • Allow placement of AU plugin views out of screen.

    does this mean I can have virtual screens - Avatar style :D

    No.. :) But it means you can drag a plugin out of the way temporarily without having it bounce back into view like it currently does.

  • @j_liljedahl said:

    @AndyPlankton said:
    • Allow placement of AU plugin views out of screen.

    does this mean I can have virtual screens - Avatar style :D

    No.. :) But it means you can drag a plugin out of the way temporarily without having it bounce back into view like it currently does.

    :) Cool

  • @j_liljedahl said:

    @Wally said:
    Amazing work .
    I notice AU presets will be saved , but my biggest problem trying to integrate AUM is indeed saving presets , but for IAA & AB . IAA apps dont seem to save their settings when saved in Aum , & if Aum is loaded in AB for statesaving ,the apps in Aum are not statesaved ,even if SS compatible .
    I have been loading generators in AB to be able to StateSave them , then using their AB input into Aum , but this still leaves the problem of FX apps .
    Hopefully the problem of saving apps settings can be solved , either by Kymatica in Aum ,or AB by having StateSave function through different layers of hosts . e.g AB>Aum>app.


    Yes, if Audiobus would decide to let me in on their state saving mechanism that would probably be possible, if not then there's these options:

    • Try to use AU apps instead, they support state saving in AUM out of the box.
    • I'd need to invent my own mechanism for IAA state saving (doable), just like Audiobus did, and then try to get every other developer on board (less doable)
    • Live with the fact that Apple doesn't have state saving for IAA apps, complain to Apple about it, save presets locally in each IAA app and take notes.

    @j_liljedahl thanks for response .
    @Sebastian , @Michael (please see above ) how about it ? could Statesave operate through "layers" , so an SS app in AUM or other host could still Statesave if Aum were itself loaded into AB ? Surely this would be useful to all concerned , & far from commercial "competition" would keep AB a necessary purchase even if other hosts are preferred by users for routing & midi control .
    It would certainly help users & further the IOS musicmaking workflow . Some devs have yet to implement StateSave , maybe this would encourage them , & any alternative would be unlikely to succeed.

  • I think its time to write a gushing 5 star review. You?
    If this app has not yet been rewarded with top music app on the app store lets make it happen, ppl

  • The last year plus that I've had my Air 2 (my 1st Apple device after years of Android) I have been in awe of the quality of apps and results that are possible with just an interface and a slate no bigger than an old school composition notebook.

    My whole studio is based around it and I'm 'pig in shit' happy with the quality of everything and possibilities for the future.

    I'll look at what I've written or what some other reviews I've seen have said of the iOS music production movement and at times think "Is it being blown outta proportion?" But when things are announced like news of this update of AUM, I don't think so.

    This is a perfect example of why I put over what we're all involved in over so much. AUM is insanely cool and useful, but with all of this additional power? damn....Thanks Jonathan, you the man.

  • @Wally said:

    @j_liljedahl said:

    @Wally said:
    Amazing work .
    I notice AU presets will be saved , but my biggest problem trying to integrate AUM is indeed saving presets , but for IAA & AB . IAA apps dont seem to save their settings when saved in Aum , & if Aum is loaded in AB for statesaving ,the apps in Aum are not statesaved ,even if SS compatible .
    I have been loading generators in AB to be able to StateSave them , then using their AB input into Aum , but this still leaves the problem of FX apps .
    Hopefully the problem of saving apps settings can be solved , either by Kymatica in Aum ,or AB by having StateSave function through different layers of hosts . e.g AB>Aum>app.


    Yes, if Audiobus would decide to let me in on their state saving mechanism that would probably be possible, if not then there's these options:

    • Try to use AU apps instead, they support state saving in AUM out of the box.
    • I'd need to invent my own mechanism for IAA state saving (doable), just like Audiobus did, and then try to get every other developer on board (less doable)
    • Live with the fact that Apple doesn't have state saving for IAA apps, complain to Apple about it, save presets locally in each IAA app and take notes.

    @j_liljedahl thanks for response .
    @Sebastian , @Michael (please see above ) how about it ? could Statesave operate through "layers" , so an SS app in AUM or other host could still Statesave if Aum were itself loaded into AB ? Surely this would be useful to all concerned , & far from commercial "competition" would keep AB a necessary purchase even if other hosts are preferred by users for routing & midi control .
    It would certainly help users & further the IOS musicmaking workflow . Some devs have yet to implement StateSave , maybe this would encourage them , & any alternative would be unlikely to succeed.

    I've come to realize that IAA has so many quirks and issues that things just work better when loaded in AB. Inputs, effects, everything. I route all my AB inputs to AUM for output. I route all my AUM effect inserts back to AB to host the effects. Best of all worlds, state saving, no zombie apps. Save the AB preset often, when things crash, open back up AB and it all comes back to life.

  • @gburks please explain how you "route the AUm fx inserts back to AB to host the fx",
    my various attempts at this failed . Thanks .

  • @Rich303 said:
    Cool, but no pitch bend and mod wheels for the keyboard?

  • @Rich303 said:

    @Rich303 said:
    Cool, but no pitch bend and mod wheels for the keyboard?

    Not this time, unfortunately. It's on the list though, the 1.2 update is planned to focus more on MIDI related things.

  • When you're focusing on midi related things i would love to see a scales option for the keyboard (like the virsyn synths & animoog has) :smile:
    Do you have any date set for releasing the 1.1 update?
    Thank you!

  • @Wally said:
    @gburks please explain how you "route the AUm fx inserts back to AB to host the fx",
    my various attempts at this failed . Thanks .

    ... this probably folds in with the question of the benefit of 'Connecting AUM to itself via Audiobus' ?

  • @j_liljedahl said:

    @Rich303 said:

    @Rich303 said:
    Cool, but no pitch bend and mod wheels for the keyboard?

    Not this time, unfortunately. It's on the list though, the 1.2 update is planned to focus more on MIDI related things.

    Thanks. I wasn't sure if I missed anything. The good news is that I can still enjoy using Viking in AUM with my Novation Launchkey 25. :)

  • edited March 2016

    @constellation33x said:
    When you're focusing on midi related things i would love to see a scales option for the keyboard (like the virsyn synths & animoog has) :smile:

    That's on my list as well.

    Do you have any date set for releasing the 1.1 update?
    Thank you!

    Very very soon :)

  • @crzycrs said:

    @Wally said:
    @gburks please explain how you "route the AUm fx inserts back to AB to host the fx",
    my various attempts at this failed . Thanks .

    ... this probably folds in with the question of the benefit of 'Connecting AUM to itself via Audiobus' ?

    Already in AUM 1.0, you could do something like this in AB:

    AUM -> SomeEffect -> OtherApp
    CoolApp -> AnotherEffect -> AUM

    Now with version 1.1 you can also do:

    AUM -> SomeEffect -> AUM

  • My head asplode.

  • @j_liljedahl said:

    @crzycrs said:

    @Wally said:
    @gburks please explain how you "route the AUm fx inserts back to AB to host the fx",
    my various attempts at this failed . Thanks .

    ... this probably folds in with the question of the benefit of 'Connecting AUM to itself via Audiobus' ?

    Already in AUM 1.0, you could do something like this in AB:

    AUM -> SomeEffect -> OtherApp
    CoolApp -> AnotherEffect -> AUM

    Now with version 1.1 you can also do:

    AUM -> SomeEffect -> AUM

    I'm not sure I understand , I will have to test these routings , but when I tried before various combinations didnt work + there were only 4 AUM ports available .
    If new version , with Aum>Aum , makes this more possible then great, but I still think we'd be missing using AUM as a central ( midi controllable/ routable ) hub & mixer if we have to load everything through Audiobus .
    Also there are / will be other hosts , so I really think it would be most beneficial to IOS workflow if Audiobus devs extended the functionality of StateSaving to include apps within other host apps ,& would hope other users & devs help lobby for this .

  • @Wally said:

    @j_liljedahl said:

    @crzycrs said:

    @Wally said:
    @gburks please explain how you "route the AUm fx inserts back to AB to host the fx",
    my various attempts at this failed . Thanks .

    ... this probably folds in with the question of the benefit of 'Connecting AUM to itself via Audiobus' ?

    Already in AUM 1.0, you could do something like this in AB:

    AUM -> SomeEffect -> OtherApp
    CoolApp -> AnotherEffect -> AUM

    Now with version 1.1 you can also do:

    AUM -> SomeEffect -> AUM

    I'm not sure I understand , I will have to test these routings , but when I tried before various combinations didnt work + there were only 4 AUM ports available .
    If new version , with Aum>Aum , makes this more possible then great, but I still think we'd be missing using AUM as a central ( midi controllable/ routable ) hub & mixer if we have to load everything through Audiobus .

    Yeah, it does make the routing quite a bit more complex than simply putting SomeEffect as an insert in a channel inside AUM.

    Also there are / will be other hosts , so I really think it would be most beneficial to IOS workflow if Audiobus devs extended the functionality of StateSaving to include apps within other host apps ,& would hope other users & devs help lobby for this .

    I guess @Sebastian and @Michael will have to chime in about that one.

  • edited March 2016
  • Guys so Audiobus remote is still a must have to trigger my drum apps in AUM? One device only.

  • It's in the UK STORE NOW ,

Sign In or Register to comment.