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.
AB3 bugs
Hello,
There still are so many compatibility issues with AB3 what render it completely unusable:
1) I still find that Soundprism Elekro is listed as AB3 compatible
https://audiob.us/apps/capability/ab3
It is not! At least on iphone SE iOS 10.3.1 if I choose all when try to load it can't be loaded nor as midi source - it says "Port unavailable" and flashes some yellow warning. If I choose either Bass, Chord or Melody it even can't be loaded and gives Tap To Fix and yellow warning sign and when I tap and try to switch it locks/blocks AB3 completely.
2) also many apps do not receive midi if midi source is Animoog (I have only two apps which can be used as midi source Soundprism Electro doesn't work at all and animoog so can't test any deeper), some however work and this behaviour is regardless if midi destination app is marked as AB3 compatible
3) when connected to hardware midi all apps, but few give warning that the are not using latest AB sdk regardless that developer marked them as AB3 compatible
4) Phasemaker can be loaded only as AUv3 and can't be loaded as app, regardless it is marked as AB3 compatible - when tap on Phasemaher icon in app picker menu - nothing happens, regardless that AB lists it as AB3 compatible
This is AB3 issue in general:
5) Removing any midi destination creates ghost app in audio routing (audio routing is not removed) - this bug is not related to compatibility issues this is exclusive AB3 bug
With so many issues I found AB3 completely unusable 
((( I'm extremely disappointed , any chances for the get fixed or AB is doomed?
Comments
There's a fix for that waiting to be released. In the mean time I've removed AP Electro from being listed as compatible with Audiobus.
I'm not sure I'm following. Please contact us directly and we'll troubleshoot this together. For me Animoog works as a midi controller.
Which apps are you talking about? This behavior has nothing to do with AB 3 compatibility but a flag that the third party developer needs to set so Audiobus knows that the app in question does not automatically connects to MIDI hardware.
I'll contact the developer about this.
That is not a bug. But we're thinking about automatically removing apps from the audio page when their counterpart midi port has been removed. We just didn't want to remove anything without asking the user first but it looks like most users prefer this.
See above. They're getting fixed.
Thanks for replay,
2) and 3) Synthmaster Player for example doesn't receives midi from Animoog via AB3 - Animoog/midi source + Synthmaster Player/midi destination = silence when Animoog is played and about half of the apps I have connected to Anomoog this way doesn't receive midi for midi source (Animoog) via AB3. I understand that this is mostly issue with third party developers, but apparently for some reason they mark apps as AB3 compatible, but in fact fail to meet the latest AB3 SDK requirements and this makes things very confusing as AB itself in app picker menu still offers/allows to load them even in fact they are not AB3 compatible.
Re #4:
Developer from Phasemaker here... I've just tried it on my iPad again, but it opens quickly and without a hitch over here. Could you please elaborate on your issue with Phasemaker?
I'm finding only a handful of apps don't receive midi in the midi recieiver list but there are a few e.g. DRC.
Phasemaker doesn't load in the midi receiver list for me either. But I guess I've always used the Audio unit so never spotted that.
@brambos try putting it in the midi page, not working here too.
You are in Audio section and this apparently works, but in midi section I cant even pick phasemaker from the list to load as midi destination. Perhaps there is a problem that midi and audio routing pages are working each on its own and not together. So one doesn't really knows what happens on other routing page.
Taking this into account perhaps it would be wise at some point to redesign routing in modular fashion - into something like this http://www.gigperformer.com/wp-content/uploads/2014/03/inset-design-150x150.jpg
Phasemaker has not been updated with AB3 MIDI yet, because the SDK is not yet available to developers. So its AB3 features are limited to what was also available in AB2; i.e. audio routing.
You can use it as an Audio Unit if you need more MIDI capabilities.
Ok then it is clear - it AB3 issue and while midi SDK is not available to developers - no one can create fully AB3 compatible apps, so AB3 is not ready in fact.
Don't want to speak for @Sebastian , but I don't think that is a fair assessment. Some key players on iOS have apparently had early access to the SDK to make sure AB3 could hit the ground running (I assume). But before a system like AB gets momentum it needs to be launched first. I don't see how the AB guys could launch Audiobus AND magically have all apps adopt every new feature from day 0.
Give it some time.
Please stop with the hyperbole. Multiple dozen developers already have the beta SDK, many apps are already live. Not every app supports every feature of Audibus 3, so that's not an indication of apps being compatible with it or Audiobus being 'ready'.
Yes, I absolutely understand this, however I don't think it is good practice to announce fully featured product, while only limited number of developers, can match requirements, so it would be better if midi part would be limited only for fully compatible apps for now.
I'm sorry for that, just feel confusing
If I'm not mistaken, if it's an IAA instrument app, it should load as a receiver. Most do ok without needing any ab3 update. I can see that Phasemaker IAA app is only listed as a generator in AUM. So I don't know why it appears in the midi receiver list in AB3.
That's exactly right. Only IAA instruments get automatically listed as MIDI receivers, because if they're just generators they can't receive midi by default. I recommend using AUX for phasemaker anyway - much more reliable and flexible.
Thanks for clarifications, but as I wrote - it is just very confusing when something doesn't work and you don't know why and user is expected to have deep knowledge of what can be connected to work and what can't
So is it safe to say use the apps by the 24 or so developers of the AB3 optimized apps in AB3 for now to avoid issues and frustration for people?
iOS is always confusing if you expect everything to work all the time. Try things. Use what works. If something doesn’t work, try a different way of connecting or using it and then possibly accepting that it’s not ready for this application. Knowing even a little about AB3 and what it’s trying to accomplish, see that it’s new and evolving. Be patient for more and more to work as it gets sorted and the list of compatible apps grows.
I think with Phasemaker I think perhaps it's a database error and perhaps has been listed as IAA instrument when it isn't. Generally speaking most of the apps in the receiver list do work as expected. Hopefully the SDK release is not too far so we can get more AB3 updates appearing.
Possibly. It's simply listed in the database as an AB 2.3.1 compatible app with an AU Extension. How that is translated inside AB3 I don't know.