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.
Sorry to say this but the emperor (currently) has no clothes.
I feel like the child in Hans Christian Andersen's story but it seems to me that as it stands AB3 is inferior to AB2 in many ways.
Let me explain my reasons before you have conniptions.
Obvious items which Sebastian has already said they will fix include not supporting AB remote or Bluetooth midi.
Despite claiming to be a solution to all the disparate interpretations of how to implement Apples Core midi AB3 itself doesn't specify how developers need to implement midi to get the AB3 badge. So that for example we have Chordion which is "AB3 optimised" but whose midi output doesn't work in AB3 and Music Sudio which only has one midi input and since AB3 doesn't support midi channels this means all midi gets recorded to one track.
Because AB3 shuts off core midi I can't use apps like changeling at the same time in the way that I can with AB2 or any other midi app that hasn't been "AB3 optimised" or even all the ones that say they have.
Hopefully all the 3rd party developers will get on board with implementing AB3 midi and that there won't be too long a delay in implementing AB3 midi for Soundprism pro, otherwise the emperor is going to catch a cold.
Comments
Yep, i Hope for the sdk Release...
But, for now, you have right.
How many apps were compatible with the very first audiobus upon release? Isn't this new midi stuff the first of its kind on iOS?
You can still use core midi apps just like before - just don't load the apps that you want to use the old way on the MIDI page. Load them on the audio page as inputs. For everything I've tried, it works just as it did before.
early days
Thanks for that. That works (not sure it's supposed to though) as I had emailed both Sebastian and Xewton about midi and neither of them mentioned it.
The School for Scandal
Could just be the context of the email being misunderstood. We now have different "input" slots that mean totally different things. It should definitely be clarified though because I think a lot of people may be feeling the same way you did - that AB3 has actually taken away functionality they used and not replaced it yet. So far I'm not seeing that as the case, but I can see how it's easy to think so.
Exactly, all the old functionality works still... Except remote.
A bit of force majeur in the nicest possible way by AB3 was always going to be required. Hats off to him for taking the reigns. There's no need for anyone to implement state saving but they are doing it as they will get more customers that way. Same thing will happen with AB3 midi. Patience. And in the meantime we all know we are supporting a developer who is (almost) single handedly propelling iOS into new worlds of wonder.
I would like it all to work straight off the bat too but how on earth would that be possible.
There's no need for anyone to implement state saving but they are doing it as they will get more customers that way. Same thing will happen with AB3 midi. Patience.
>
well conversely to your assertion ,
my initial shock at the emperor's danglies was that usually strict AB control were actually allowing new "AB3 Optimised " labelling of still Non-StateSave apps , which seemed a contradiction & a practical loophole in their " it just works " ethos .
So if, as I understand , AB3 Optimised means the midi config of app is " statesaveable" ,
it seems pretty silly that the main project content of the app isnt ,( necessarily ) .
So presumably loading up your penultimate project X will have the correct midi settings for apps such as Patterning and even yes Loopy !!! , but their project content will play Y from their last session , as default , because they arent StateSave compatible .
Please correct me if I have this wrong .
Whilst Sebastian replied to my critique of this that they couldn't force devs to implement SS , my point is that " AB3 Optimised " status could insist on SS as a requirement .
@BiancaNeve I dont yet have AB3 , I'm confused to read AB3 doesnt support midichannels . How are multichannel apps meant work both for I/O ?
I was given to believe the MidiFlow apps would allow even more routing flexibility .
while I'm here , could anyone confirm or deny the topic of Multiple Audio Out support for multi i/o audio interfaces . I asked on FB & only answer I got was " not supported " .
Really ?
This is what I've been doing with Genome, loading it on the audio side, (can use the Genome onboard instruments that way too. Modstep probably will work the same way...) this way you still get the control panel benefit in all the involved apps
Funnily enough AB3 sent me back to both AUM and AB2, the above Genome thing worked in AB2 just the same way, upside of using AB3 was playing with some midi toys that seem to work even though they're not in the chain - midiLFOs does and maybe the midiflow stuff does too...
to me the AB3 experience is a wait-and-see, I'm hoping my fav midi sequencers adopt the new standard...till then existing tech is already damn nice, and as I said AB3 lured me out of the all-in-one iSequence, Caustic, FLSM, PixiTracker/SunVox funtimes back into the realm of the multiple spinning plates, albeit in AB2, AUM, and slowly into AB3
seem to have problems posting , trying again
@adfa said:
There's no need for anyone to implement state saving but they are doing it as they will get more customers that way. Same thing will happen with AB3 midi. Patience.
well conversely to your assertion ,
my initial shock at the emperor's danglies was that usually strict AB control were actually allowing new "AB3 Optimised " labelling of still Non-StateSave apps , which seemed a contradiction & a practical loophole in their " it just works " ethos .
So if, as I understand , AB3 Optimised means the midi config of app is " statesaveable" ,
it seems pretty silly that the main project content of the app isnt ,( necessarily ) .
So presumably loading up your penultimate project X will have the correct midi settings for apps such as Patterning and even yes Loopy !!! , but their project content will play Y from their last session , as default , because they arent StateSave compatible .
Please correct me if I have this wrong .
Whilst Sebastian replied to my critique of this that they couldn't force devs to implement SS , my point is that " AB3 Optimised " status could insist on SS as a requirement .
@BiancaNeve I dont yet have AB3 , I'm confused to read AB3 doesnt support midichannels . How are multichannel apps meant work both for I/O ?
I was given to believe the MidiFlow apps would allow even more routing flexibility .
while I'm here , could anyone confirm or deny the topic of Multiple Audio Out support for multi i/o audio interfaces . I asked on FB & only answer I got was " not supported " .
Really ?
Quote
Very well stated. Big, important missions require tenacity and patience. If not the AB crew, then who?
The intriguing thing really is the modularity of all the new and possible midi toys
Outfitted in a jaunty thong and tank top this Emporer is ready for a truly memorable summer.
Gotta say... I agree. The part about being the solution to all the MIDI problems in iOS... i don't really see it... unless there's a general consensus about what means being fully compatible with audiobus 3 Issues will remain.
Still...I hope for the best.
MIDI is hard. This is why they haven't released the public beta yet, I assume. There are too many use cases than a simple beta test can account for. For the vast majority of users, though, this is going to be aces (once enough apps come on board). Early days.
I think it's important to remember that Audiobus has always relied upon developers adding Audiobus support to their apps for the benefit of their users and the makers of Audiobus try to make adding Audiobus support to their apps as easy as possible. As part of the development process, the Audiobus team had to work with a small group of developers to work out and refine how to integrate apps with the new functionality of Audiobus 3.
As usual developers have different levels of Audiobus support they can provide.
It is very early days for Audiobus 3 and other developers outside of the Audiobus 3 development collaboration haven't had time to implement Audiobus 3 support yet. I think the Audiobus team has had a history of listening to what users have had to say. As Audiobus 3 continues to be refined and updated from its initial release, I'm sure they'll continue to listen and incorporate some of our suggestions into Audiobus 3.
While the Emperor may not have many new clothes and some of the older ones need to be altered to fit, this should not be surprising to people who have used iOS music creation apps for any length of time. New standards and updates don't happen overnight and there is not always universal adoption of them either.
The story of chicken little seems more appropriate than the emperor's new clothes as app users may benefit from a more realistic expectation of how iOS development works in the real world rather than an idealized version of how they think it should work.
Audiobus 1 launched with 12 compatible apps. Twelve.
Audiobus 3 today, four days after launch, is compatible with about 900 apps for it's audio system, 17 midi Controllers apps, 9 Midi Filters, hundreds of Midi receivers, about 3 dozen aux apps and all class compatible Midi hardware.
We have not releasd a public SDK, which will happen in the next days, and I am getting multiple requests for it every day.
Our work takes time. I highly recommend encouraging third party developers to get behind the new system and letting everyone do their job.
We could easily make Audiobus compatible with Core Midi from existing apps, which would make us compatible with everything... on paper. But that could potentially lead to double connections, misconfigurations and confusion, which is what we've worked on for years to avoid.
If you like Audiobus, this forum, mobile music becoming easier to use and more reliable, please contact third party developers whose apps you want to be compatible with the new Midi system and ask them politely to implement the Audiobus Midi SDK.
Thank you
PS: I will close/sink this thread in case it turns into a bigger source for drama (than it already is). Please keep it friendly.
In other words, Audiobus was always meant to be the skin and bones that provide the frame for hanging a wardrobe full of music apps upon. Of course the new shape demands a new wardrobe of clothes that fit. It will take time for developers to catch up.
I'm glad for the progress, big thanks to the Audiobus team.
I find that I'm so into it that I keep checking AppStore for AB3 updates in all the possible and various apps.
It wasn't all that long ago I was checking the AppStore for apps that implemented Sonoma audio copy..
+1 Well put.
Us too (not the thong part so much).
I, for one, welcome our Audiobus overloards. ;-)
Yes, constructing the Space Knight took time.
And building an infrastructure is never all that glamorous, but it makes all the other cool things possible!
I think if the SDK was released, many will implement it, I wish the audio bus team success and trust completely on it.
If I had to buy AB3 just to participate in this forum I probably would just to show support for what has gone before.
I'm going to have fun with what is and watch my app updates eagerly.