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
Whoot! Great to hear! I wasn’t sure if there was a an actual hunt / follow up!
I would love to sample it into a pad too but that option only seems available when you have an AU instrument pad as the source. Unless I have missed a trick.
Yes.
This is top priority. We all want this fixed.
I was told this and tried it before (along with other superstitions / voodoo tricks) but still have had times when it did not work. All it takes is five minutes of (admittedly like self diluted) magic to evaporate and...
Only way to load AUs at the moment is on a pad/bank.
It is hard to explain if you haven’t used BM3 (and it is an avoidable use case) but essentially it is a just a condition for recording that doesn’t record anything. You can sample AU instruments and AU fx just fine.
I know. What I am saying though is you cannot sample AUfx in the same way that you can sample AU instruments to a pad. It would be great to have the Sampler and Au fx with sample to pad.... ( unless I have missed a trick with layers or some such thing... )
Scenario... play a loop on a pad with Turnado loaded as an AU fx and spin them big old dials and record the ouput to a pad. (i dont think this is possible... is it?)
(PS. But if automation gets fixed then not a big deal as I will just do it as The Maker intended then!)
Great! My play with it last night has renewed my interest. I'm just trying to replicate, to some extent, my other groovebox experiences. And then in a perfect world, offload them from BM3 to desktop.
I have added a compatibility section on the wiki page. People please add to that page if there are other AU you find unreliable in BM3
https://wiki.audiob.us/doku.php?id=beatmaker_3
@hansjbs Wow! Great news. Thank you very much. 😊
A well-programmed host should be relatively immune to crashes and corruption caused by a poorly-behaved plugin. AUM and Audiobus 3 seem to have been built well in this regard. Plugin crashes tend not to kill things or prevent sessions from loading. I believe the same is true of Apematrix, but I don't have very much experience with it.
For DAWs, the situation is much more of a mixed bag. Auria Pro, for example, seems much more influenced by poorly-behaved AU than AUM and AB3. This is compounded by a bug in Auria Pro's recovery mechanism that is supposed to give you an opportunity to select a project snapshot when you launch it after a project crashed.
NS2 and Cubasis and BM3 are mixed bags. Their stability seems to be to be influenced by badly behaving AUs but to a lesser degree.
While AUM may occasionally go down when a plugin misbehaves, it (and AB3) does so far far less frequently than any of the DAWs that host AUv3. While iOS may not be as robust as the better desktop OS releases, it is more robust than you imply. iOS does have memory protection (an app crashing rarely crashes another app -- so much so that many people go months without even power-cycling their devices or doing any sort of reset).
Actually how host vs. plugins works on iOS is better than on desktop in some way. Or to be exact, it's a bit restricted on iOS exactly from reason to get hosts less likely crashing when plugon crashes. On desktop, host is allowed to load plugins into own threads, which is a tiny bit better in terms of performance, but also lot more propable that buggy plugin take down whole host.
On iOS, plugin's thread are strictly splitted from host thread. All instances of same plugin are sharing single UI thread, but each one runs DSP audio in own thread - and they all
are totally separated from host thread, communication between host and plugin runs strictly through iOS API "inter-app" communication layer.
Plugin is allowed to use any range of values for parameter. Host is able to get from plugin information about min and max values for each parameter: https://developer.apple.com/documentation/audiotoolbox/auparameter
And Blip notes that some AUs report wrong min/max ranges (bottom page in link). Could the long-standing squishy thingy bug be as simple as that? https://www.blipinteractive.co.uk/community/index.php?p=/discussion/479/some-notes-for-au-developers
Thanks. Those links are in the ticket. Hopefully they see them.
Also, I wonder if problems with Audio Damage Replicant 2 have anything to do with the particular iPad's hardware sample rate? Or the attached audio interface's sample rate?
That's my most used AU FX in BM3 and it's been rock-solid. Even when exporting multiple tracks w/ multiple instances of Rep2. 2017 iPad Pro 10.5 at 44.1kHz.
Yes you can. Don’t load the aufx for the overall bank, load it on the pad (pad mixer) with the AU instruments. Then you’ll be able to record With the aufx.
I was saying not with an AU instrument but with a loop on the sampler.
See, when this window is open you cannot go to the FX and manipulate them manually while recording.
Would be awesome to have this...
...on this...
...for the purposes of recording the Sampler output with manipulating fx in realtime.
@AudioGus Ahhhh ok now I got you. Good one
Also when using the keyboard it needs an option to route the midi properly to the right plug-in or plug-ins.
For example if multiple pads are used in one bank the keyboard needs to target the correct pad and its effects, it's a bit 'random routing' as is, the keyboard used for AUv3 effect always seems to target pad 1 in the current bank.
For example when using a vocoder plug-in on an audio track there is currently no way to route a midi from a pad/bank to a plug-in hosted on the audio-track.
I do get that a full routing matrix (route any pad in any bank to any audio track or pad in another bank) would get confusing for some but would be insanely flexible.
Looking forward to the update when it drops
(And maybe the above is already fixed, but I know nothing).
I remember someone mentioning this issue. I’ll check the list. I don’t use it that way so I’ve never noticed it. Thanks
Seeing all this attention being paid to fixing bugs in BM3 is the best thing to happen in 2020.
@AudioGus I understand...sometime it does feel like voodoo...some days the Gods seem to smile upon me in ways I cannot imagine and then I hit one button and....seems to happen with too many apps in my opinion...having said all that I think BM3 does seem to be getting closer to that sample Nirvana...and maybe even one day it will fully realise it's full potential. Still fun to work with.....
Yup, if I can automate AU fx without worry I will certainly be loading up old BM3 sketches and pushing them further... then start whining for bank freezing again when the CPU maxes out.
Yo, I’ve recorded my main while turning knobs on turnado, I do it all the time, when that window pops up set up everything, like what you are recording and all that, then close that window, now hit the little red circle 🔴 , you can see it above the window to the left a bit, try that,. You can do it, I’ve been doing it for a while, and I just sample the main.
Yes, I can record Turnado while twiddling knobs in some scenarios but was giving a specific circumstance in which it cannot be done.
Though I never cared much for mpc style sequencing I have always loved the sampler in Bm3. If the dang thing wouldn't crash 10 minutes into every use I would use it often. New features are great but if the stability isn't improved then what's the point?
If you are getting crashes every 10 minutes, there is something about your configuration (perhaps particular plugins?) causing the instability. I use it (primarily for its sampler -- using it for real-time re-pitching and tempo changing sliced up audio) and I rarely get crashes (i.e. I can go days or weeks between crashes). I don't run tons of tracks simultaneously and I avoid AU's that are known to cause issues.
What plug-ins are you using with it? What hardware and OS?
The only thing I know of that gets a crash in BM3 (that is not AU related) is if you set more than 64 slices on a sample and play back a slice by double tapping on it.