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

1…111213141517»

Comments

  • espiegel123espiegel123

    @ashh said:
    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?

    If someone asks questions on the slack channel they get answered. Do people sometimes disagree about what they would like to see? Sure, and I haven't seen any uncivil behavior in those discussions as people try to explain why they would like things a certain way. Michael sets a good tone

    From what I have seen, people are willing to help each other out.

    And Michael really does listen and really is interested in what total beginners find comfusing or not workable.

    I wouldn't decide in advance that any discussion group will turn into a re-enactment of Lord of The Flies.

  • MichaelMichael

    @DarkAum3o said:

    @Michael said:

    @ashh said:
    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?

    Oh, not at all, I think the spirit of ABF has made its way over there. But yeah, no worries.

    It’s very nice that you encourage „shy“ people to go to slack with their dumbest questions.
    I fell much more confidence now and I’m also happy if it helps.
    Let’s see how it moves forward.
    Beta testing is also a learning process, because it’s not always easy to find the right words to explain the problem.

    Last post from my site here…I try to concentrate to the slack channel!

    🙏🏽🖤🙏🏽🖤🙏🏽

    👍❤️

  • [Deleted User][Deleted User]
    The user and all related content has been deleted.
  • [Deleted User][Deleted User]

    Hi, what about support for 24 outputs like AUM Cubasis BM3 done? Only these apps see all outs on some interfaces. I know Drambo will get update and maybe this will be fixed….
    so if we shaping now app for us, Im asking for this, Please?

  • tahichetahiche
    edited November 2021

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

    I totally get what @Michael is saying, but this is a sort of chase-your-tail situation.

    A) Michael is expecting user input in order to do any sort of manual. It’s a smart move, seeing how and where people are lost will dictate how the manual is focused. Legit.
    B ) Some users are uncomfortable with a blank canvas, feeling totally lost. Also legit.

    Way I see it maybe it’s not fair to force these users into a blank canvas they don’t enjoy. I’m a “noodler” myself, I tend to dive in and read manuals later, I don’t have this problem, but I can see how some people just don’t enjoy it and plain don’t want to go through this.
    So I see 2 options:
    A) Provide a very basic “QuickStart” manual to guide through basic functionality to get started so these users don’t confront a blank canvas. THEN gather their valuable input: “ok, I got my first loop, how do I add effects now?.”
    B ) Its ok if they don’t beta test, no betrayal, they’re just not enjoying the process without a head start. I can see how one might feel “pressured” and think “I’m so lost it’s not worth for it to go to slack and ask ‘how do I start.’ “. (In line with @ashh comment above)

    I’d go for option A as these users’ input would be most valuable prior to release and to do the “proper” manual.

    Personally I would consider novice users the “standard” and set up the staring project accordingly. For example (I already mentioned this in slack) having a “long press” donut master menu to guide the user into FX, editing, copying, whatever…

  • MichaelMichael

    You’re absolutely right of course, @tahiche …

  • MichaelMichael

    With that said I have had some invaluable advice over the last few days from just those people 😄

  • supadomsupadom
    edited November 2021

    Agreed @tahiche

    Although if you’re a novice driver you’ll probably manage to park an articulated lorry it’s just it will take you a wee bit longer to do it.

  • KrupaKrupa
    edited November 2021

    I really need to dig into this more, I got the very basic basics straight away, but as I began to explore further, I started to feel a bit lost and ‘un grounded’ - I started to feel like there were several ways to do things maybe, and I wasn’t sure which was better, or correct, mainly things like adding external effects and instruments… I also have never got deeply into the old versions, so there’s probably a common language between those and this that would help - I’ll have another converted bash at it this week and get involved on slack I think…I’ve submitted a couple of crash reports as and when they’ve occurred I think, at that’s at least some help 🙃

  • [Deleted User][Deleted User]
    The user and all related content has been deleted.
  • JocphoneJocphone

    Enjoying the elegance of looping in the main workflow. Applying Effects seems a bit clunky and putting it in the settings menu now seems a retrograde step, even further from where you might find it.

  • supadomsupadom
    edited November 2021

    @Jocphone said:
    Enjoying the elegance of looping in the main workflow. Applying Effects seems a bit clunky and putting it in the settings menu now seems a retrograde step, even further from where you might find it.

    Perhaps putting an fx send slider and destination in the quick swipe up menu could help?

  • lukesleepwalkerlukesleepwalker

    @Krupa said:
    I really need to dig into this more, I got the very basic basics straight away, but as I began to explore further, I started to feel a bit lost and ‘un grounded’ - I started to feel like there were several ways to do things maybe, and I wasn’t sure which was better, or correct, mainly things like adding external effects and instruments… I also have never got deeply into the old versions, so there’s probably a common language between those and this that would help - I’ll have another converted bash at it this week and get involved on slack I think…I’ve submitted a couple of crash reports as and when they’ve occurred I think, at that’s at least some help 🙃

    I stand by my initial observation that the UX presents a track based view (donuts) but then expects the user to find the different mental models (audio inputs, colors, sub-menus, etc) separately. The big miss, to me, is the pencil in each track, which is an absolute head scratcher to a novice. I don’t have access to analytics but I’m willing to bet that most users try to find the options for audio, fx, etc by diving in to a track through the pencil. If the user could set basic options per track (audio input, fx, etc) and then slowly learn how the colors and groups make things efficient and powerful, I think there would be less flailing. Two cents.

  • tahichetahiche

    @lukesleepwalker said:

    @Krupa said:
    I really need to dig into this more, I got the very basic basics straight away, but as I began to explore further, I started to feel a bit lost and ‘un grounded’ - I started to feel like there were several ways to do things maybe, and I wasn’t sure which was better, or correct, mainly things like adding external effects and instruments… I also have never got deeply into the old versions, so there’s probably a common language between those and this that would help - I’ll have another converted bash at it this week and get involved on slack I think…I’ve submitted a couple of crash reports as and when they’ve occurred I think, at that’s at least some help 🙃

    I stand by my initial observation that the UX presents a track based view (donuts) but then expects the user to find the different mental models (audio inputs, colors, sub-menus, etc) separately. The big miss, to me, is the pencil in each track, which is an absolute head scratcher to a novice. I don’t have access to analytics but I’m willing to bet that most users try to find the options for audio, fx, etc by diving in to a track through the pencil. If the user could set basic options per track (audio input, fx, etc) and then slowly learn how the colors and groups make things efficient and powerful, I think there would be less flailing. Two cents.

    I agree. I too gravitate to donut->fx or donut->edit rather than fx->donut or edit->donut.
    I’m guessing this are the precise kind of things that Michael needs from beta testers. Maybe he is the fx->donut type and it’s just natural so he needs other people to point out the “other” way. Then both workflows could be accommodated.
    Btw: I can’t find the fx anymore after the last update 🤣

  • tahichetahiche

    @supadom said:
    Agreed @tahiche

    Although if you’re a novice driver you’ll probably manage to park an articulated lorry it’s just it will take you a wee bit longer to do it.

    You’re almost as good at memes as you’re at looping! 🤟🙏

  • lukesleepwalkerlukesleepwalker

    @tahiche said:

    @lukesleepwalker said:

    @Krupa said:
    I really need to dig into this more, I got the very basic basics straight away, but as I began to explore further, I started to feel a bit lost and ‘un grounded’ - I started to feel like there were several ways to do things maybe, and I wasn’t sure which was better, or correct, mainly things like adding external effects and instruments… I also have never got deeply into the old versions, so there’s probably a common language between those and this that would help - I’ll have another converted bash at it this week and get involved on slack I think…I’ve submitted a couple of crash reports as and when they’ve occurred I think, at that’s at least some help 🙃

    I stand by my initial observation that the UX presents a track based view (donuts) but then expects the user to find the different mental models (audio inputs, colors, sub-menus, etc) separately. The big miss, to me, is the pencil in each track, which is an absolute head scratcher to a novice. I don’t have access to analytics but I’m willing to bet that most users try to find the options for audio, fx, etc by diving in to a track through the pencil. If the user could set basic options per track (audio input, fx, etc) and then slowly learn how the colors and groups make things efficient and powerful, I think there would be less flailing. Two cents.

    I agree. I too gravitate to donut->fx or donut->edit rather than fx->donut or edit->donut.
    I’m guessing this are the precise kind of things that Michael needs from beta testers. Maybe he is the fx->donut type and it’s just natural so he needs other people to point out the “other” way. Then both workflows could be accommodated.
    Btw: I can’t find the fx anymore after the last update 🤣

    I understand the reason why he went the way he did but I think most musicians think this way. And once you’ve recorded a loop it kinda makes sense to have the waveform front and center, but I think the user could find the right submenu easier from the donut.

  • espiegel123espiegel123

    @lukesleepwalker said:

    @tahiche said:

    @lukesleepwalker said:

    @Krupa said:
    I really need to dig into this more, I got the very basic basics straight away, but as I began to explore further, I started to feel a bit lost and ‘un grounded’ - I started to feel like there were several ways to do things maybe, and I wasn’t sure which was better, or correct, mainly things like adding external effects and instruments… I also have never got deeply into the old versions, so there’s probably a common language between those and this that would help - I’ll have another converted bash at it this week and get involved on slack I think…I’ve submitted a couple of crash reports as and when they’ve occurred I think, at that’s at least some help 🙃

    I stand by my initial observation that the UX presents a track based view (donuts) but then expects the user to find the different mental models (audio inputs, colors, sub-menus, etc) separately. The big miss, to me, is the pencil in each track, which is an absolute head scratcher to a novice. I don’t have access to analytics but I’m willing to bet that most users try to find the options for audio, fx, etc by diving in to a track through the pencil. If the user could set basic options per track (audio input, fx, etc) and then slowly learn how the colors and groups make things efficient and powerful, I think there would be less flailing. Two cents.

    I agree. I too gravitate to donut->fx or donut->edit rather than fx->donut or edit->donut.
    I’m guessing this are the precise kind of things that Michael needs from beta testers. Maybe he is the fx->donut type and it’s just natural so he needs other people to point out the “other” way. Then both workflows could be accommodated.
    Btw: I can’t find the fx anymore after the last update 🤣

    I understand the reason why he went the way he did but I think most musicians think this way. And once you’ve recorded a loop it kinda makes sense to have the waveform front and center, but I think the user could find the right submenu easier from the donut.

    Can conversations about the state of the beta and likes and dislikes about it maybe happen on the Slack channel set up for it or the Loopy Beta forum that got set up for it rather than here? There is a lot of design tweaking going on and discussion of it on the beta forum.

    We should all of us be careful about extrapolating from our personal preferences to "most musicians". I spent a lot of years working on an app largely used by professional musicians and sound designers -- there is a lot less unanimity of preference than you would imagine. The various preferences are all legit -- but you would be surprised at how much disagreement there is even among groups like professional sound designers about what is intuitive.

  • celtic_elkceltic_elk
    edited November 2021

    @espiegel123 said:
    We should all of us be careful about extrapolating from our personal preferences to "most musicians". I spent a lot of years working on an app largely used by professional musicians and sound designers -- there is a lot less unanimity of preference than you would imagine. The various preferences are all legit -- but you would be surprised at how much disagreement there is even among groups like professional sound designers about what is intuitive.

    I’m running smack into this in my participation in the beta so far. The discussion of features is very advanced on topics that I consider extremely arcane, while features that I consider utterly basic - stuff I could get on guitar pedals 20 years ago, or that appear in the looper modules that multi-effects hardware manufacturers include seemingly out of obligation, like reverse loop playback - are not only absent, but their absence goes entirely unremarked-upon.

  • espiegel123espiegel123

    @celtic_elk said:

    @espiegel123 said:
    We should all of us be careful about extrapolating from our personal preferences to "most musicians". I spent a lot of years working on an app largely used by professional musicians and sound designers -- there is a lot less unanimity of preference than you would imagine. The various preferences are all legit -- but you would be surprised at how much disagreement there is even among groups like professional sound designers about what is intuitive.

    I’m running smack into this in my participation in the beta so far. The discussion of features is very advanced on topics that I consider extremely arcane, while features that I consider utterly basic - stuff I could get on guitar pedals 20 years ago, or that appear in the looper modules that multi-effects hardware manufacturers include seemingly out of obligation, like reverse loop playback - are not only absent, but their absence goes entirely unremarked-upon.

    So remark on it there. Michael pays attention to everything that comes up whether it gets remarked on or not. Keep in mind that there is more stuff that he'd like to do than there is time to implement so he has to triage. There are certainly things that he'd love to have in there now that won't happen till after 1.0.

  • celtic_elkceltic_elk

    @espiegel123 said:

    @celtic_elk said:

    @espiegel123 said:
    We should all of us be careful about extrapolating from our personal preferences to "most musicians". I spent a lot of years working on an app largely used by professional musicians and sound designers -- there is a lot less unanimity of preference than you would imagine. The various preferences are all legit -- but you would be surprised at how much disagreement there is even among groups like professional sound designers about what is intuitive.

    I’m running smack into this in my participation in the beta so far. The discussion of features is very advanced on topics that I consider extremely arcane, while features that I consider utterly basic - stuff I could get on guitar pedals 20 years ago, or that appear in the looper modules that multi-effects hardware manufacturers include seemingly out of obligation, like reverse loop playback - are not only absent, but their absence goes entirely unremarked-upon.

    So remark on it there. Michael pays attention to everything that comes up whether it gets remarked on or not. Keep in mind that there is more stuff that he'd like to do than there is time to implement so he has to triage. There are certainly things that he'd love to have in there now that won't happen till after 1.0.

    They’re already on the post-1.0 list. I’m simply making an observation in support of your point about differences of opinion.

  • espiegel123espiegel123

    @celtic_elk said:

    @espiegel123 said:

    @celtic_elk said:

    @espiegel123 said:
    We should all of us be careful about extrapolating from our personal preferences to "most musicians". I spent a lot of years working on an app largely used by professional musicians and sound designers -- there is a lot less unanimity of preference than you would imagine. The various preferences are all legit -- but you would be surprised at how much disagreement there is even among groups like professional sound designers about what is intuitive.

    I’m running smack into this in my participation in the beta so far. The discussion of features is very advanced on topics that I consider extremely arcane, while features that I consider utterly basic - stuff I could get on guitar pedals 20 years ago, or that appear in the looper modules that multi-effects hardware manufacturers include seemingly out of obligation, like reverse loop playback - are not only absent, but their absence goes entirely unremarked-upon.

    So remark on it there. Michael pays attention to everything that comes up whether it gets remarked on or not. Keep in mind that there is more stuff that he'd like to do than there is time to implement so he has to triage. There are certainly things that he'd love to have in there now that won't happen till after 1.0.

    They’re already on the post-1.0 list. I’m simply making an observation in support of your point about differences of opinion.

    Gotcha

  • JocphoneJocphone

    @supadom said:

    @Jocphone said:
    Enjoying the elegance of looping in the main workflow. Applying Effects seems a bit clunky and putting it in the settings menu now seems a retrograde step, even further from where you might find it.

    Perhaps putting an fx send slider and destination in the quick swipe up menu could help?

    Possibly, but it might take some more thought to come up with a concept that is as well thought out as the main UI. Doesn’t have to be fixed for version 1, the effects section works but could be made nicer for a followup.

  • Fantomas86Fantomas86
    edited November 2021

    Sooo… any chance I can get into testing this baby? I’m uncontrollably excited and I usually create the most unique situations so rare things might come up thanks to my sophisticated taste of methods and attention to detail :) or at least to Slack… I’d really wanna see how it evolves day by day 😇

  • sigma79sigma79

    Think I declined beta but need a looper for launchpad beats and turntable.

  • cuscolimacuscolima

    Is it possible to freeze/unfreeze loops?

  • telechargetelecharge

    Happy Anniversary, @Michael! 🎂

  • MichaelMichael

    Wow

  • BenBen

    Wow is right.
    I remember watching this video and thinking: can’t wait to see where this goes.
    We shall soon see.
    Feel kind of fortunate to have been around for it.

Sign In or Register to comment.