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.
Audiobus 3: things you should know / upcoming features
Hi all,
First of all:
We've tested with dozens of beta testers and our Testflight logs show no crashes, which is why we think Audiobus 3 is ready for prime time. But bugs will be found, and we rely on you to report them. The best place to report them is our Zendesk support system
Thank you! 
Some things you should know:
- Don't use Audiobus 2 and Audiobus 3 at the same time. Apps are going to get confused.
- Siri, Facetime, Skype calls will mess with an Audiobus 3 session. We're working on that.
- To avoid inter-app-audio issues with zombies of apps that are still running in the background and that are not visible in the multitasking menu: just reboot your device before an Audiobus session. It's not absolutely necessary, but when something goes wrong, a reboot fixes problems 99% of the time.
- Since Audiobus 3 launches apps into the background and the preset system invites you to have bigger setups, you might save some battery if you're reboot your device after a music making session (that also saves you the reboot before your next session
). The reason for that is that some apps like MIDI filters or audio generator apps might have been launched into the background and you might not ever have brought them to the foreground. So they don't appear in the multitasking menu, which means you won't be able to quit them manually (because they're not visible). - AUX presets are not accessible if there is no preset management for that built-in into the AUX's user interface, find out more in this thread. Join that discussion to voice your opinion.
- If you're a developer: The new Audiobus 3 SDK will be available in the next few days.
Here are the features that didn't make it to the 3.0 release that we're working on right now. I expect them to be available very soon:
- Audiobus Remote is not fully compatible with Audiobus 3 yet.
- Ableton Link Status is not passed on to AUX instances yet.
- IAA launch/stop messages are not propagated to apps in the pipeline (Workaround: use global Audiobus stop/play buttons)
- no midi learn for the Mixer, app buttons and presets. This might take a little longer but it's high up on our to-do list.
- double tap on mixer controls to reset to 0db & center pan
- support for Bluetooth MIDI
Known Bugs:
- Eject button for filter apps is inaccessible sometimes when large setups are loaded. Workaround: switch back between MIDI and audio mode, that will reset the view.
- iPhone SE Landscape: Mixer view cannot be scrolled after loading a preset
- the iConnect Audio 4+ interface from iConnectivity doesn't seem to work properly with Audiobus 3 in combination with midiSTEPs and midiLFOs with Audiobus 3. I've contacted the developer of both apps about this.
- Fixed: There's currently a bug with the compatible apps list in that it doesn't show the hundreds of apps that can be used in the MIDI output slot (every app that has an IAA instrument port that is registered in our database can be used there).
- sometimes other iOS devices show up as MIDI senders in the midi input/output slot.
I will update this list with new information once it become available.
Cheers,
Sebastian
Comments
Do i need Audiobus 2 now or can i uninstall it?
Make sure to save your presets, but then you can delete it.
Please add Bluetooth MIDI to the features to support NonoKey/NanoKontrol Studio and BlueBoard as soon as you can @Sebastian. I think it's quite important.
Adding that. Yep, that one should be easy.
If you do, save yourself a day of head-scratching and be mindful of this iPhone Bluetooth bug (still present when I last checked): https://forums.developer.apple.com/message/211931#211931
Thanks!
how do i migrate the presets to Audiobus 3 ? bit confused as to how to do it....
I second this
Seconded.
loving it so far
Really easy to set up some experimental midi stuff and save it for exploring later.
Have been setting up a SPA drum patch into Ruismaker and then adding some random sauce from midiflow random.
Can't wait for more midi apps to become AB3 compatible. Another thing I've tried is Animoog controlling several synths at once. Just tales a few seconds to set up. No menu diving
hopefully Jonatan will get around to updating AUM soon with AB3. You can route the AB3 channels in AUM and record into Audioshare but at the moment you can't see what source is what.
Also in AUM you can see multiple "Audiobus intermediate out" ports but not sure if these are working yet. Are these the multi audio out ports which aren't currently working in the release version?
He's working on that as we speak.
Audiobus hosts everything itself and then passes on the audio to IAA hosts like Cubasis and Audioshare via it's own Intermediary ports. That's what you're seeing. You can't do anything with them though, because they're all controlled by the Audiobus/ the Audiobus SDK. If there's audio arriving on one of them they're already connected, which means you cannot re-host them. And if there's no audio, they're just silent.
Long story short, ignore them. The next AUM update will most likely hide them.
ok thanks
>
Please do this soon @Sebastian. Thanks and congrats.
The tempo will be saved by all apps that are part of the session. In an upcoming update, Audiobus will save it as well (and probably even set it).
I know ;D
Given AB team's usual control standards in the name of user ease ;
( is there an emoji for " that's not necessarily a compliment" ? )
it seems strange & wrong to me that an app can be AB3 Optimised , but NOT be StateSave compliant .
I am refering to Olympia Noise Co. Patterning & Chordion , whom I've expressed this to on FB , but also Cubasis & a couple more I think according to AB Database .
Surely AB3 Optimisation must include StateSaving , both philosophically & practically ,
or are we still searching for app specific presets in this new Ab3 world ?
I suppose congratulations are in order for AB team's work ,
though as I have stated previously I lament of a free market where so much duplication of manpower seems a waste to the user ,
& therefore wish Audiobus had collaborated with AUM dev to produce a single Uber app that offered ALL the advantages of both , instead of either using one & losing unique functionality of other , or attempting crazy interwiring to gain benefits of both .
This post infuriated me in a deeply subtle yet poignant way that I can't quite articulate.
Re: State Saving.
Some apps are better suited in a practical manner to save their own states. For example Patterning (and Modstep).
We're not dictating what developers can/should do. Adding state saving makes sense for some apps, but we are in no position to outright tell third party developers what they should spend their time with. If users demand state saving, developers usually oblige.
@OscarSouth " Deeply subtle yet poignant " , thanks .
Was it the AB Control , StateSave or Aum collaboration that offended ?
Re: StateSave . I think your reply undermines the whole point of StateSave in Audiobus , especially in AB3 which is meant to be the final one stop Global SAVE & LOAD .
& how can an app be optimised if it forgets its settings next time you load the preset?
What practical manner are you thinking ?
you can't dictate that devs implement StateSaving
( indeed not even seemingly persuade your partner & its inventor to add to his own Loopy )
but I meant " AB3 Optimised " classification to my mind should include StateSave in its entry criteria ; so no StateSave = not AB3 optimised .
It just seems contrary to the Audiobus ease of fuctionality ,& integrated working paradigm,
that apps vaunted as " Optimised " aren't , & when user loads preset with "optimised" apps it's not going to work correctly .
Ah , ok , maybe I should have asked exactly what "Optimised" meant to begin with . @Sebastian ?
But having seen on video e.g FugueMachine present itself as four independent midi engines / channels in the midi page as " Optimised " for AB3 app I had assumed there was a lot more to AB3 Optimisation than just opening itself , so I'm kinda hoping you're wrong @Max23
AB 3 optimized just means it launches into the background displays AUX instances in its connection panel and basically uses the new Audiobus 3SDK. We could just say that it uses the Audiobus 3 SDK but I doubt many more users would understand that.
@Sebastian, You mention rebooting a couple of times. I've always had good success with killing ghost apps by holding down the power button until the power-off slider shows, then holding down the home button until returned to the main screen. Is it possible that this is as effective as a restart?
I don't like thinking about having to reboot all the time. It takes longer and messes with touch-id, and some other apps I use. I'm interested if the workaround above is just as effective.
BTW, is there any way to know what is still running in the background?