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, not at all, I think the spirit of ABF has made its way over there. But yeah, no worries.
Thank you. You are always so generous with help.
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!
🙏🏽🖤🙏🏽🖤🙏🏽
I don’t think anyone has even mildly indicated in any way that they might think that ‘the developer has been sitting on his hands for hours every day and just can't be bothered to write a manual?’ @wim - so I’m confused as to why you would ask the question in this way?
To me - and I have mentioned this about previous apps and as you were also mentioning - my preference would to have a manual available for release. To me it just makes more sense for multiple reasons. Those that want it can get going with the app much quicker and those that have more time in the day or just like exploring and discovering can learn it for themselves.
There would be generally just less frustration and less binning of apps. It all goes towards the reputation of the app and for me, not having a manual will only increase the chances of directing it towards the negative.
In fact I think a manual should be a standard feature. I don’t think that there should be a disassociation. Every app with any functionality should have one. People pay money for apps - they want to know how to use it, it’s should be a given. I don’t really like giving out my money then being left to get on with it. Sometimes it feels a bit like a slap in the face, it’s just good customer care in my book.
So I think that developers should be factoring in the manual development to the time of the actual app development.
What I was meaning in my earlier post was - if an app takes years to develop a) it’s likely going to be at least mildly complex in use, and b) what % of the actual total production time would writing a manual for it take?
You really reckon it would take between a month and two months to write an instruction manual @wim? I can’t imagine how. I’m sure I could knock one up for pretty much all the apps I have in a good bit less than a week. (I don’t mean all of them, I mean any one of them 😀)
It’s true!!! ❤️❤️
As soon as I posted my moaner post I got an immediate response which startled me a bit and I was like I need a few hours to think about it!! But in the end we had a good exchange and managed to boil things down which indeed resulted in changes within hours.
It took a couple of days to fine tune that small swipe up loop pop up menu as others weighed in with their opinions but as of today it is ready and fully functional and really nice to use.
Guys, this is your chance to help shaping the app that you’ve been waiting for for so long. Don’t miss the opportunity!
I can't wait for the official release, is all I want to say.
Ideally a manual & tutorial should be included on release , but at the very least a list of any built in GESTURES should be included.
It is so frustrating trying a understand a new app & having unexpected things happening depending on how you inadvertently touch the screen, especially if screen area unlabelled .
Music software should not feel like touch & point puzzle games .
As Michael said, there will be a manual on release.
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.
👍❤️
Please send me beta invite! If it is what I think it is I can get rid of a lot of hardware and therefore save the planet!
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?
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…
You’re absolutely right of course, @tahiche …
With that said I have had some invaluable advice over the last few days from just those people 😄
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.
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 🙃
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?
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 🤣
You’re almost as good at memes as you’re at looping! 🤟🙏
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.
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
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.