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 Version Compliance Devil's Advocate
I've wondered this for a good while.
Let's say you're an app developer and have created a few apps over the last several years. Your first app came out, worked great, but many of the users were demanding it be compliant with audiobus. Even though you've already made the bulk of your profit off this app, you cave and recode for audiobus compliance.
Things are all swell again, and you're not getting all those emails, twitter, facebook messages demanding audiobus.
Then, Audiobus2 comes out. Your app no longer works with audiobus. You've already moved onto something else, you're not really making much off that original app anymore, but the users are now screaming that your app is no longer audiobus compliant and start bombarding you with messages again, and writing scathing reviews in the itunes store and saying the app is dead and abandoned.
So, you find the time eventually, and update it again so that it works with Audiobus2.
Now, Audiobus3 is about to come out. Will all these AudioBus2 compliant apps need to once again updated to work with Audiobus3? And if you're a dev, with your past experiences with keeping your app Audiobus compliant... are you going to be so keen to make your new app you're working on Audiobus compliant at all?
Comments
If I recall correctly AB2 apps will continue to work in AB2 and will work in AB3 ( a whole new App) but without the NEW features unless they are updated.
In fairness it was Apple who broke AB1 (and Jack) when they introduced IAA.
I think developers will follow the money, if AB3 is in demand when they code their new app they will include it especially if the new features are as compelling as we are expecting.
Do you know if new AB3 compliant apps or updated apps to AB3 will still be compliant with AB2?
That's a good question that I don't recall having been answered, I would assume so or there's going to be a lot of unhappy punters.
One for @Sebastian methinks.
The point of the question is... if you're a dev and have to sweat whether or not your app will still work after each of Apple's iOS updates... and if you have to ALSO hope that your app still works after Audiobus updates... are you less likely to add the extra headache of making your app AudioBus compliant? And, does this go for an app's IAA compliance as well?
Just asking the question because I've been wondering why some devs create spectacularly awesome and unique apps, but fail to add AB or IAA or Audioshare?
Maybe they don't want the extra potential update/compliance hassles?
This will always be a 'problem' as there is no way to 'update' the SDK inside other developers apps automatically similar to how a 'linked libraries & frameworks' work.
Imagine if AB was able to deploy a 'framework' on system-level to which other apps could link to, this would make updating pretty smooth. Update AudioBus app and all apps that depend on the frameworks would get the new updated version the moment AudioBus app gets installed...
Personally I'm more and more using IAA-Instrument/Generator apps and AU-X directly with my hosts of choice (Cubasis and AUM).
For me to even consider getting a new 'music app' it has to at least include IAA Support(Generator or Instrument) or standard 'Open In...' for export so the created content can be used with other apps. AudioBus is a 'bonus'.
Even with my current 'scenario' I will get AB3 to show my support even if it takes some time to fully utilise it.
Audiobus is shockingly easy to implement; takes one day if you've never done it. Less if it's your nth time. IAA was a struggle, and I'm currently fighting with AU.
@Michael has it all figured out, don't worry. Devs who can't sort out a simple Audiobus integration probably don't even try because they don't make enough money.
I've also wondered why someone couldn't have made an app that you could point at the output of a non-AB/IAA/AudioShare-compliant app... then redirect the output into an AB/IAA/Audioshare-compliant stream?
Sort of an liaison or bridge?
Because if someone could hijack the audio output of any old app then they wouldn't have needed to invent audiobus in the 1st place.
Just imagine if you could hijack Spotify for example and then record directly in pure digital quality.
AB3 IS backwards compatible with AB2 apps according to @Sebastian
https://forum.audiob.us/discussion/14883/lets-talk-about-audiobus-3/p1
So disappointing, I don't understand why Frederik Hart didn't just ask warner bros to reference him, or state that the wall mural was based on his work. Instead of demanding it be removed. It's not like there haven't been similar artworks before this. There are many similar paintings with this theme. If I was him I would have been proud. Man I am pretty sure I have seen similar marble used in an office before. Better call the tilers and let them know of the blatant forgery! ..... apart from a few people stuck in a wall, and a few rocks they actually look completely different.I prefer the devils advocate version over the original too.... Maybe he was jealous.
i'm really liking these random eruptions of dislocated thought suddenly appearing on the forum, its like a ouija board channeling millenial netflix users
I couldn't figure out what was going on, but you've explained it clearly...thanks!