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
The current update has taken longer than expected and has involved substantial changes to Loopy Pro’s internal architecture to ensure long-term stability as new capabilities are added. Work has been ongoing. Understand that Loopy is a massively complex project, and 2.0 represents a formidable step forward.
As a result of the nature of the changes, the frequent incremental updates we were doing for a while stopped being feasible. At the point where frequent incremental releases stopped, the software was in a solid state.
There have been a few opportunities to join the beta project and there will likely be on more round for a final round of banging before release.
We appreciate people’s patience as we get the software wrapped up.
Michael has always been very fair about what new enhancements get included for existing purchasers when development has taken longer than expected. I see no reason to think it will be otherwise now.
I’m sorry, you’re not listening, simply repeating yourself. I DO have (some) patience, but it’s not what a was offered when buying a pro-license including a year of ‘free’ updates and upgrades.
Furthermore, I also DO understand that it’s a lot of work, especially for a one-man band.
So, I’m NOT asking to speed things up or release v2 (way) too early nor do I want Michael to offer some kind of a discount (if he even had planned on doing so, he needs to get paid for his hard work).
But, it has been more than 8 months since the last release. And due to the lack of communication (from a one-man band, so I DO understand) I’m simply asking to offer paying customers access to the beta.
Why acting like some sort of a gatekeeper on that one?
The irony is palpable
What update is needed with the current version? I haven’t run into any issues or bugs for a long time. Are you having a different experience?
Beta user…?
What is offered is that when new features are added within a year of purchase, there will be no charge for them. There isn’t a promise of new features being added throughout the year.
I work part-time at A Tasty Pixel. Part of my job is responding to questions about Loopy Pro so that Michael can focus on development.
That’s awesome!
Negative. I use the plain old App Store version. What needs fixing? It’s an honest question, I Loopy Pro quite a bit, and haven’t had any problems with it for a long time.
That’s probably what I should do, too.
In the current version I’m missing one important thing, which contains configuration of the busses / routing.
This, and other requests, are posted and discussed by many pro-version users on the agile-style feedback board.
Some of those requests were granted, and in development ever since (including simple MIDI looping).
Nobody asked for a mayor version, just ‘minor’ updates and improvements. Just like before.
This is where I completely disagree with @espiegel123 ’s (personal) opinion, and almost legal standpoint.
Michael chose to go for a big jump, and also expanding to desktop. So not agile growing and maintaining the product.
That’s where he (already) did let go of his new business strategy. We’re back add a classic development and licensing model.
So maybe I should go with a more classic and simpler looper app, too. Let go of an integrated mixer and control surface.
After all, iOS and iPadOS) once started with the idea of interconnected, smaller apps, not classic desktop monoliths.
Fwiw, desktop version development is on hold until 2.0 is out. It’s not impacting anything.
A reminder that it's easy to mute the trolls instead of feeding them!
I don’t consider that trolling. Just a customer voicing dissatisfaction.
Just like it’s your choice to respond in the first place. And if you want to mute me, fine.
Absolutely not trolling. Been a loyal customer and advocate for Loopy on several forums, especially when he introduced Pro.
And yes, I became disappointed due to this non-Agile approach, and especially due to the lack of communication.
@MaikR wrote
The current non-agile cycle was necessary because some changes required significant architectural changes not originally foreseen. With an app this complex, you sometimes don't realize the implications of early design decisions...and you discover when trying to implement some features that you need to make architectural changes that you can't agile-ly roll in.
I'll beg to differ on the claim "nobody asked for...."
All the changes are responsive to user requests and/or were part of long-term roadmap.
Believe me no one wishes Loopy Pro was finished more than Michael.
This not a new strategy. Everything being done now has been part of the long-term plan. The new version and the future features that the current work will make possible will be of great benefit for a great many people.
It has just taken longer to accomplish than hoped for.
p.s. Implicit in your messages is the notion that there was a promise to have a constant stream of new features rolling in. I don't believe such a promise was ever made. There was a period where that was happening as we rolled in features and tweaks.But there wasn't a promise that it would always proceed like that.
The 12-month upgrade pricing is easy to think of simply as some subjective rate of new features rolling in, but if you really think it through, it's not that. If it was, then it would be quite limiting.
It's a way of providing income to make it possible to further develop product features. Two advanced features could consume the effort of twenty smaller features. The smaller features might make a few people a little happy, but those waiting for the two killer advanced features would still be waiting.
Some high-effort features like midi looping can't be put off just to satisfy people expecting a constant flow of smaller feel-good updates. Some also can't be released piecemeal. Some features end up requiring other big features to accommodate them. For instance, midi looping required a total overhaul of the mixer to accommodate the routing and other aspects. The big stuff that is coming just doesn't fit an Agile model very well.
I get someone feeling like the updates flow they expected from the 12-month re-up is lacking. There's more to it than that though. When the updates do hit, they represent a year of honest, hard effort whether they're two feature additions or twenty. If they take more than 12 months, they represent more than 12 months of work.
You either trust that or you don't. Either way you vote with your wallet. I feel I'm cheating Michael by paying as little as I do personally. ymmv.
As for opening the beta to keep people applying pressure happy? Bad idea. Some people are good beta testers (I suspect @MaikR may be one) but an open public beta can have real downsides when trying to focus on simply getting the product ready to roll out.
I dont want 2.0 to be released until it is good an ready, but I think the whole transition could have been handled better, especially given how customers are billed for Loopy Pro.
It get that the announcement in fall was probably premature and to avoid making the same mistake, no further announcements will be made until it is ready. But look at it from the customers point of view. People who purchased in spring of 2024 saw few, if any, updates. Renewals may have decreased because of the lack of updates so maybe the announcement was made in fall to reassure customers and make it sound like the release was immanent to help retain customers and entice new ones. It feels disingenuous to tell customers that they will receive "feature updates for 12 months to keep" and then stop delivering them for the current version because efforts have been redirected to a new major release.
At this point, I think it is only fair to offer all previous customers an upgrade to 2.0 or extend everyones updates by a year (assuming 2.0 does not come out until spring which will be about a year since the last update), since we had to forgo regular updates while all development has shifted to 2.0. It would also be nice to have the an updated release estimate provided since the previous one has come and gone. I am not talking about an exact date, a vague window like "Summer 2025" would be sufficient. That way new customers can decide if they want to purchase now, knowing that no updates will be made until 2.0 is released, or wait until it is released.
Impatience is understandable.
... but it'll still be ready at exactly the same time it would be if a release date is guesstimated.
@DontShare : I think I've explained in this thread why we aren't giving a timeframe...we thought we were very very close to release...and then found some issues that required some time-consuming rearchitecture...and so we are trying to avoid that misestimation happening again.
best comment EVER!!!
I get it. Im just stating that the whole situation looks shady. There was no hesitation months ago and I have no doubt the announcement generated a bunch of subs, but now lips are zipped. Its been about 3/4 of a year since regular updates are abandoned. Hopefully if/when 2.0 is ever released you do the right thing and either extend everyones subs by the the time since the last update or offer everyone a free upgrade.
It's worth noting that no-one has to renew the 12-month upgrades until they see features already released that are worthwhile to them. When they do renew, they still get all the intervening feature updates, plus the next 12-months.
If anyone doesn't like the uncertainty that they'll be happy with the updates over the next 12 months, then they don't need to "pay forward" for anything next time around.
(Saying that for general info, not as a rebuttal to the previous post.)
I realize now that I upgraded almost a year ago. I did so hoping that midi looping was on the horizon. While I am a little bummed that it has taken longer than I thought it would, I am good with it. The value I have received from this program has been far more than the cost of the program and the upgrade. When I compare it to what I have paid over the years for something like Ableton Live, it is ridiculous. What I can do with this program boggles my mind. And I have paid less than $50. I support the efforts of Michael and all who work at A Tasty Pixel. I can understand the frustrations of those who have expected more. At the same time I want to applaud the work that has gone into the program and I look forward to its next release. I like supporting the people who create the tools that give me so much. I do so out of self interest; their well being will allow them to continue working on this amazing program. And it's also a way to show my gratitude. I'm sure I will upgrade again.
To clarify, the reason for not giving an estimate NOW is precisely because we goofed on the earlier estimate. We are being cognizant that our estimates are subject to error. Learning from a mistake rather than repeating it.
I am not sure why that seems shady to you. If it does, I am sorry.
We are working hard on getting the software done.
I’m not too sure where to ask this but I would like to suggest something towards Michael. When an auv3 is open and then the phone turns to portrait then back to landscape, the sizing of the window turns to a square and not fully stretched out like it was in landscape. The windows do not restore back to how they were before the orientation got flipped. Really messes up the flow. Not sure if it’s meant to do this or if it’s a bug
Thank you ed
This is expected behavior. When you rotate your device, Loopy will re-size an open window to keep the top and bottom on screen. That size becomes the new window size.
It doesn't store different AU window settings for different orientations. It isn't expected that you will be switching back and forth between orientations during a session.
Feel free to request different behavior on the roadmap site https://roadmap.loopypro.com
You get a year of updates if and when there are updates!
No point in updating when there are no serious bugs that need to be fixed or when new features are simply not ready, or?
But I do understand the wish to access the beta 😉
EDIT: And within the last year, there were 24 updates!!!
I can see both sides of this. I completely understand how someone who bought their 12 months early last year expecting MIDI looping to be released within that cycle (and therefore be available to them forever) could be disappointed, considering that the intended release schedule did seem pretty clear at the time. There are extenuating circumstances, however, and the current situation certainly isn't due to a lack of hard work. You should always buy software or hardware (whether outright or on subscription) based on what's available at the time, and not on intended future features that may or may not appear. That is certainly hard to do, though - I'm certainly always thinking about potential updates when I buy something!
It's a tough one, this - I don't think anyone should be entitled to a free year's upgrade, but can also see why they might think they should be. It's not like Loopy Pro stood still in the meantime, though. And also, a big freebie would then impact Michael in terms of having the money to justify developing the app beyond MIDI looping.
So on balance, I'm not in favour of any 'compensation' but appreciate that the situation regarding communications about the MIDI looping update timing wasn't ideal.
The howling misstep was to release a teaser ‘it’s coming really soon’ video via Doug last October. I can fully understand why people who saw that and thought, ‘great, it’ll happen well before my yearly cutoff,’ would be pissed off when it then failed to appear and their year’s cutoff passed by. A sincere apology for that would be due i guess, but not compensation - the model doesn’t promise any specific updates in any specific year. Hopefully a lesson has been learned though - releasing publicity before things really are good to go is tempting fate and asking for trouble.
I bought this last month with the hope of getting the midi update before the yearly cut-off, so fingers crossed
