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.
Let's talk about Audiobus 3
Hi all,
We're getting closer and closer to the Audiobus 3 launch. So here I am to create hype tell you about what we're doing with it and create even more hype answer your questions.
We've been working on this for about two years now and the main goal of Audiobus 3 is to help you make more music with less time spent on setup. One way we're doing this is by now automatically and instantly launching apps into the background. We can even launch most output apps into the background, like Loopy and Cubasis – something only we can do because the Audiobus SDK in these apps allows us to tell them what to host and how to behave. It's pretty neat, and it’s going to make setting up sessions and switching presets much smoother.
We’re looking forward to showing you more of the app in the days to come; we’ve got some brilliant features to show you!
Audiobus 3 is not going to be a free update. We think its features and general workflow improvements make it an instant purchase for anyone who’s serious about making music on and with iOS devices.
I'm here to answer your questions over the coming days and weeks until launch.
Cheers,
Sebastian
Comments
Will AB3 be backwards compatible with apps with AB2 support ?
Will it be a separate app, so we can still use AB2 in case some apps do not update?
Will it have a built in midi keyboard?
Will it have any midi controllers, such as knobs to control app settings?
Is there any AUv3 integration? If so what's the nature of it?
Yes.
Not Audiobus 3.0 but we're aiming for that in 3.1. We think adding MIDI controllers is required for decent AUX support but we want to do that right, so we're not rushing it into the initial launch feature set.
We're currently automatically adding volume/pan control for every app that sits in the Audiobus input. We're going to add more features to the mixer in future updates.
We're not limiting what can be sent. If an app sends MIDI CC messages or manipulates them as a filter then that can be passed on to apps that live further down the MIDI chain. State saving is available for all apps supporting Audiobus and for which their respective developers has implemented that feature.
Audiobus itself does not create and MIDI messages. It all depends on MIDI senders/filters/output apps.
Whatever it can do, it'll be Fab......... As always. Looking forward to the new version.
Woot. Weeks, eh? Congrats!
Stuff I'd be glad to hear more about:
1) The organization and recall of saved states. Still a giant flat list? Is there MIDI PC support?
2) Whatever is going on with MIDI processing and routing.
3) FX app bypass?
4) Interdevice audio? MIDI?
5) Will Loopy Masterpiece be bundled?
And a +1 for the integrated keyboard and backwards compatibility questions above. If there's a keyboard integrated, it'd be sweet if AB3(dot 1) could detect if SoundPrism is installed on the device and if so, offer it as an alternative keyboard directly within the app.
No separate app please. What about the MIDI features that will come with this update? will I be able to split a MIDI keyboard between apps with ease inside audiobus? As a live player rather than a home/ studio guy that would be awesome. MIDI splits on iOS are a pain to setup and use comparing it to something like Mainstage 3 for example. Or maybe everything MIDI related will just be background stuff?
Sorry, there's no other sensible way for us to do this. We'd love to do a paid upgrade but Apple doesn't allow that. And IAPs are incredibly messy.
That's exactly what Johannes Dörr is working on (and I've had the pleasure of being involved in making sure it's pleasant to use). He's made a MIDI splitter and it's incredibly easy to set up. You'll be able to set it up in seconds with multiple split points.
So I guess this will hit about same time as Cubasis 2....
Auto starting apps is all I hoped for, and the MIDI features are a blessing from the heavens. How much will it cost.. and when can I pay it?
Yep, it's a flat list but it doesn't automatically load a preset when you tap it anymore. You'll have to tap load after selecting the new one, so you don't trash your current setup by accident. Also since everything launches into the background it's a lot more powerful.
I'm sorry, I don't understand what you mean with MIDI PC.
Can you be more specific? It's basically the whole thing Audiobus did for audio routing, just for MIDI as well.
You mean MIDI FX app? Yep, we're probably going to add a bypass button to the connection panel for MIDI filters as well.
No, we're not touching that with Audiobus 3.
Heh. I can't talk about that regarding release dates but damn, it's so awesome... ^_^
Apps that have been compatible with Audiobus 2 will be after they update to the Audiobus 3 update but you really want to update to the Audiobus 3 app, because that's the future.
Regarding SoundPrism: huh, neat idea.
We've not settled on a price yet but it'll be somewhere in the range of what Audiobus 1 was initially, if anyone remembers. Right now it doesn't look like it will have in-app purchases.
I'm just hoping it's not AB3 that is keeping some major apps from getting released already
(Beatmaker3, BeatHawk, Cubasis 2, FLM 3 etc...).
Is the midi transparent ?
What I mean by this is, Launchpad only works with Launch hardware, if these are connected within AB3, will the devices still appear as Launch hardware to the LP app or will they become AB3 midi ports instead ? If so, is it possible to exclude devices from the AB3 midi routing to get around this ?
What about IAA. Any better "collaboration/integration"?
We're not changing the way apps work when they're not connected to Audiobus. And we're not doing anything to hardware midi controllers. But if apps are connected to Audiobus and support Audiobus 3 MIDI then their MIDI routing will be done within Audiobus 3. There might be exceptions for this for apps that want to do something special with MIDI CC and want to have the settings for that inside of their app's UI.
But the main point is that we are going to urge third party developers to always make sure that stuff like automatic MIDI connection to other app's open CoreMIDI ports isn't happening anymore. Double notes and opaque MIDI routing needs to disappear from iOS, so that iPads and iPhones can be used as reliable and pleasant MIDI controllers, without any nasty configuration headaches for users like you.
What do you mean? Audiobus 3 is built upon IAA.
I don't think you need to worry about that.
Will we be able to use AB3 as a mixer? And can I map my midi controller?
Yes.
To the Mixer? Mhh... maybe in 3.1? Is this super important to you for it to be in 3.0?
Sorry about that. Is it possible to recall states via MIDI Program Change messages?
Yeah, too vague, I know. I just love love love MIDI Flow and am looking forward to any/all details about JD's work on AB3. You mentioned that he was working on some smaller MIDI apps. Can you give us an idea on the scope of those? You mentioned filters. Arpeggiators?
I meant audio fx. As it is now, you have to remove an app entirely to bypass it. Bypass for MIDI FX sounds rad.
Of course I'll buy it on day one but is it fair to assume that to keep using the long tail of audio apps, including abandoned apps, we'll need to keep and use AB2 for a while? Probably no chance of loading AB2 as in input or output into AB3, eh?
Do it!
I'm guessing it's possible to route audio into loopy masterpiece and midi map the controls. A possible work around ?
How long will you continue support for AB 2? (I ask because I imagine not everyone will update right away).
Will it be possible to use AB3 as an IAA-Generator for those rare moments when users by accident start a so called 'Pro' apps from a Retr....ms....???
How expensive will it be ? Just a ballpark estimate would be nice.
I'm guessing it will support multi out interfaces this time around?
Also will it have a significantly bigger ram footprint than the previous version?
Oh you mean switch Audiobus presets via control messages? Like back and forth? Interesting feature, probably something we can add.
Nothing is keeping Johannes (or anyone else) from building all of these things as MIDI filter apps for Audiobus 3.
You can already bypass audio effects via the bypass button in the connection panel. That's probably how we're going to do it for MIDI filters as well. But I guess we could add specifica UI for it in the Audiobus app. Hmm...
Any app that works in Audiobus 2 will also work in Audiobus 3. No need for any AB 2 in AB 3 stuff (and it won't work that way anyway).