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
Plugin Delay Compensation, usually expected as an automatic feature to align different audio streams in a DAW.
It‘s not that simple... Avid (Pro Tools) needed more than 10years and it still wasn‘t 100% reliable.
BM's sampler is definitely one part of a bigger whole. I can't make many suggestions for what I think is a reasonable sub-set of features as I'm almost completely unaware of the limitations of AU. But once I own BM, I'd be happy to pay a $5 IAP even if the only thing it offered was the ability to load kits I've designed in the main program, play them on either 16 or 64 pads (I'm guessing it wouldn't be too difficult to add the left-panel velocity, beat-repeat and pad-velocity functionality). This along with being able to leverage expected behaviours of AUv3 (Multiple instances, state-saving etc.) would make a huge difference.
Of course, anything above and beyond that would be a bonus. And I'm pretty sure that there is much more scope to improve upon my suggestions
As to the possibility of complaining? I guess. Perhaps Koala's developer could offer some insight into that, given Koala's AUv3 IAP.
You can change the type of sensitivity for the knobs in the midi focus action for the ones it’s possible for like “Macro control” the different variations are : Pickup, Relative to 64, Relative to 16, Relative to 0. Find out which ones best suit your controller.
As for the the forum I’m tagging the forum Admin maybe he knows wassup. Hey @tk32 not sure why he’s having issues creating an account in the forum.
We don’t really use the forum anymore and you can find many of us in discord here https://discord.gg/ZaVuuVS
Hope this helps.
PDC is a big item on the list. I think almost all of us want this.
Well you might be one of the few ones that feel that way. The reason Serato studio was created is because of what most people wanted from Serato sample.
Hi @Janosax
As forum admin I can see you registered for the Intua forum in Nov 2021, but it appears you never confirmed your email address with the verification email (perhaps it got caught in spam?).
Let me know if you need any help getting authenticated.. or alternatively join our Discord as @hansjbs suggested above.
You may be right that I'm one of a few that feels the way I do, but has Serato published actual data regarding how many of their customers upgraded and prefer using 'Studio' in its entirety?
I also don't see any conflict between their situation in which they now find themselves and what is being proposed for BM. Being able to satisfy both distinct sets of customer demands seems like a double-win.
As I understand it, that's not how it works. It's 12 months from the date you personally purchased it, not a cyclic event based on the same calendar for everyone.
[edit] or maybe I'm misreading what you said. Yes, I wonder how renewals will go starting 12 months out from release date, as people gradually start to hit the 12-month mark. We won't be likely to know how that goes, but I truly hope it goes fabulously.
Point Defence Cannon. Awesome for destroying inbound projectile weapons.
That’s suck a dope controller, I shouldn’t have sold mine. One of the best pads but unfortunately no, the XY pad is for internal usage only, note repeat and things like that which does not sync either. One of the reasons I sold it.
@el_bo, @CapnWillie check this out. Let’s hope waves bring this to iOS and I think people won’t ask for BM3 sampler AUV3 anymore
Considering that Waves and Steinberg have a history together on iOS I would not be surprised if it gets 'embedded' into Cubasis so people will still scream after an AUv3 sampler
(Personally I would be happy if Steinberg would add the Cubase Sampler Track to Cubasis as it would cover most of my sampling needs).
For most of my current sampling needs Drambo and Sunvox cover almost everything I need...
...I cheat a bit with Koala from time to time haha...
Yeah waves needs to do the same thing Fabfilter did. DISCONNECT 😂😂😂
>
Considering it's 'cheap' on the desktop (most likely to 'lure' people into the Waves Eco-System) I doubt we'll see it on iOS...
...but if we do it will most likely be embedded into Cubasis like the other Waves stuff.
Even though I have a love/hate relationship with Cubasis it is still one of the most complete 'DAWs' on iOS/iPadOS.
And since it's pretty 'simple' I have a good grip on how it works and there are no 'hidden surprises' when it comes to features other than that it can dive when I least expect it, but it's been surprisingly stable for the past week or two...
Ironically I have a gut-feeling that the GarageBand sampler will get an update before we get an updated sampler in Cubasis.
Cheers!
I would like BM3s sampler as an auv3.
For me, a BM3 sampler in another host would be an improvement over using it within BM3 because, quite frankly, I dislike BM3s workflow.
Back In the day I had an AKAI ‘S’ sampler, not an MPC. I liked the rack more and using it with a keyboard and sequencer of my choice was better for me.
I appreciate that for a lot of people an MPC>S but not me. And I’m confident enough in my opinion and abilities that I don’t give a rats arse what anybody else thinks. :-)
It doesn’t bother me in the slightest when somebody hates what I like. Who cares? It doesn’t diminish my experience. I don’t need anybody else’s validation.
Conversely Im very comfortable knowing other people make great use of tools like BM3 in a way I never will. I enjoy knowing how other people make music. I like seeing a great drummer drum even though I can’t drum for toffee. I have trouble coordinating one hand let alone two hands and two feet. I’m in awe that that’s even possible.
So yeah. I like the kind of music people make with BM3 and MPCs. I enjoy seeing how they do it. And learning different ways of programming can be inspiring, especially if you are that knowledge and use it differently.
If I want BM3s sampler as an auv3 I’m very aware of why I’d want it and how I’d use it. I’m also aware of what it couldn’t do without the rest of BM3. But guess what. I don’t want those bits.
Other opinions are available and equally valid.
Actually, I started a thread for this in the 'Desktop' section.
As good as this might turn out to be (I'll reserve judgment until I hear some better examples of stretching etc.), it still completely misses why I (perhaps others, also) want to be able to use an AU mini version of BM inside other DAW. I had a whole thread asking about workflow possibilities between BM and other DAW. I specifically wanted a way to be able to sample from , from example Cubasis, to then be able to edit and make kits from those samples in BM, and to then be able to play those kits live into other DAW. After a pretty circuitous discussion, the solution turned out to be as simple as hosting as IAA.
Of course, now having owned Cubasis, I now understand how much of a non-starter IAA is. How much of that is user-error is yet to be determined (still experimenting). Either way, even if it did work as expected, there are clearly advantages to AU over IAA.
I'm just obviously missing something. It seems nobody has an issue getting behind Koala's integration as an AU effect, but there's such a huge amount of resistance to the same happening for BM. Yes, there'd be some compromises. But in the model I suggested everyone would have to own the full app anyway. So nothing is lost. The user gets the entirety of the BM experience when needed as such, but then has a 'bridge'/plug-out/plug-in to utilise all of those great kits we've spent hours designing, within other apps...should we so desire.
Nothing more; Nothing less
Or maybe I misspoke
For some reason I thought the cycle pretty much coincided with a calendar year (Did LP get release in December, perhaps?). That being the case, I'm just imagining there being people in the later months of the year who'd wait for the next update in order to get those features in their first paid activation.
But I'm sure I'm wrong about some of that, having not really followed the progress of LP. I just think the model is a good way to ensure that the developer is continually motivated to 'Bring It!'
If it works out then perhaps other developers will adopt the idea, to the benefit of all.
I LOVE KOALA.
It is closer to feeling like an instrument than most of the iOS apps.
When it comes to capturing ideas, very hard to match Koala.
Actually, I came here to post that if I keep my use of Beatmaker3 to a drum machine, I'm happy with it. When I go deeper, the quirky UI adds a lot of friction to the experience. It obviously has deep, deep capability, but needs some UX design love.
So for me to come back to it, I'll do my best to contain my curiousity.
I have no real evidence, but considering what @hansjbs wrote the „Sampler“ is probably the whole BM3 app (or spread over the whole app), it‘s not a dedicated module that can be isolated.
The existing design has a certain functionality - „extracting“ the sampler would essentially mean to rewrite the whole app.
Which of course is possible, but that effort would be subtracted from what‘s going into BM3 improvements atm.
Time is an extremely sparse resource in development...
ps: the audio processing part in a DAW like app is just a small fraction of the code. The majority of work (90%) is about presentation and handling of user interaction.
That’s pretty much it and the fact that it’s not a dedicated module. I think he already understood that. I understand what people are asking for, I just want them to understand that even with that some won’t be happy, they will ask for more features which would mean it probably would turn back to being BM3 again😂😂😂😂
😂😂😂 I just replied above about an au sampler with people asking for more features would turn back into BM3 again 😂😂.
I don’t want iOS to be like desktop at all, that would kill the vibe of ios. Desktop Tablets are getting cheaper and MacBooks are more powerful get those for the desktop mobility stuff. Let iOS/iPadOS be what they are.
Ain’t that true. Can’t please em all :-)
But you can’t do anything if you’re scared of some people being unhappy. That bit is inevitable.
It’s the main controller I use for iOS.
If you can get one cheap, go for it because:
2.It is the most easy controller to set up
3.You can get a heap of uses out of the knobs and XY pad because cycling through “scenes” is very fast.
It also does this dope light show when you’re not using it.
Also the XY pad is assignable so if you can MIDI map the XY pads in BM3 then it will work. It’s not just for the Roll/Flam stuff.
Thanks!! The issue is with GUI touchscreen knobs, no issues via midi. I will try to report on Intua Forum or Discord.
I never received any mail even spam. The issue must be there. As I said I will report again, thanks you a lot for help.
Yup!
Balanced and well-stated case.
Yep, I think it’s clear most of us want the “instrument” part as an AUv3. It doesn’t require the other components to function that way.
And some of us want both
Would be curious to know the kinds of numbers (of users) such an expansion/option would bring in.
Not much at all. I don’t think many understands how many people use BM3 and are happy with it. I didn’t understand/believe either until maybe a couple years back.
BM3 did very well for the developers and continues to do well. Heck it’s been doing pretty well since version 2 so with that, it’s best to wish/get another developer to create that auv3 sampler.
This is the second time you've made claims about potential/actual market share (Serato and BM), without providing any actual proof. I did ask for data to support your contention that I was one of only a few people who preferred using 'Sample' in my go-to DAW, but you've yet to answer. Now you are asserting "Not much at all" in response to my wondering about how many currently non-BM customers an AUv3 option would attract. So, I'll ask again for some proof for your claims.
There's nothing wrong with speculation. That's what we're doing in this thread - speculating, throwing around ideas etc. And if you want to say that you "don't think" there's a potential market, then that's all good. But if you're making absolute claims then please provide proof.
Thanks.