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.

AUM - Many thanks to j_liljedahl / Kymatica

2

Comments

  • Yes they did see bottom right corner, in the menu.

  • @Poppadocrock said:

    Didn’t they add a tip feature in one of the recent updates?

    Yepp, there's a tip-jar in the settings and that's all cool :sunglasses:

  • The user and all related content has been deleted.
  • The user and all related content has been deleted.
  • @ehehehe said:
    I'm a linear guy preferring the timeline of Cubasis 3. I find AUM to be alot slower to setup stuff with too many moving pieces. Automation is an absolute must, and to me AUM seems like the pinnacle of ipad workflow workarounds. As a digital mixer it's quite awesome, but I have a feeling that it's a pretty small minority in the music community that this workflow works for. Great piece of kit if one need a workaround though.

    Yeah, I can't imagine trying to produce EDM in AUM, hence why I use Gadget and NS2. But for my live sound experiments, AUM is hard to beat. I simply use my fingers for automation.

  • edited July 2022

    @Poppadocrock :how did I not notice this? Thanks for pointing out the AUM tip jar. Duly tipped! :)

  • Thank you all for your support!

    I have no plans on going the subscription or subscribe-for-updates a la Loopy, but I do plan on IAPs for additional big features such as MIDI Clock Receive, DAW style editable audio tracks, Automation, Customizable performance screen, etc.

    The Tip Jar was a first test of the IAP implementation, and it seems to work as expected. Big thanks to every one who has tipped!

  • @j_liljedahl
    Thanks for speaking about the road plan
    But get back to the grind, cause I got money waiting for all those iap plans
    And yet again thanks for a damn kick arse app !!

  • edited July 2022

    IAP is, in my opinion, the best pricing strategy, at least for the end user. You pay once for what you really want. The "a la Loopy" strategy is probably more fair for the dev in term of incomes and planification but it can be very frustrating for the user. An exemple : I am still waiting for Beatsurfing's AU promised compatibility but so far, nothing can prove it will ever happen, even if you pay (in the future) for the upgrade subscription...

  • @Samu said:
    With 'Stage Manager' in mind since we'll be hooking out iPad's to a screen using HDMI iPadOS16 needs a way to allow us to select which device we prefer to use for audio-output.

    This since HDMI also carries audio and well...
    ...I do NOT like the current way iOS/iPadOS chooses which device to use (ie. plug-in order).

    Currently If I have my iPadPro hooked to an audio interface via a hub working all nice and dandy and connect the HDMI cable to the hub iPadOS automatically thinks I want to forward the Audio to my TV which is NOT the case. I then need to un-plug/re-plug the interface to get the audio back, like this is 2022 not early 90s. But hey it's Apple 'were doing it wrong' according to them...

    So if anyone is on 'beta' for iPadOS16 please do bombard Apple with requests that we need something similar to Audio & Midi Setup for iPadOS where we can choose our preferred Input & Output devices.

    You can switch between connected audio interfaces in the iOS Control Center or on AUMs Settings menu.

  • @j_liljedahl said:

    >

    You can switch between connected audio interfaces in the iOS Control Center or on AUMs Settings menu.

    Oh, that's good to hear :sunglasses:

    With the 11" M1 iPadPro with iPadOS15.5 I can not use an USB-Audio interface while my iPad is connected to my TV...
    I can however select my AirPods (or any BT Speaker) as the output when HDMI hooked to the TV via the control center but not any device connected to the iPad via USB...

    But still, support for multiple devices doing the same thing (Audio Input & Output) a system-wide control panel is the way to go.
    I might want to use my iRig Mic HD to record some sounds while recording the audio from my external instruments using a a line-input on the audio-interface.

    Maybe iPadOS could just 'Auto Aggregate' all connected audio devices and show all available inputs at once?!
    (Would be nice to be able to do IDAM between iPads as one example or from Mac to iPad not just iPad to Mac).

    And I do hope Files.app gets a proper 'format & eject' functions so I don't have to run First Disk Aid every time a hard-disk has visited the iPad :smiley:

    Cheers!

  • “DAW style editable audio tracks” !!!
    Very happy about that.

  • @Ben said:
    “DAW style editable audio tracks” !!!
    Very happy about that.

    +1

  • @Schmotown said:

    @Ben said:
    “DAW style editable audio tracks” !!!
    Very happy about that.

    +1

    +12

  • @anickt said:

    @Schmotown said:

    @Ben said:
    “DAW style editable audio tracks” !!!
    Very happy about that.

    +1

    +12

    +144

  • edited July 2022

    I never thought that in this thread so much interesting information is exchanged and even the current roadmap of the developer is made known to us, when I opened this thread.

    Many thanks to all.

  • @j_liljedahl said:
    Thank you all for your support!

    I have no plans on going the subscription or subscribe-for-updates a la Loopy, but I do plan on IAPs for additional big features such as MIDI Clock Receive, DAW style editable audio tracks, Automation, Customizable performance screen, etc.

    The Tip Jar was a first test of the IAP implementation, and it seems to work as expected. Big thanks to every one who has tipped!

    Oh my!

  • @ExAsperis99 said:

    @anickt said:

    @Schmotown said:

    @Ben said:
    “DAW style editable audio tracks” !!!
    Very happy about that.

    +1

    +12

    +144

    The approval rating seems to be growing exponentially.

  • I always have been a hardware / tactile person. And i realize now that how we interact with individual apps is in many ways similar to working with a piece of gear.
    Its not just about having physical knobs or being tactile or that special 'analog' sound.

    Its also about how it looks. How it feels. How we interact and associate.

    I think most ios users will know any app by name by just looking at the icon.
    We know how an speicific app sounds.
    And we like to have all midi processing apps than anything else😎

    Touch screens are extremely tactile.
    The interaction is just as direct as operating a piece of gear.

    A Modular rack or Animoog.
    Both are amazing in different ways.
    There is nothing in between.
    No keyboard or mouse. No confirming your actions on a seperate screen.
    No looking left or right or down😂

    But i am sure the brilliant mind of @j_liljedahl already realized this early on.
    Audio/music devs that are just as skilled at UX/UI as writing code are extremely rare
    AUM is the modular beating heart of iOS music making.

  • @cuscolima said:
    IAP is, in my opinion, the best pricing strategy, at least for the end user. You pay once for what you really want. The "a la Loopy" strategy is probably more fair for the dev in term of incomes and planification but it can be very frustrating for the user. An exemple : I am still waiting for Beatsurfing's AU promised compatibility but so far, nothing can prove it will ever happen, even if you pay (in the future) for the upgrade subscription...

    I think you've misunderstood Loopy Pro's model. You don't have to pay forward for updates that you may never see, or not see for some time. You can hold off paying after the 12 months. You'll still have the app as-is but you won't get further feature updates, only bug-fixes. When/If you feel like the newer features are worth it, you can pay the 12 month upgrade, and you'll get every update that has happened and that will happen for the next 12 months.

  • @j_liljedahl said:
    Thank you all for your support!

    I have no plans on going the subscription or subscribe-for-updates a la Loopy...

    Well, subscription or not, I want AUM to remain forever in the appstore.

    ...but I do plan on IAPs for additional big features such as MIDI Clock Receive

    😳

    DAW style editable audio tracks

    😱

    Automation

    🥲

    Customizable performance screen, etc.

    🥰

    Holy shit. These upcoming features are going to be massive game changers! And all I was hoping for was a customisable performance screen to make creating my twisted Ambient experiments a little easier without having to jump around between plugins. I mean, full blown audio tracks?! Automation!? MIDI Clock Receive!? What IS this magic?!

  • Let’s all tip what you can right now! Haha!

  • @mjcouche said:
    Let’s all tip what you can right now! Haha!

    This! 👆

    @j_liljedahl is doing so much for us that at this point it'd be a crime not to toss money his way.

  • edited July 2022

    @wim said:

    @cuscolima said:
    IAP is, in my opinion, the best pricing strategy, at least for the end user. You pay once for what you really want. The "a la Loopy" strategy is probably more fair for the dev in term of incomes and planification but it can be very frustrating for the user. An exemple : I am still waiting for Beatsurfing's AU promised compatibility but so far, nothing can prove it will ever happen, even if you pay (in the future) for the upgrade subscription...

    I think you've misunderstood Loopy Pro's model. You don't have to pay forward for updates that you may never see, or not see for some time. You can hold off paying after the 12 months. You'll still have the app as-is but you won't get further feature updates, only bug-fixes. When/If you feel like the newer features are worth it, you can pay the 12 month upgrade, and you'll get every update that has happened and that will happen for the next 12 months.

    Thanks wim, I understand now. Let see how this model will evolve in the time.

    [edit] All this has been discussed in many ways in other threads but I want to mention one big disadvantage of the Loopy model. This is a pure marketing principle : if you want to sell big, then you need a killer-feature. It means that a dev can decide to wait before publishing a new feature because he knows that this is the one that will convince the customers to buy the next 12 months. IAP is better as it can be immediately made available for purchase.

  • The user and all related content has been deleted.
  • @cuscolima said:

    @tja said:

    @cuscolima said:

    @wim said:

    @cuscolima said:
    IAP is, in my opinion, the best pricing strategy, at least for the end user. You pay once for what you really want. The "a la Loopy" strategy is probably more fair for the dev in term of incomes and planification but it can be very frustrating for the user. An exemple : I am still waiting for Beatsurfing's AU promised compatibility but so far, nothing can prove it will ever happen, even if you pay (in the future) for the upgrade subscription...

    I think you've misunderstood Loopy Pro's model. You don't have to pay forward for updates that you may never see, or not see for some time. You can hold off paying after the 12 months. You'll still have the app as-is but you won't get further feature updates, only bug-fixes. When/If you feel like the newer features are worth it, you can pay the 12 month upgrade, and you'll get every update that has happened and that will happen for the next 12 months.

    Thanks wim, I understand now. Let see how this model will evolve in the time.

    [edit] All this has been discussed in many ways in other threads but I want to mention one big disadvantage of the Loopy model. This is a pure marketing principle : if you want to sell big, then you need a killer-feature. It means that a dev can decide to wait before publishing a new feature because he knows that this is the one that will convince the customers to buy the next 12 months. IAP is better as it can be immediately made available for purchase.

    No.

    The WorkingCopy / Wotja / Loopy Pro model is the best thing possible, for both customers and developers.

    This is totally apparent as soon as you understand the model.

    But right, I often see that people misunderstand something in this.

    Just saying.

    Ok if you say it…no more arguments requested

    I still think that there are some unexpected « side effects » related to this model.

  • The user and all related content has been deleted.
  • @tja said:

    @cuscolima said:

    @cuscolima said:

    @tja said:

    @cuscolima said:

    @wim said:

    @cuscolima said:
    IAP is, in my opinion, the best pricing strategy, at least for the end user. You pay once for what you really want. The "a la Loopy" strategy is probably more fair for the dev in term of incomes and planification but it can be very frustrating for the user. An exemple : I am still waiting for Beatsurfing's AU promised compatibility but so far, nothing can prove it will ever happen, even if you pay (in the future) for the upgrade subscription...

    I think you've misunderstood Loopy Pro's model. You don't have to pay forward for updates that you may never see, or not see for some time. You can hold off paying after the 12 months. You'll still have the app as-is but you won't get further feature updates, only bug-fixes. When/If you feel like the newer features are worth it, you can pay the 12 month upgrade, and you'll get every update that has happened and that will happen for the next 12 months.

    Thanks wim, I understand now. Let see how this model will evolve in the time.

    [edit] All this has been discussed in many ways in other threads but I want to mention one big disadvantage of the Loopy model. This is a pure marketing principle : if you want to sell big, then you need a killer-feature. It means that a dev can decide to wait before publishing a new feature because he knows that this is the one that will convince the customers to buy the next 12 months. IAP is better as it can be immediately made available for purchase.

    No.

    The WorkingCopy / Wotja / Loopy Pro model is the best thing possible, for both customers and developers.

    This is totally apparent as soon as you understand the model.

    But right, I often see that people misunderstand something in this.

    Just saying.

    Ok if you say it…no more arguments requested

    I still think that there are some unexpected « side effects » related to this model.

    You get what you pay for, and you can use this for the rest of your live.
    And as bonus, you get even all new features for a year and probably security updates for longer.
    So, what is bad here?

    ONLY when there is - at any time after that first year - a version that finally offers something that you really want, you can opt to buy it. Just like a major new version from any other software, and again this is yours for your live.

    You never loose anything and, but your version will never fully deprecate like other software that has version 2, 3, 4 ... the older version will most likely never updated again for new OS versions or security.
    But the WorkingCopy and Loopy Pro licensing will normally always update your bought version for OS and security, even if you never ever buy a new version again.

    I really cannot see any "side effect" here!

    It is the perfect model for both developers and customers: Customers only buy again, when there are good enough new features, while developers are motivated to deliver them!

    Your thoughts?

    Thanks for your arguments that are perfectly valid. I don’t say that this model is bad. I say I see a risk that key features will be delayed till the next 12 months period purely for marketing reasons. I prefer a dev releasing immediately the key feature as an IAP. Apps like Loopy Pro and AUM have a huge potential for evolution, so I think both model will be ok here. Some other apps are much more limited and in this case, I fear the few key features will be deliberately delayed…that’s my point of view

  • @Iskander said:
    At the moment there is a lot of hype about STAGE MANAGER and everyone on the web is excited that something like this will (finally) be available soon.

    Many outside of our community are not aware that many of these features and more already exist in AUM for many years like moveable and resizeable windows.

    Big compliments to @j_liljedahl who worked his magic here. He showed early on what is feasible.

    Having worked in software development for over 40 years myself, I can well appreciate what my colleague has created here. And that with an app size of around 6 MB. Always admirable for me.

    He has already realized a long time ago, what other iPad or IPhone users had dreamed of so far (with iPhone it will probably stay that way for the time being). STAGE MANAGER will probably only run on M1 iPads for the time being.
    AUM on the other hand will run on ALL DEVICES.

    Many thanks again @j_liljedahl for a fabulous and admirable app, which offers so many functions, as hardly any other app. I am always thrilled with every (almost daily) use and discover more and more possibilities.

    For us music creators, AUM is indispensable.

    Amen! AUM has completely shaped the way I do music on iOS. Brilliant app with constant updates. It just gets better and better, yet we have never even had to pay for an upgrade. Big thanks @j_liljedahl

  • wimwim
    edited July 2022

    @cuscolima said:

    @tja said:

    @cuscolima said:

    @cuscolima said:

    @tja said:

    @cuscolima said:

    @wim said:

    @cuscolima said:
    IAP is, in my opinion, the best pricing strategy, at least for the end user. You pay once for what you really want. The "a la Loopy" strategy is probably more fair for the dev in term of incomes and planification but it can be very frustrating for the user. An exemple : I am still waiting for Beatsurfing's AU promised compatibility but so far, nothing can prove it will ever happen, even if you pay (in the future) for the upgrade subscription...

    I think you've misunderstood Loopy Pro's model. You don't have to pay forward for updates that you may never see, or not see for some time. You can hold off paying after the 12 months. You'll still have the app as-is but you won't get further feature updates, only bug-fixes. When/If you feel like the newer features are worth it, you can pay the 12 month upgrade, and you'll get every update that has happened and that will happen for the next 12 months.

    Thanks wim, I understand now. Let see how this model will evolve in the time.

    [edit] All this has been discussed in many ways in other threads but I want to mention one big disadvantage of the Loopy model. This is a pure marketing principle : if you want to sell big, then you need a killer-feature. It means that a dev can decide to wait before publishing a new feature because he knows that this is the one that will convince the customers to buy the next 12 months. IAP is better as it can be immediately made available for purchase.

    No.

    The WorkingCopy / Wotja / Loopy Pro model is the best thing possible, for both customers and developers.

    This is totally apparent as soon as you understand the model.

    But right, I often see that people misunderstand something in this.

    Just saying.

    Ok if you say it…no more arguments requested

    I still think that there are some unexpected « side effects » related to this model.

    You get what you pay for, and you can use this for the rest of your live.
    And as bonus, you get even all new features for a year and probably security updates for longer.
    So, what is bad here?

    ONLY when there is - at any time after that first year - a version that finally offers something that you really want, you can opt to buy it. Just like a major new version from any other software, and again this is yours for your live.

    You never loose anything and, but your version will never fully deprecate like other software that has version 2, 3, 4 ... the older version will most likely never updated again for new OS versions or security.
    But the WorkingCopy and Loopy Pro licensing will normally always update your bought version for OS and security, even if you never ever buy a new version again.

    I really cannot see any "side effect" here!

    It is the perfect model for both developers and customers: Customers only buy again, when there are good enough new features, while developers are motivated to deliver them!

    Your thoughts?

    Thanks for your arguments that are perfectly valid. I don’t say that this model is bad. I say I see a risk that key features will be delayed till the next 12 months period purely for marketing reasons. I prefer a dev releasing immediately the key feature as an IAP. Apps like Loopy Pro and AUM have a huge potential for evolution, so I think both model will be ok here. Some other apps are much more limited and in this case, I fear the few key features will be deliberately delayed…that’s my point of view

    I don’t think you quite understand the model yet. There is no fixed 12 month schedule that is the same for everyone. It’s 12 months from the time each customer has bought the app. There’s no way that the developer could game the timing of the system in that way.

Sign In or Register to comment.