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
THANKS FOR THIS!
Edt: And I agree with you as well as regards cross-fade, that would be pretty...
OK... I'll take that as "Consumer Desktop Software Model". Catchy. I get that you don't think this is the dev's problem but for @Michael's business it will be a negative and we could help with his "marketing" of the benefits to the community for this approach.
Ask any Nanostudio 2, Auria Pro, or Beatmaker 3 user if their worried about their DAWs future?
Can you name any current IOS apps using this model with a "future disclosure" at release. This is news and worthy of comment and "framing" since many see it as a greedy model because they left the desktop due to many issues around pricing. I know I appreciated the years of low cost apps and many updates without paying anything more. But it's obviously not sustainable based upon many app vendors that have closed up shop.
Who wants to buy fewer, better quality apps for the same yearly spend? I'm starting to question if I need another FX app or another DAW or some type of new sequencer. At $5-10 a pop it's often something to distract myself. Above $10... I get really cautious about my needs and this impulse has trained developers to generally target <$10 pricing to get the numbers up in the hopes we create more demand for the app.
Threads like "NuWidget Crashes an AUv3" rather than just posting a comment in the "NuWidget Thread" or better yet... emailing the support for clues. I do appreciate that sometimes the forum can supply some really good advice but a thread per user issue is excessively bad for the dev's business.
I think I kind of see the confusion here. Say it gets to month 12. Paying for 12 months of upgrades right then would be an act of faith in what's to come, unlike a desktop app where the features are already there.
However, in reality, you don't have to pay for the upgrade at month 12. You'll stop getting new features until you pay. At some point, when you feel its worth it, you pull the trigger. Now you get all the updates + updates for the next 12 months.
It's a bit weird since let's say I wait until month 18 to pay. I get the updates from the last 6 months + 12 more months of updates. Or, lets say I skip a year. I still get all the previous updates + the next year of updates. So by sitting out that year I'm getting a 50% discount.
Strange, but about the best that can be done within the App Store limitations, I think.
(Of course I could be completely wrong about how it works. This is what I thought I understood from earlier dialog with @Michael.)
@gregsmith
Very impressive work there (if also somewhat intimidating
@all
If you recognize this app to be a serious addition to the IOS world and our aural weaponary within it: GO REVIEW! It's the right thing to do, can take you just a few seconds, and is even good game theory to ensure that the app gets the kind of support it deserves moving forward.
@michael
Here's a a long speech about what to do as regard negative energy spat ignorantly from uninformed people: Fuck em.
Personally, I like "Train Release"... you buy a ticket and can ride that train indefinitely.
The Train is maintained with bug fixes.
But the developer intends to Create an improved "Train" with new features like a "Video Game" car, or a "Rock Climbing Wall" for example and you have the option of buying a ticket to the new venue/destination.
Cubasis effectively did this with the Cubasis 2 (train) to Cubasis 3 play... Cubasis 3 got hit with so many complaints about Cubasis 2 to 3 issues and that is a significant issue with the Train Release...
Traditional software teams manage this expectation with "dot" releases (bug fixes) and Integer releases with each integer representing a "Train" with massive new feature changes.
Forward and backward compatibility is often negotiated... usually downwards to the user have to live with the issues or ride the old train.
Apple forces new trains on users, developers and partners... it must be nice to the King
if you can get the job.
Well said 😆
Yes, this is my understanding as well. Instead of creating incentive to update you are better off waiting out. Definitely more pressure on dev, yet no frequent revenue.
Saving money isn't the only incentive out there though. Many people, will be incentivized to pay earlier and more frequently out of good will or in the recognition that paying forward and more frequently helps sustain development.
It may seem like everyone is only out for their own self-interest these days, but I like to think that's further from the truth than people realize.
Yes, I am cynical... sorry, don’t mean to sh!t on this parade, just another POV. We certainly experience very different realities. In mine betting on good will rarely ends well, I do hope you’re right though.
I don't blame anyone for feeling that way. Either way, the reality is, the App Store doesn't provide a better framework that I can think of. It's either the "S" word, or coming out with a completely new app every 12 months and having people pissed about that, or something like this.
Apparently it's been working well for the other company Michael talked with that has been doing it this way. So there's hope.
I would just pay again when I see new features have been implemented that I want (that people on the forum are raving about etc), get them instantly, and then wow 12 months of free, potentially mystery but still free, updates on top of having just bought what I wanted.
I do this Pay yearly model with Bitwig and i personally love it. It’s been great over the last 2 years.
Really glad more devs are adopting this approach.
Totally reasonable, pretty sure many will do the same understandably... but if you think about it that’s a ‘gain’ on the user side and ‘loss’ on the dev side, at least in terms of who’s in ‘control’
Feels like we’re moving the goalpost to wrong direction.
Anyway, I hope I can dive in soon too
I imagine it is still a far more empowering gain for a dev than the dominant non subscription model of ‘receive tiny payday once and have to serve cheap ass whiney bitches for years on end’ and/or the dilemmas /complications/nerd rage associated with purging old app versions.
Sowrry, what’s this aboot?
I’m waiting until I have time to enjoy the free trial, but I doubt if I would decide not to buy it.
I’m interested how this pricing model even works. I guess there must be some part of the App Store that knows when it’s supposed to stop getting new updates? Also, then say you don’t update will bug fix updates be a separate thing from feature updates to sort out who gets to apply what updates? It’s a bit confusing, but I’m sure it’s probably been looked over. Having the options to get updates now makes no sense when everyone would be in the only had it for a year category.
Some get upset when after the purchase the app goes on sale
Imagine user A updating every year for 3 years, deciding to skip because it’s been quite for the past half year - M is working on a major feature - meanwhile user B enjoying LP for 11th month... and a week later major update drops
I mean, even if the update cycles would be fixed (instead of individual case for each user) it could help to avoid drama later on, while way easier to manage...
On the other hand, I think the fact that IAPs can now be arranged outside the AppStore may leave more revenue with the dev. Also I expect AppStore to change a lot in the next few years, when cross platform apps take off and desktop type selling methods start to pressure/influence AppStore.
I suspect the "updates" will be managed as IAP's. If you pay for it, you'll get the updates that
are bundled with that IAP. If not, then you continue to get updates that are included with the base package (just bug fixes at some point to follow IOS releases and Apple caused changes).
Drambo sort of did this with the "waves extension" IAP.
Korg's been working me like an ATM for years with Module Pro. They even took away the organ (tho' mine still worked but I couldn't update) and then they gave me a better Organ IAP in exchange. Something to do with a 3rd party contract I think.
@Michael could offer Loop Set IAP's in concert with content creators like
@jakoB_haQ generated for Reason Compact and other apps. Many players would probably love not having to do all that file management that comes with Loop shopping.
@espiegel123 thank you for all the informations.
MIDI works as you said, 5 stars and review written.
Maybe in the future session midi network will be seen as midi port? At least on my iPad it is hidden in LP.
AUM can use network midi port, LoopyPro not (yet).
I think we are waiting for multioutput, and If possible multiinput auv3.
Midi learn and midi control are nice separated, and working Ok!
Yes I love this app. Thank you.
And about usb multichannel out: Is there possibility to allow interfaces for full 24 ouputs (rme xtc octamic).
I know other interfaces are working Ok, it is about some interfaces need „opening all ports”, i mean analog audio outs is always seen by LP, but other (MADI) are not.
AUM BM3 allow to use 24 outs, but Drambo , LP and most other not….
If AUM can I hope LP will also can and Drambo etc.
@Michael
Thank you for the Forum and app!
This is first time when I speak directly to you, what a pleasure!
Can I ask, the most gently as I can, for considering to add possibility to choose vertical or horizontal input (drag) for faders and knobs? Ex-lanation: I like to use horizontal faders with vertical movement, would be nice to have this option.
And would be nice to have „show value” feature on knobs, faders.
edit: i like how we can name faders! Maybe there is hope for value 0-127 on top of each widget?
or in name we could use variable, for example name „fader ” will show something like „fader 010” where 010 is an example value?
Edit2: in edit mode, text size is hard to set with Apple Pencil. With finger it is Ok, but with pencil it is hard to catch settings.
Yep, everything’s hosted in Loopy. I hid all the apps that stack up at the bottom of the screen by toggling the little eye icon on each one. They took up far too much room otherwise.
I left italizer in there as it’s not state saving all its parameters, so needed to tweak a few things each time I open the project.
Here’s the mixer view…
I’ll see if I can find time to make a walkthrough.
In the meantime, here’s a few screenshots of the widget setup. It’s actually incredibly simple, especially if you’ve setup midi in Audiobus before.
Ya totally, I think all the confusion around the business model just means that it is not currently being explained well enough both in the app store description, and in the app. This is totally a solvable problem. I think adding direct examples of how it works / an faq / basically explaining it to a 4 year old to understand, will go a long way to solving this issue. I am confident that if its explained in the right way, people will accept it.
And hopefully also, when people see how many updates are going to be added over the next year (which i'm assuming is michael's plan), people will start to see the value of the model.
Will the twelve month thing be a universal/global period (or 2022-23), or per user? The latter seems almost impossible for Michael to coordinate, especially allowing for bug fixes, even early seems like something that will get administratively worse for him as time goes on… I hope the model works out for him though, fully deserved as this thing is incredible!
I think that’s correct. I’m not sure of the mechanics, but I’m sure it doesn’t require intervention from Michael. Working Copy is the app he modeled this after.
Why not just add Animoog Z as an Audio Unit input, and record a loop while playing it? You do seem to be massively overcomplicating things!