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 StoreLoopy Pro is your all-in-one musical toolkit. Try it for free today.
Comments
Oh nooooo, I missed it again 😭
I feel you, brutha. I was lucky this time.
Check your spam folder also. However I think it might also be said that the emails are not going to everyone but to a subset of the emails on the list based on the date signed up. I got an email and it was several days later that I decided to join.
It won't be long. If you recall Drambo it was months and there was no talk at all about a public beta. So at least this way we get drips of images and videos.
Speaking of which, new video up today about the auto loop detection from @Michael at
Same. 😢
If there was a way to give my access to the beta to someone I would. I have repeatedly failed to grasp how to use it and feel bad for taking up a space. Back to Loopy HD for now.
No more betas for me.
🙏🏽You are not alone😂😂😂
For those of you frustrated or confused by the beta, you can make a significant contribution by asking questions over on the beta and expressing your points of confusion…that will help Michael know where tweaks are needed and what isn’t clear.
@DarkAum3o thank you, I’ve been kicking myself wondering if it’s just me. I love Michael and his apps and this forum and am sure the manual/ videos will make it all clear and a joy to use. I guess our brains all just work differently.
Don't feel bad. I've been looping with some fairly complex hardware loopers for 20 years, and dive fearlessly into esoteric apps like Beatcutter, and I still find Loopy Pro a lot to wrap my head around.
Thanks @espiegel123 but it’s too late now. I read the slack chats and realised that I am completely out of my depth. You guys are doing really well and helping enormously, the last thing progress needs is me asking ‘errr, what do any of these things do?’’ Keep up the good work 👍
IMO (retired developer, btw), those “err how do I make this work?“ questions are pretty key in improving user experience. When beta teams are mostly people that are on the same page with each other and happy, a developer is missing important actionable information about user experience that can be used to improve the software or prepare materials.
Facts 💯
Please give input to make the workflow and user experience better.
I feel exactly the same way and earlier this week posted the same thing - I would like to give up my Beta slot to someone who can make better use of the app.
I have been encouraged to instead do my duty and go on #slack and detail out exactly where I'm getting stuck. I fear, however, that I'm just getting stuck on the basics. For example I know Loopy Pro can be an AUV3 host, but apart from using the stock microphone I can't figure out how to loop in some sound from an AUV3 sound source. Earlier today I had difficulty finding the fiddly little button to add an AUV3 as I always press the wrong thing (I think it is the pencil) first. Then once you get there, how do you add it to a track/circle? Probably something super simple and just watching someone do it I'll probably kick myself for not realizing it by myself.
This evening I plan to just sit with it and play around to see what I can do. It isn't immediately intuitive like Loopy HD was. But that could be biased by the time I got Loopy HD I think I'd watched a video and that was enough to get me started. If I'd been a beta tester for Loopy HD maybe I'd be similarly stuck!
I can get you sussed out with all that -- but please ask on the Slack channel rather than here. I think a little bit of info will have you up and running quickly. In the AUv3, getting audio sources into Loopy is the same as getting audio sources into any effect. If you are trying to route multiple audio sources to loopy, send all those sources to a bus send in AUM and send that bus into Loopy.
Loopy should be in the FX slot in AUM!
Just gotta say, loop detection + Ableton Link is awesome. Finally no need to think ahead about tempo. Just play until you have a reasonable groove going, hit record, then hit stop. The loop gets detected and the tempo set. Even running in AUM, if you have Link enabled, the AUM tempo will be set to match.
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!
Ah interesting, that is pretty clever. It’s going to fulfill the crashing broken promise of L7.
Yeah, this is the secret sauce for me with live looping and then building up a tune around a groove. I’ll throw in another exhortation to those struggling with the UX to weigh in with challenges. Before I got on slack i was sending Michael early reports of being completely befuddled. While i don’t expect changes before launch i do believe he’s paying attention to the reports around “i have no idea how to quickly set up an audio source”. Trust me when i say you are not alone in being challenged without a manual or an onboard guide. I’ve slowly come to understand the logic behind the UX but it takes a while and fresh eyes and perspectives are so key to optimizing a new product!
I received the original email, but no further emails when the beta opens up again. Nothing is in spam. I think there are just no alerts for opening up slots further beyond the first announcement that the beta has started. I”m not sure how you were able to wait days later because the beta was filled within what seemed to be less than an hour after it opened as far as it seems.
there was a more recent posting in the forum here for the most recent wave. and that one did not instantly fill up. Michael is working pretty much round the clock...and being a dad...so maybe a mailing slipped through the cracks and posting here seemed sufficient.
Right, well I have alerts for this thread now so even though it’s kind of annoying to see when anyone posts anything at least I’ll see if there are new openings. Otherwise I’ll just have to wait for public release and hopefully they find all the major bugs.
Open the Files menu in the beta and click the "Beta" label. That will open a popup browser window to the Beta page on the Loopy Pro website, which contains a link to the Slack channel.
I’m on board with this as well. Good on you for bringing it up. I deleted it hoping that this would get me out and free up a space, but it doesn’t - I still get updates. I am involved in several other workflows at the moment and I’m afraid that I underestimated the time requirement investment to investigate, understand etc this from the ground up - time that I just don’t have.
I thought it would be a lot more straightforward, but I have been up too many blind alleyways and all the rest of it to keep me engaged and feel enthused to carry on. Yes I want it to do well and succeed - absolutely so.
I can tell you this though - it’s not intuitive. Well not intuitive enough to not require a manual, for me at least. And yes I did note that feedback is sought from everyone without a manual to hand, but I thought I could slip into it and soon start sending the feedback - but not to be.
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. An app of this standing which may well herald a new world of music making should have one in my view either for testers to go through all the functionality and discover what’s working and what’s not etc or for those that purchase the app to get to grips with it in a soon a time as possible.
It has an apparent plethora of capabilities considering the queries that had a reply in the affirmative, which can feel slightly overawing when trying to tiptoe your way through it without a reference to hand. On balance my sense is that it’s just too much logistical work now to unearth feedback that has in all probability been already given.
This is my feedback and it’s given in all sincerity with a hope that it helps along the line.
So yes I’m in the same position as others have mentioned, I would happily give up my slot and wait for the release.
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.
If you want to get out of Testflight testing of an app you can select "Stop Testing" at the bottom of the app page in testflight.
I'm a huge manual fan. In a perfect world I'd prefer every app to have a great one even before release. The reality is manuals take a shitload of time and are almost impossible to produce when features are still in flux. Does anyone really think the developer has been sitting on his hands for hours every day and just can't be bothered to write a manual?
The other day I set about drafting some how-to guides for Loopy Pro with the goal of contributing some unofficial resources to have ready for release date. Just one or two subjects took most of a day. Time I could have been using to help find bugs. A full manual + quick start guides is a huge and distracting effort. (And then only the old techie farts like me will read it. Everyone else will want videos.
)
If anyone is really not sympathetic about there not being a manual at release ... I wonder if they'd prefer the release to be delayed another month or two??
(That's actually a serious question. I would actually prefer it that way but I know I'm a rare exception and I totally understand why it isn't that way.)
It’s a good question. I like your idea about the guides, though. I was wondering if we could crowd source some guidance….