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 bought a couple packs and they show purchased but after a few reboots they are still not showing up in the packs list. Any suggestions?
here’s a quick summary of the speicifc scenario that ‘might’ lead to corrupted autosaves (although if you’re sensible thiis should never affect you, and it has never affected me)...
It says purchases but not installed like my others
When i press reinstall it looks like it wants me to purchase it again
Great news!
But mine is not updating from.....014...
Normally just updates automatically..what update page please?
Not true. The iPhone version is still on schedule for shortly after the release of the Blackberry version.
Thanks so much for the info. I’ve always habitually saved constantly during projects. I am hoping perhaps force quitting was the culprit. Getting back into BeatMaker. It’s been too long. Ahh the ease of resampling thanks again for the info.
I got it...you mean in App Store update....
Wow...free vocal samples too......
Something that helps a lot with Cubasis 3 proper auto save is to go to home screen first before swipe app to close it. Could also help with BM3??..
It seems like a good extra level of safety could be to create a new empty project before force quitting. This should absolutely close down the project cleanly, I think. And that's only a few taps to accomplish.
Good idea. I may just create a dummy project and load it every time I quit - that would be a great test and no loss if the dummy project corrupts.
I don't see why you need a dummy project. Just save the old, then tap "New". Then quit. But whatever works!
unless maybe creating a new project leaves behind a bunch of autosaves, etc. I never really checked that.
So can you resample in bm3 like you do in koala/sp404?
I want to play a sequence on pads 1-3 for example and have to record as a new sample to pad 4.
Doable????
ha!
If you've already sequenced pads 1-3 you can do an export of those 3 pads/tracks and import the file to pad 4...
...or solo the pads you need to re-sample, use the bank hosting the pads as an input for the recorder and do a synced recording on pad 4. (So if you want to resample pads 1-3 in bank a, solo them, select pad 4 and use bank a as the input).
Sure not as 'immediate' as Koala but doable.
Yes it doable as Samu pointed above but why do that when BM3 offers you 64 pads per bank and more banks than one need for music making. You have a linear timeline as well as scenes
Ahh I’m going to have to try that. It maybe less messy if i resample in koala and import back to bm3 tho but def going to try those out!
I just love the resample workflow to get stuff to a single pad for triggering. I fully dig the time line and sequencer in bm3 but would love to resample pads on the fly as well. I’ll probably just resample via koala then import into bm3.
Just remember that when you do an export of selected pads they are separate files but there's nothing stopping you from loading multiple samples to the same pad and layer them with full control over each layer.
The 'solo' when recording to another pad is optional and just in case more pads than 1-3 are already sequenced.
When you use a bank as the sampling/recording source all active pads are used, thus the need to solo or mute un-needed pads.
You could also create an audio track that uses the bank as the source and record you performance straight to audio...
When it comes to BM3 it's not if it can do it, bur rather how and I feel @hansjbs will agree no?
Sure Multi In/Out AUv3 support is missing and it's still a bit wonky to record midi from AUv3 Midi Plug-Ins but it's doable...
...and sometimes require additional tools.
Good Luck!
Felt good to use this old classic piece of kit. Banged it around for a couple hours last night and all was good.
Could never get my head around the sequencer inside BM3 found editing inside it Clunky. Now we got Loopbud, Atom 2 hopefully coming this week I have options now for sequencing. Just re downloaded it.
The sequencer is actually quite similar the piano roll in Koala Samurai update.
On the top level of a pattern you have 'pads' and tapping on the 'keys' icon top right gives you piano-grid for each pad.
BeatHawk also works somewhat similar to this so it's nothing 'unique'.
When selecting a pattern in the pattern helper it plays it in 'scene mode' not 'time-line' which can be a bit confusing at first.
Patterns can be dragged from the pattern helper to the time-line.
I guess like with everything, once it 'clicks' it just works, but until it 'clicks' it can feel a bit frustrating.
Unfortunately there is no 'bank exploder' (ie. show each pad in a bank as an individual track).
Each bank can hold 128 pads (Samples, AUv3's etc.) and multiple banks can be created.
Many seem to prefer to have one sound per bank to make arranging on the time-line easier.
The more detailed the question is the more likely a good answer will pop-up
I completely agre.
It make take the long way out but my plan and the rest of the beta team’s plan is to have as solid and crash free app as possible first. Fixes for automation, some long standing bugs are already there so soon it will be time to add some features.
We have a whole list of features for Vincent already and some have been discussed. Like I said it’s just a matter of time and what’s more doable.
So is the consensus that this release is even more reliable than the previous version (which has been stable for me)?
I’ve been using all day today and yesterday, no problems.
Yeah it seems super stable. I opened a bunch of older tracks and no issues with playback or stability.
Appreciate it man!
I’ve always got along good with bm3 with what i know how to do. Hoping to try some new ideas to get a little deeper!
For now it’s been stable and I’m hoping that audio unit state save works on projects after time has passed. So far so good !
Getting back on the horse:
I will wait for the implementation of PDC, without it I cannot work with the app.