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.
Michael got interviewed
Pretty good interview with Mike at 7:55 minutes:
Comments
Nice interview.
Did you listen to the whole thing? Anything that spiked your interest in it?
Well, call me crazy, but I believe he said Audiobus 2 will allow us not only to save app chains and share them, but also the state of every app in the chain, meaning that the preset chosen or other settings of the state will be saved.
Exactly.
EDIT: This is a feature we're still testing and it'll require developers to update their apps with a new version of the Audiobus SDK. Currently we're not handing out this SDK to everybody by default because ... we're still testing it.
We want to make sure when we launch Audiobus 2 we'll have a direct and fast connection to all the devs whose apps support this new feature in case there are any bugs that need fixing. You might remember this procedure from the Audiobus 1.0 launch.
My interest was spiked by details concerning saving app configurations in a preset. I guess we're going to need to get a list of "state-saving" apps. Hopefully it'll be a lengthy list. Never really thought about that feature until now.
maybe it will also kick more devs into supporting MIDI Program Change too, the awareness that we really really need App state control.
Great news thank you!
Great interview and the state saving sounds terrific!
Well done
Nice add.
+1 for wot dwarman said....
if 'someone' could drop something right in the middle of all this..(I'm seeing an audulus style ui rather then a menu to select midi input/output)....a visual representation that is easy to understand,where we can join 'midi' nodes....that works....?!?
@dwarman - actually this 'state-saving' sounds exactly like like MIDI program change.
Indeed the first devs who need most kicking into supporting it are Seb and Michael. It would be crucial for this feature that AudioBus presets can be selected via MIDI program change. MIDI Bridge has done this quite well. You can program it to issue program change messages to connected apps when it loads its own preset which can of course also be selected by program change. With one touch of a knob on the keyboard I can setup all the MIDI routes, filters and have my sound generating apps switch to the sounds for that preset.
United States of Apperica ....SuperCool feature!
especially the ability to share those presets. Wow, very excited to use AB2! Oh btw...... © 
@snoopy said:
State saving will not include MIDI data. We've decided to discourage third party developers from saving any sort of MIDI port or channel information in the Audiobus state. The reason for this is that when shared this data could overwrite other user's MIDI settings (for example mapping for MIDI controllers) and apps typically don't have any way of managing these settings in their UI. So loading someone else's app state with MIDI settings could include invisible MIDI settings changes that cannot be reset easily, which is bad.
Also we don't want to mess with potential future MIDI routing via Audiobus (which we're still planning to add in a later version of Audiobus).
@Sebastian will this potentially include tempo sync between apps? Kind of audiobus master clock?
Sorry, I used 'state-saving' incorrectly. I did not mean that AudioBus presets should save MIDI state. Simply that AudioBus should allow a user to switch its presets via MIDI. That feature needs to be there when you launch presets, IMHO.
As for adding MIDI routing to AudioBus. I've said it before, but you guys should assimilate MIDI Bridge. Imagine having a central point for setting up audio and midi and clocking in the one place with nice AudioBus UI and app switching via MIDI too.
I'm doing work with a company Mac app and we're trialling the MIDI Bridge library right now. It gives you clock send right out of the box and Nic promises he is going to add routing to it also for us. From what I can gather the iPad version includes MIDI app switching support too (disabled in the Mac version). We've found it very easy to integrate into our application. We may consider an iPad app at some stage so we can just re-use all our MIDI code. It would seem logical for AudioBus to look into it also.
This is great! Really looking forward to ab2. App of the year for sure!
@supadom said:
No, not in this iteration.
I knew we'd get to this level of control eventually. Good to see the right people heading it up.
It's like seeing the evolution of midi all over again.