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
I'm usually a nightmare customer since I know way more about the gear than the people who are trying to sell it to me
(ie. I do my re-search of the stuff I'm interested in before I go to the store. I don't go to the store to get 'educated' by sales-talk).
Sadly the technical gear knowledge of todays sales persons (at least in my experience) is fairly low and the only focus seems to be to to sell as much stuff as possible with the highest profit...
One idea here would be a 1% discount for every product related question the sales person fails to answer
(I got roughly $40 discount on the MicroFreak when I bought mine by demoing it to the sales person...).
I remember having to explain MIDI in a music store back in the day...
I almost forgot why I stopped using BM3. There are aspect of the app that I miss as it’s unrivalled for certain things
But.
Out of curiosity I have just tried it again and have reminded myself why I never use it any more.
I started working on a song by importing some audio stems.
To those tracks I added one auv3. I wanted a moog bass and I started by adding a Viking synth. But BM3 still doesn’t manage auv3 presets which meant I couldn’t load any presets into VS. But I have model D so I added that instead. And BM3 started to burst at the seams. I couldn’t record the baseline as I was hitting cpu spikes and everything got too glitchy to even play model D.
So one auv3 and 8 or 9 audio tracks with a smattering of fx is too much.
I started over in GarageBand and it all works fine. No cpu issues even though I’m having to use more audio fx as GarageBand doesn’t have aux tracks so I couldn’t use auv3 reverb and delay on sends.
And I can keep adding more auv3s. I know my iPad Air 2 is a bit creaky now, but BM3 falls over long before I have cpu issues in other apps.
This is still kind of bizarre at this time. One would think the GB team would want to demonstrate how to conserve CPU resources. Especially since it’s also an educational platform.
We can stack auv3 reverbs on a track but not on a send?
Irresponsible ish.
@klownshed if you want any realistic chance of using the Moog AUv3s in your projects on an iPad Air2 you’re probably going to have to set a higher buffer than the default in BM3
I would suggest 512 or even 1,024 samples buffer to avoid the crackling.
To be clear, nothing you posted is specifically BM3’s fault
It would certainly be nice to have a patch browser for old plugins like Viking, but fortunately all new plugins provide their own patch management in the UI, and other devs (such as BramBos) have retrospectively added to them their older plugins - so this isn’t a priority for the BM3 dev.
GarageBand has reverb and delay available on sends but they’re hardwired so you can’t switch them for auv3 plugins instead.
I wouldn’t go as far as calling it irresponsible. Ish. Though. ;-)
I would 😅 plus naming the effects sends “Master Effects” that takes the cake.
I use GB extensively but I recommend Logic to all new/aspiring producers I meet so they don’t get such a bad education
I’d already set it to 512. 1024 is way too long to be able to play live. I can’t live with the latency. I set it to 1024 when I’m mixing/arranging but it’s a no go for playing.
Yes it kind of is. 😂
It is demonstrably less efficient than other apps when using auv3 instrument plugins.
Sorry. But it’s true.
I know. But Most DAWs offer preset hosting and it’s part of the audio unit spec for the host to do so. Whether or not it’s a priority for Intua is something I can’t know, but it doesn’t mean it’s right. But it’s not a biggie really due to the sheer number of plugins that do their own lewser management.
I’ve been using Beatmaker since version 1. It was the first daw type app I ever bought for iOS.
I used BM2 for years.
I didn’t say any of this to be hostile or to troll.
I have a degree of fondness towards Intua but unfortunately I can only speak for my own experience and BM3 ain’t very efficient.
To be fair to Intua, auv3 hosting is still a bit of a mess for most DAWs and it would appear, especially given how much things have changed in iaoS13, that Apple should shoulder much of the blame.
But when I compare like with like I can get much more done with other apps before hitting CPu limits.
However if you take auv3 instruments out of the equation and use BM3 as a mega sample it’s great.
Almost all of my issues with BM3 are when using it to play auv3 instruments, including the way they’re implemented.
Nothing comes close as a sample chopper-upperer.
I will continue to keep BM3 around and just use it to its strengths.
Logic ain’t on iOS.
I’ve used logic since version 1.1 on Mac! It was Emagic Notator Logic back then. It came in a huge plastic box and included a notator Logic t-shirt.
I have literally been there done that got the T-shirt! 😂
Heh. Yup maybe Logic makes it to iPadOS in October 2020. You only have to look at Logic Remote to see a glimpse of what they are planning...
but until then iOS/GB for me, Logic/Ableton/Mac for the kids.
I’ve just been revisiting BM3, and instead of using it as a DAW, testing it as an IAA sampler player/rhythm thing into AUM. And it seems to work ok.
Since I don’t use the iPad as a DAW anyway, this might get some use when I make my clips for Ableton.
Umn... why should I care how famous BM3 is when it glitches and crashes on me all the time? The iOS DAW that “wins” for me is the one that is stable, has the features I need, and has a workflow I like. So far there is no winner, but BM3 does get a solid 1 out of 3 score.
As you mentioned above AUV3 is still a little unstable in most DAW. Moog Apps, audiodamage apps and some other give me issues in Cubasis. Auria and BM3 so I stay away from them until they’re more stable. I saw moog came out with a bunch of updates for their apps, I’ve yet to try them in BM3 and other app’s recently.
I use plenty of AUV3 instruments and fx in all my BM3 projects with samples, stems etc... so far I haven’t had a major crash in a while, maybe 2 to 3 times a month and I use BM3 daily. Maybe it’s because I use it so much that I know it’s quirks but I can’t seem to remember when I started doing what I do with it. It just came natural.
Also just because you have a comment on BM3 crashing doesn’t mean you’re trolling. Us beta testers want to know what make BM3 crash so we can reproduce and add to our bug list. Please when u get a chance drop by the forum and document how you make BM3 crash. Thanks.
Ns2, Gadget, various Audiobus setups. Maybe I’m lucky
I have run BM3 on an Air1, Mini2, 2017 (I guess iPad 5?) and a Pro 10.5. While the 2017 came close to working well in terms of performance, stability is more of an issue. I find anything less than the 10.5 Pro is hard to recommend without caveats.
see, there are people who show with what tools they work with
and then there are these people who just work with the tools they have.
My guitar and piano NEVER crash on me, so there’s two tools I can count on anyway 😁
Haven’t you broke a string on your guitar? Or they go out of tune?
I think we all do work with the tools available even with their inadequacies. I don’t think any of us would be on this forum otherwise. I just think it’s silly to argue about which DAW is best (or even sillier, most popular) when NONE of them are working well enough yet to call professional, imo, at least when used in conjunction with AUv3s, IAA, or an host like AudioBus (much easier to stay stable when the app is self-contained, but it’s also a less useful tool that way). Still... more to love in iOS music production than to dislike I think.
I admit that my attitude is biased by the fact that I’ve spent 20 years using ProTools and plugins on desktops and laptops, and problems are VERY, VERY, rare. Our studio would have gone out of business if things went wrong as often as they do on iPads and iPhones. I also spent 20 times more money on desktop/laptop so there’s that “get what you pay for” factor.
touché! 😁
I totally agree with you. I’m of the camp that I don’t expect an iOS DAW to be that solid in today’s world just because of maturity. It’s a small corner of the music world compared to desktop and I just don’t see it changing super drastically. I am definitely amazed at what I can do right now and it’s enough for me. I love my desktop workflow and won’t give it up...and I don’t have to. Nobody does. It’s an AND not an OR. I know there are folks that have totally switched and that’s awesome! More power to them.
As for pianos and guitars, I guess they remain up with known workarounds
20 years ago ProTools had been in development for more than 10 years ... with a full-time dedicated development team larger than any team (by a considerable amount) working on iOS DAWs today (including a full-time testing department).
During much of its first decade, it required dedicated hardware (often more expensive than the computer it ran on) and had limited MIDI.
So, yeah. You get what you pay for. iOS DAWs will probably struggle on the stability front when trying to compete with desktop-like completeness until the hardware advances with more memory and better use of all the available cores -- which is probably more of a challenge on the OS side than we appreciate given the need for aggressive power management (throttling).
I’ve gotten > @espiegel123 said:
Exactly. It’s why I felt a need to admit my bias.
And 30 years ago we were still using magnetic tape at the studio because we didn’t trust computers yet. So glad I don’t have to deal with tape anymore.
But we developed chops and patience. I think my years tethered to tape and pre-MIDI reliance on cutting to tape with every track probably makes me less annoyed by workarounds than people that grew up with MIDI.
THIS
Agree with everything except for the "don’t see it changing super drastically"... I just think it will eventually... but I too am amazed at what I can do now as a hobbyist for the past 18 years, compared to what I did with Reason 2.0 and Sonic Foundry's Acid Pro, lol .
To me everything on my iPad is a tool for crazy inspiration to start, to then end up in Ableton, thus BM3 is like my poor-man's MPC... which also ends up in Ableton. I never expected to get a super solid stable digital audio workstation for under $20 (I bought BM3 at launch price).
Who knows when the BM3 update wills ship but I'm honestly starting to loose my patience...
I mean at least drop a temporary update and fix to input monitoring and bring back the fun into sampling
(And no the work around to use audio tracks for this is not a viable solution!)
Meanwhile I'm back to using Renoise on my MacBook Air and the iPad serves as a sound module thru IDAM.
Beta testers indicate steady progress. Developers honestly can't know how long debugging will take. From all indications, the dev is working hard.
Take crap for a buggy release, take crap for leaving out features, or take crap for taking a long time. No win for the developer.
What is that formula again? Quick, Cheap, High Quality. Pick two.
Or something like that.
Yeah, but that doesn't really help those not on the beta, right?
What triggers me the most is when an update broke existing features and it takes ages to get them back if ever.
Don't know if the touch-related issues are fixed either?!
(Tap and hold a pad, switch to sample edit view while holding down the pad and you can still play it by moving your finger even though the pads can not be seen, there's also some UI glitches related to the widget library in use and I have no clue if the dude is still part of the team).
But yeah, I do hope those on the beta look at every aspect of the app.
I suffer from slight OCD and the app is not good for my mental health, to many small WTFs in too many places...
I’m not comparing the performance of BM3 to desktop DAWs. I’m comparing it to other apps I have on iOS.
It would be nice if I could use BM3 more but I hit a brick wall with it long before I do in other apps.
But it was pretty disappointing to hit a brick wall with only one auv3 instrument and 8 audio tracks.
Anyway, I’ve not given up. I just made the baseline in another app and used that as another audio loop in BM3 . I can use the sampler to chop up the loop for more variation if needs be. Might be fun. Who knows something interesting might even come of it.
To be honest I don’t think the song is going to be any good anyway but I’m enjoying making it which is all that matter to me at the moment.
I’m quite liking using BM3 with only audio and sample tracks.
But I hate using auv3 instruments in BM3. I think the Intua guys were drunk when they implemented auv3 instruments into banks/pads instead of as their own track type. ;-)
But thats Cool... I can use aum and NS2 to make all the synth loops I need.
I like having everything as an audio loop anyway. I dump as many loops as o can into BlocsWave on my phone, which is great fun And allows me to make music on the throne 😂