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
Got it!. Thanks @samu and @Geir
It’s almost as if the main developer isn’t there?
I guess congrats for the new update, but this update really makes me wonder if the dev(s) at Intua Have what it takes to keep bm3 moving forward? I thought that this update when it finally dropped would be something to assure me of bm3 having an actual future on the level it did a couple years ago...nope. Back to our thread already in progress.
great to see an update.
has anyone tried to purchase from the sound store? i was having issues previously with downloading packs
The recent sound store issue has been fixed for a while now.
cool!
No free speech at INTUA, they got a mall cop on the beat.
not seeing the update, tiered release?
@hansjbs or @tk32 Do you know if any sample based 'housekeeping' is in the pipe-line?
It would be nice to 'purge' the [xxx].wav temp files that are created when editing samples?
Ie. a simple 'cleanup session' function that deletes & trashes samples in the session folder that are no longer used by the session. I do get that the 'undo' function relies on the [xxx].wav files so when doing a 'cleanup' the undo history would also be purged.
A 'rename sample' in the sample-editor could be handy. This rename could optionally also rename the pad where the sample is used so instead of each pad with a newly recorded sample being named after the input source which was used to record it it could use the sample-name set in the sample editor.
I mean the file is already 'saved' (after recording) so having to re-save it just to give it a name is a bit meh...
To avoid the temp files and option here would be to simply use a one-step undo in the sample editor and skip creating the backup files for every 'destructive' action that is done, on average when I'm editing samples I get >20 of these temp-files which is pretty annoying!
To make 'destructive editing' safer the sample could first (optionally) be copied to the session folder...
...this way the risk of trashing the original sample is minimised.
There is one thing I do like in the NS2's sample editor and it's the way it is able to overwrite the source sample after one is done editing it...
Oh well, I'll dig into this update and see how many wtf's I bump into
Kudos to the devs and beta squad, keep it up!
/Samuel
Does this BM3 update fix export after 2 years? Has anyone tried it? Without proper export what’s the point?
Can you please provide more details on what you think is broken? I own BeatMaker 3 and was considering giving it another go, but if export is broken, I am not going to bother. Thank you.
For the past year on heavy sessions I typically had to export banks in two passes. I would export once with all banks selected and a handful of banks would be missing so then i select and export the missing banks. I never had a bank completely refuse to export properly. Exporting just the main out has been solid for me.
Edit: oh, I do recall a couple cases when it seemed like I had to delete a couple already exported banks to free up resources for another bank to export.
Thanks @AudioGus that is good to know. Appreciate you taking the time to detail the problem.
@MrSmileZ In the years I been using bm3 I never once had an export issue. Check your Auv3 plugins maybe
I export stems a lot from BM3 to either send to mix or send to artist and barely had any issues. The issue I had a couple times is when a track with AUV3 did not load correctly. So I always make sure everything is loaded and listen to the track before export.
I do bank exports, pads exports and do export with banks, pads and audio without an issue. I don’t ever export AUX track, so I don’t know if that’s where the issue is.
Export been solid for me.
Yes there are some sample based stuff on the list but not sure where they fall in priority. Right now automation fix and stability is leading the way.
I too would like some of the things mentioned above and they’re noted.
Bank freezing would be lovely... feels like duplicating banks may be some sort of under the hood precursor to this... ...(hoping anyway).
Another nice option would be a shortcut to 'render bank-track/pattern to new audio track/clip' with the option to keep the source. Don't know if unloading plug-ins after freeze to save CPU would be stable enough...
This could be used to quickly turn 'bank patterns' to 'audio patterns/clips'.
We'll see where things go, currently I'm enjoying ZenBeats 2.0 a bit too much on my iPhone...
...(iPhone because it's got more CPU juice than my iPad Air 2).
@tk32 and @hansjbs
Updated on both of my machines.
Going to have a play around with it.
Glad to see that there's movement on the horizon.
I'm just glad BM3 is still able to bring people joy.
By the way, I never set out to be its defender, mall cop, spokesperson and/or evangelist. Far from it, my only goal was to try to help other users get the best out of this app.
Somehow I seem to have pissed a few people off along the way.
I have found it generally takes multiple attempts to export a session/project on BM3.
It generally exports blank audio files for tracks that are using samples
Track 1 is a notable place where this happens for me.
After the multiple renders you have to go back and check the entire project to see what didn’t go..
On small sessions not too bad
On big sessions major time waste, annoying, extra ish.
Actually it’s notorious in my past use for track one pad one...the most.
Not to mention thinking to save every 5 minutes, because a crash is imminent in so many cases.
If that is fixed, along with the file management space waster backup thing...and crashes are down some more, I may have interest in bm3 again.
I can confirm that issue happens to me. Haven’t tried with the update but not just au issue when exporting.
A cool update to add would be if a pad doesn’t have midi on it it shouldn’t show up in the mix channels. Or maybe a button option to throw there so you can mix faster.
A couple of time-saving tricks for making sliced kits from long loops (ripped from Discord):
Activate Live Stretch, choose your slice mode but don’t slice to pad yet! Just go back to Pad View and enable Keys View! So no need to commit to slicing first.
Enable Live Stretch before slicing, and after slicing it'll apply it to all slices. Same with filter and envelope settings, too. Huge time-saver!
Another powerful BM3 slicing feature is playing each slice chromatically, like we can with each drum/pad in a drumkit.
If you have the internet and a personality this becomes inevitable.
I have downloaded the update, let’s see if it fixed vital things.
Edit: Deleted original post. Too much negativity. Stability is hugely improved to the point where I actually like it more than a dedicated Groovebox. Just hoping for more integrated features to come.
Just to understand, there is another update coming soon?
Still crashes on small loop range with cross fading and hitting reverse.
Same with duplicate pattern and undo
Launched Zeeon , I thought I couldn’t record automation and switched to AU knobs ,don’t touch the first unlabeled knob , instacrash
Loaded Phasemaker, nice automation worked , changing some parameters while automation big buzz alert, no audio rebooted.
Loaded good old Viking since my Air2 is struggling with BM3 (bigger buffers needed compared to AB3 and other hosts)
Everything fine , automations recorded but nothing is shown in the pattern .
Excited seeing AB3 sdk update , but still no AB3 as audio source to host there AUs
Half an hour on CrashBugger3 . Can’t wait to explore the app more !
PS. Intua’s bug section Forum is useless, well maybe it’s ok to check if something is known bug (some are 3 years old).
Directly sending a message to support at intua would be better choice but don’t expect any kind of feedback .
And yes I’ve reported most bugs ...but I’m not a beta tester so I’ll probably delete it before finding more ... maybe next year !
I personally don’t mind the frequency of the updates. As far as I’m aware I haven’t experienced any obvious regressions while using bm3.
Good to see this update. Gonna see how it handles the way I work now. Anyone know an easy way to import whole key groups into BM3? I can't seem to drag multi samples to the Layers view...I know I'm missing something, but the manual is pretty vague about this
Found something here, but it looks like it will be one at a time: 