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.

Loopy Pro: Limited public beta now open

11213141618

Comments

  • @lukesleepwalker said:
    It’s a good question. I like your idea about the guides, though. I was wondering if we could crowd source some guidance….

    Yes!! That!! :D

    I will have a manual done by release; I'm a reasonably fast writer, but as has been very well put – now's not the time. But wow, some third-party how-to videos would help enormously (and probably attract some views too, no doubt, haha..)

  • @wim said:
    To those totally lost that are bailing on the beta ... I second the hearty request that you jump in on Slack with the most basic questions possible! It might feel embarrassing, but that's actually the most vitally needed feedback there is right now!

    The bugs are gonna show up and get fixed. That's actually the easy part compared to figuring out how to ease the learning curve on release.

    Loopy Pro can be dead simple to get started with, but there's so much power and capability that the simple ways to use it can be obscured. A bunch of geeks trying out every advanced feature aren't going to be as effective at figuring out how to have a successful beginner experience. Bring them there "dumb" questions! Please!

    Send me a beta invite then. I promise to ask the dumbest questions possible. And to most likely not understand the answers either.

  • wimwim
    edited November 2021

    @Michael said:

    @lukesleepwalker said:
    It’s a good question. I like your idea about the guides, though. I was wondering if we could crowd source some guidance….

    Yes!! That!! :D

    I will have a manual done by release; I'm a reasonably fast writer, but as has been very well put – now's not the time. But wow, some third-party how-to videos would help enormously (and probably attract some views too, no doubt, haha..)

    Wow, good to hear about the manual. In one of your videos in Slack you mentioned that there wouldn't be one before release. If you can pull it off, that will be fantastic.

    As far as crowd sourcing, maybe a namespace for the purpose on the AB wiki? Though it it might be better in a place that's less visible before release. I suck at vids, but am up for writing.

  • @wim said:

    @Michael said:

    @lukesleepwalker said:
    It’s a good question. I like your idea about the guides, though. I was wondering if we could crowd source some guidance….

    Yes!! That!! :D

    I will have a manual done by release; I'm a reasonably fast writer, but as has been very well put – now's not the time. But wow, some third-party how-to videos would help enormously (and probably attract some views too, no doubt, haha..)

    Wow, good to hear about the manual. In one of your videos in Slack you mentioned that there wouldn't be one before release. If you can pull it off, that will be fantastic.

    As far as crowd sourcing, maybe a namespace for the purpose on the AB wiki? though it it might be better in a place that's less visible before release.

    On my to-do list is to set up a hidden namespace on the Audiobus wiki to start this.

  • @espiegel123 said:

    @wim said:

    @Michael said:

    @lukesleepwalker said:
    It’s a good question. I like your idea about the guides, though. I was wondering if we could crowd source some guidance….

    Yes!! That!! :D

    I will have a manual done by release; I'm a reasonably fast writer, but as has been very well put – now's not the time. But wow, some third-party how-to videos would help enormously (and probably attract some views too, no doubt, haha..)

    Wow, good to hear about the manual. In one of your videos in Slack you mentioned that there wouldn't be one before release. If you can pull it off, that will be fantastic.

    As far as crowd sourcing, maybe a namespace for the purpose on the AB wiki? though it it might be better in a place that's less visible before release.

    On my to-do list is to set up a hidden namespace on the Audiobus wiki to start this.

    Perfect. I've been dumping some stuff into Obsidian, but would prefer to write in-place where it will eventually be available.

  • @rud, @DarkAum3o, @fprintf any others who are deciding to bail – your perspectives are just what I need! Fleksi weighted in the other day only reluctantly with some problems he was having, and it was enormously useful and resulted in some immediate changes. That's exactly what I need.

    Here's the thing: I can't see this stuff myself any more; I've been working on this damn thing for seven years, and for the most part I can't see it any more. That's why I need people of all different sorts to give it a try and tell me what's hard.

    Just bailing without telling me anything feels like a real betrayal to me, to be honest, because it's exactly that perspective which will help. So please, just bloody get in touch and tell me what you think! I'm literally working every waking second right now, and don't a great amount of time to go searching for comments in places like this thread; if you can't be assed getting on the Slack, then just email me.

    And thank you.

  • @Michael I downloaded it and had no real idea where to start. Too much of a blank slate for me to do without help

  • wimwim
    edited November 2021

    @audiobussy said:
    @Michael I downloaded it and had no real idea where to start. Too much of a blank slate for me to do without help

    Good start, but it's more helpful if you think of questions to ask rather than to just say you're stuck. You don't go to the doctor and simply say you don't feel well and expect them to know how to help you. Maybe start with the first question that comes to your mind (and don't just say "how do I start"? 😉).

    Asking those questions on the Slack channel is much better than on this thread. But, if here is what it takes to get people to do it, I say "bring it". (apologies in advance to those who disagree)

  • Yeah, I'll start reading this thread as part of my routine; it's an extra time-sink but I'm willing to do it if it'll bear fruit.

  • @wim said:

    @audiobussy said:
    @Michael I downloaded it and had no real idea where to start. Too much of a blank slate for me to do without help

    Good start, but it's more helpful if you think of questions to ask rather than to just say you're stuck. You don't go to the doctor and simply say you don't feel well and expect them to know how to help you. Maybe start with the first question that comes to your mind (and don't just say "how do I start"? 😉).

    Asking those questions on the Slack channel is much better than on this thread. But, if here is what it takes to get people to do it, I say "bring it". (apologies in advance to those who disagree)

    Many apps start you off with something fiddlable. Or a guided tutorial. This seems it may be too much of a blank slate.

  • @audiobussy said:

    @wim said:

    @audiobussy said:
    @Michael I downloaded it and had no real idea where to start. Too much of a blank slate for me to do without help

    Good start, but it's more helpful if you think of questions to ask rather than to just say you're stuck. You don't go to the doctor and simply say you don't feel well and expect them to know how to help you. Maybe start with the first question that comes to your mind (and don't just say "how do I start"? 😉).

    Asking those questions on the Slack channel is much better than on this thread. But, if here is what it takes to get people to do it, I say "bring it". (apologies in advance to those who disagree)

    Many apps start you off with something fiddlable. Or a guided tutorial. This seems it may be too much of a blank slate.

    Okay, fair enough. It will have those things, but it's still in development, so those final touches just aren't there yet.

  • Hey @Michael, my apologies. I had no intention of betrayal. I ventured into the slack and saw conversations that were way over my level. With being on the later release of the beta I felt like the moment when Walter berates Donny in The Big Lebowski, describes him as a child who walks in halfway through a conversation and so on. I also felt a bit Wayne’s World doing the whole ‘we’re not worthy’ routine.
    And so I retreated to your wonderful forum and left the adults to their business.
    @wim, for whom I have total respect for his knowledgeable answers and valuable contributions, put forward the very reasonable suggestion of asking questions rather than simply stating ‘I’m stuck’. I would like to be able to do that but at this moment I have found the startup process to be quite confuddling and find myself asking ‘what do I do?’
    From now on I’ll use the slack as I can now see other perspectives on the matter. I genuinely believed I had nothing to offer to the cause, yet now I understand that the experience of those who may lack app-related intuition is still relevant.
    It’s past my bedtime but I will have another crack at it tomorrow. Long live the forum and those who bail in her 😬

  • fwiw, I'm trying to write a few "blank slate" quick start guides. Hopefully they won't be needed by the time the app comes out but they're helping me to break things down into small chunks for my own understanding and testing purposes. I just wrote one for recording one's first auto-detected loop with automatic tempo setting for AUM. It really isn't hard to get going when you see it laid out in steps.

    I'm confident that all important "what do I do now??" question will be a lot less intimidating than it is now before release. B)

  • @audiobussy said:
    @Michael I downloaded it and had no real idea where to start. Too much of a blank slate for me to do without help

    Come on over to the slack channel. I bet with a few questions answered we can get you on track.

  • @rud said:
    Hey @Michael, my apologies. I had no intention of betrayal. I ventured into the slack and saw conversations that were way over my level. With being on the later release of the beta I felt like the moment when Walter berates Donny in The Big Lebowski, describes him as a child who walks in halfway through a conversation and so on. I also felt a bit Wayne’s World doing the whole ‘we’re not worthy’ routine.
    And so I retreated to your wonderful forum and left the adults to their business.
    @wim, for whom I have total respect for his knowledgeable answers and valuable contributions, put forward the very reasonable suggestion of asking questions rather than simply stating ‘I’m stuck’. I would like to be able to do that but at this moment I have found the startup process to be quite confuddling and find myself asking ‘what do I do?’
    From now on I’ll use the slack as I can now see other perspectives on the matter. I genuinely believed I had nothing to offer to the cause, yet now I understand that the experience of those who may lack app-related intuition is still relevant.
    It’s past my bedtime but I will have another crack at it tomorrow. Long live the forum and those who bail in her 😬

    No worries at all 😁 I get it! And perhaps there'll be some for whom a blank slate holds only blank bafflement; I'm keenly aware that an onboarding process is necessary, as well as a full written manual, and I'll get there prior to release. Even this conversation is helpful though; the addition your voice can only be a good thing.

  • Damn, late to the party again.

    Would love to give it a spin as I tend to have a knack for breaking apps/finding bugs.

  • Can someone explain/show what the support for Launchpad includes? Or direct me to where it maybe is already explained or shown...? Sorry if I’ve missed it, the thread is steadily growing...

    Mostly I want to know if it’s worth getting a Launchpad or if i could get this controller, which also has knobs, to pretty much do the same thing with the help of Mozaic or some other magic... (https://www.amazon.com/gp/product/B00WU6FDNG/ref=ox_sc_act_title_2?smid=ATVPDKIKX0DER&psc=10)

  • @ManWhoWouldBeStrings said:
    Can someone explain/show what the support for Launchpad includes? Or direct me to where it maybe is already explained or shown...? Sorry if I’ve missed it, the thread is steadily growing...

    Mostly I want to know if it’s worth getting a Launchpad or if i could get this controller, which also has knobs, to pretty much do the same thing with the help of Mozaic or some other magic... (https://www.amazon.com/gp/product/B00WU6FDNG/ref=ox_sc_act_title_2?smid=ATVPDKIKX0DER&psc=10)

    Too soon. Launchpad support capabilities are still in flux.

    I wouldn't expect to get anywhere near the level of integration using Mozaic or anything other than inbuilt integration though, not without way more trouble than any cost difference would justify, and maybe not at all.

  • @wim said:

    @ManWhoWouldBeStrings said:
    Can someone explain/show what the support for Launchpad includes? Or direct me to where it maybe is already explained or shown...? Sorry if I’ve missed it, the thread is steadily growing...

    Mostly I want to know if it’s worth getting a Launchpad or if i could get this controller, which also has knobs, to pretty much do the same thing with the help of Mozaic or some other magic... (https://www.amazon.com/gp/product/B00WU6FDNG/ref=ox_sc_act_title_2?smid=ATVPDKIKX0DER&psc=10)

    Too soon. Launchpad support capabilities are still in flux.

    I wouldn't expect to get anywhere near the level of integration using Mozaic or anything other than inbuilt integration though, not without way more trouble than any cost difference would justify, and maybe not at all.

    It’s more the fact that this other controller i posted a link for has knobs rather than a cost difference, which really is negligible when I’ve seen used Launchpads for about $20 more...

    I know things are early, the reason I’m asking is because I’m in the U.S. now where these things seem to be cheaper but leaving soon and was hoping to get some idea of what’s coming so I can decide if it’s worth getting one while I’m here...

  • wimwim
    edited November 2021

    All I can say is the level of Launchpad integration that Loopy Pro will have would be extremely difficult to achieve with another controller and scripting such as Mozaic. It depends in your priorities.

    Fwiw, I don’t care about the LP integration for my purposes. I’d be just as likely to prefer that other controller myself.

  • Fingers crossed for LP black Friday deals it is then.

  • edited November 2021

    OK I'll start with a specific request.

    For context I just sat down to play with the beta for the first time an hour ago, and am as confused as others seem to be about how to actually get started.

    • My first time trying to use a looper of any sort - I get the concept of what they do, but clearly there's some assumed knowledge of a looper's user interface that I don't have
    • I can generally work my way through music apps on iOS without too much difficulty, but Loopy Pro has me stumped as soon as I start it
    • I'm a coder in my day job, and have no trouble writing Mozaic code to do pretty much anything that occurs to me

    Could someone please explain (or record a short video, or whatever) how to use Loopy Pro in AUM? Just the barest essentials - setting up a MIDI synth to send to Loopy Pro, then record a loop, then play it back, all inside AUM. I think once I've seen that, a lot will become clearer.

  • @espiegel123 said:

    @robosardine said:
    …. I think @Michael recently said there was no time to write a manual? I can’t understand this as it’s been so long already. It needs and should have a manual ready to go

    The scale of this project is immense. With an immense project whose feature set and workflow is not frozen (which can’t happen till there has been usability testing and tweaking), you can’t write the manual or create tutorials till the software is frozen. Michael works extremely hard and the scale of the undertaking enormous and he is putting in tons of time to make software right. This has involved a lot of (wise) re-thinking of how certain things are done in response to feedback from people testing,

    There are only so many hours in a day.

    It is entirely understandable that there isn’t a manual yet.

    I'm sure you could do it.

  • @wim said:
    All I can say is the level of Launchpad integration that Loopy Pro will have would be extremely difficult to achieve with another controller and scripting such as Mozaic. It depends in your priorities.

    Fwiw, I don’t care about the LP integration for my purposes. I’d be just as likely to prefer that other controller myself.

    But if you can say that...there must be some more specific idea of WHAT is being integrated out there no? Not meaning to harass, just curious as TestFlight has said Launchpad is starting to be included with the last few builds but i don’t have one yet to try anything out

  • @ManWhoWouldBeStrings said:

    @wim said:
    All I can say is the level of Launchpad integration that Loopy Pro will have would be extremely difficult to achieve with another controller and scripting such as Mozaic. It depends in your priorities.

    Fwiw, I don’t care about the LP integration for my purposes. I’d be just as likely to prefer that other controller myself.

    But if you can say that...there must be some more specific idea of WHAT is being integrated out there no? Not meaning to harass, just curious as TestFlight has said Launchpad is starting to be included with the last few builds but i don’t have one yet to try anything out

    Would you be buying one solely for Loopy Pro? I'm thinking that even if you do and that function does not materialise then you can definitely use it for a lot of other apps.

    That said, I bought a Pro last year and have just sold it.

  • @ashh said:

    @ManWhoWouldBeStrings said:

    @wim said:
    All I can say is the level of Launchpad integration that Loopy Pro will have would be extremely difficult to achieve with another controller and scripting such as Mozaic. It depends in your priorities.

    Fwiw, I don’t care about the LP integration for my purposes. I’d be just as likely to prefer that other controller myself.

    But if you can say that...there must be some more specific idea of WHAT is being integrated out there no? Not meaning to harass, just curious as TestFlight has said Launchpad is starting to be included with the last few builds but i don’t have one yet to try anything out

    Would you be buying one solely for Loopy Pro? I'm thinking that even if you do and that function does not materialise then you can definitely use it for a lot of other apps.

    That said, I bought a Pro last year and have just sold it.

    Yeah, I want to get a new controller with more pads than my current keyboard has, but would also like some knobs, which the Novation Launchpad does not have, so i was thinking to get a different one, like the one i linked to above, but as my purposes are primarily for Loopy Pro I was hoping for some input on what I might miss out on if I go that route. Knobs or Loopy Pro native support integration...that is the question? I guess...

  • @ManWhoWouldBeStrings said:

    @ashh said:

    @ManWhoWouldBeStrings said:

    @wim said:
    All I can say is the level of Launchpad integration that Loopy Pro will have would be extremely difficult to achieve with another controller and scripting such as Mozaic. It depends in your priorities.

    Fwiw, I don’t care about the LP integration for my purposes. I’d be just as likely to prefer that other controller myself.

    But if you can say that...there must be some more specific idea of WHAT is being integrated out there no? Not meaning to harass, just curious as TestFlight has said Launchpad is starting to be included with the last few builds but i don’t have one yet to try anything out

    Would you be buying one solely for Loopy Pro? I'm thinking that even if you do and that function does not materialise then you can definitely use it for a lot of other apps.

    That said, I bought a Pro last year and have just sold it.

    Yeah, I want to get a new controller with more pads than my current keyboard has, but would also like some knobs, which the Novation Launchpad does not have, so i was thinking to get a different one, like the one i linked to above, but as my purposes are primarily for Loopy Pro I was hoping for some input on what I might miss out on if I go that route. Knobs or Loopy Pro native support integration...that is the question? I guess...

    Well, you could get a Launchpad and a Launch Control?

  • edited November 2021

    I don’t have Launchpad so I could be wrong, but I f you think of LP as an audio clip recorder / player, (like Ableton scene view) Launchpad support makes a lot of sense. On top of that it is probably useful as a keyboard, sequencer, controller.
    The main difference between support vs integration will be the 2way communication. While Launchpad will pick up colours and button states automatically, this other controller won’t. Even though it looks similar, it would require complete integration to do that, which will likely never come... unrealistic to expect that... for other controllers, there is the generic ‘midi learn’ which is nice, but will always leave you to wish for more.

    Edit:
    We buy controllers for specific or generic reasons... if you want something for Loopy, nothing will come close to its Launchpad integration,probably for long time if ever.

  • @rud said:
    Hey @Michael, my apologies. I had no intention of betrayal. I ventured into the slack and saw conversations that were way over my level. With being on the later release of the beta I felt like the moment when Walter berates Donny in The Big Lebowski, describes him as a child who walks in halfway through a conversation and so on. I also felt a bit Wayne’s World doing the whole ‘we’re not worthy’ routine.
    And so I retreated to your wonderful forum and left the adults to their business.
    @wim, for whom I have total respect for his knowledgeable answers and valuable contributions, put forward the very reasonable suggestion of asking questions rather than simply stating ‘I’m stuck’. I would like to be able to do that but at this moment I have found the startup process to be quite confuddling and find myself asking ‘what do I do?’
    From now on I’ll use the slack as I can now see other perspectives on the matter. I genuinely believed I had nothing to offer to the cause, yet now I understand that the experience of those who may lack app-related intuition is still relevant.
    It’s past my bedtime but I will have another crack at it tomorrow. Long live the forum and those who bail in her 😬

    The slack is definitely quite intimidating, especially with some users posting 10+ threads per day. It’s impossible to keep up with so don’t feel like you need to.

    I would recommend rather than trying to find out what loopy ‘does’, think about what you might want to get out of something like loopy. For instance, I don’t record live instruments at all, but I do love playing with samples, so I’m focusing on importing audio tracks into loopy and remixing them. Just focussing on that one aspect, I’ve been able to contribute a number of bug reports and helped suggest things that just don’t work how you’d expect them to.

    @wim said:

    @espiegel123 said:

    @wim said:

    @Michael said:

    @lukesleepwalker said:
    It’s a good question. I like your idea about the guides, though. I was wondering if we could crowd source some guidance….

    Yes!! That!! :D

    I will have a manual done by release; I'm a reasonably fast writer, but as has been very well put – now's not the time. But wow, some third-party how-to videos would help enormously (and probably attract some views too, no doubt, haha..)

    Wow, good to hear about the manual. In one of your videos in Slack you mentioned that there wouldn't be one before release. If you can pull it off, that will be fantastic.

    As far as crowd sourcing, maybe a namespace for the purpose on the AB wiki? though it it might be better in a place that's less visible before release.

    On my to-do list is to set up a hidden namespace on the Audiobus wiki to start this.

    Perfect. I've been dumping some stuff into Obsidian, but would prefer to write in-place where it will eventually be available.

    I’d definitely be up for contributing to this

  • I think I would find Slack quite intimidating. There will always be power struggles in whatever arena humans are in, Slack will be no different. So to say to someone "hey! It's great that you know nothing! Come and demonstrate that to all the Experts over at the Slack channel!" Well, I get it.

    That said, it's probably your voice that needs to be heard much more than the Experts. It's just a shame that it probably won't be, unless you find a way. That feeling of "my voice is not worthy" is possibly a deep-seated thing so this forum may not be the place where you tackle it. However, you could send Michael your thoughts via some other channel?

Sign In or Register to comment.