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.
IAA issues in Cubasis 3
![[Deleted User]](https://images.v-cdn.net/banned_large.png)
The user and all related content has been deleted.
Comments
Then lets us just hope that @LFS and his team brings us a more competent sampler (hint start with Cubase Sampler Track) so we don't have to rely on external apps for slicing and dicing our samples.
Freezing from BeatHawk has always worked fine for me in Cubasis using both 44.1k& 48k sample rates.
Sometimes I feel really lucky that I've not rushed into getting a new iPad...
...the kind of issues plaguing the newer devices would have driven be nuts beyond recovery...
Hi @ehehehe,
Hope you're well!
Gave BeatHawk a short check which worked as expected (see video example, link expires in one week). Environment: iPad Pro 12.9" 1st Gen with iOS 14.4, Cubasis 3.2.1, BeathHawk loaded via IAA MIDI.
Would suggest to load BeatHawk via AU though.
Apple discontinued IAA quite a while ago, and the AU format brings many more advantages in use.
Hope that helps!
Best wishes,
Lars
@LFS : Apple deprecated IAA. It did not discontinue it. There is a huge difference between deprecating and discontinuing. When one has a choice between using and AU and IAA version of the same plug-in/app, AU is preferable BUT there are still important stable IAA apps not available as AU.
🙄
Until Apple actually announces they will remove IAA from iOS/iPadOS we’ll be stuck with IAA based apps. Once IAA is removed we’ll see what happens.
It could even go that far that apps relying on deprecated technologies will be removed from the AppStore completely or dissalowed new sales. As long as IAA is there there’s no real rush for developers to update old apps especially when it has to be done for ’free’ and this could be hard if the app has not sold any new copies for the past few years.
As an exaple, how many copies has Nave sold in the last few years?
Guess we’ll know more after WWDC’21.
Hi @espiegel123,
Thanks for your message.
Inter-App Audio comes with huge limitations, plus Apple dropped supporting the format.
It is strongly suggested to let app vendors who support IAA only, know about the request for an AU version.
Best wishes,
Lars
Sorry to pushback, but what you are saying is not quite right. I sympathize with how annoying IAA is to deal with from a programmer's perspective and that it is a technology that won't move forward. Deprecation is not the same as not supporting. Apple has not dropped support for it yet. Since the deprecation was announced, Apple has fixed a number of bugs related to IAA -- and in some cases IAA has fared better in some 14.x releases than AUv3. They have developers who make sure that it continues to work and doesn't break.
I think it is important for developers to be clear about what deprecation is and isn't and to not be -- however unintentionally -- misleading. IAA is a technology that IS supported but will not receive new features. It is a technology that Apple would prefer for people to replace. It will at some unknown point in the future be removed. It might disappear in iOS 15 (though that would surprise me) or it might be here for another decade.
It is one thing to decide that you won't support IAA before releasing an app (which could be a reasonable decision for a new app) -- there are plenty of apps that have made the decision not to support it. But, I think it is also important that if a developer has an app that supports IAA (such as Steinberg's Cubasis) that they actually support it.
Another hassle is supporting multiple iOS/iPadOS versions especially if some of the versions require version specific work-arounds that have been 'fixed' by an iOS/iPadOS update.
A good indication about IAA is Apple's very own GarageBand, when GarageBand drops IAA support IAA is officially 'done'.
Until that happens we're stuck with IAA...
I started another thread re Lumbeats apps not working well as IAA with Cubasis3. Anyone else experiencing similar issues? Luis Martinez has got to go Au at some point.... doesn’t he?
How do you define "support"? And where have you read that Apple has not dropped support for IAA yet? Do you mean support as in "we will continue to fix it", or "it will continue to work until it doesn't", or?
Do you have a source for the assertion highlighted in bold? I can't find any. Nor can I find any statement regarding any level of support or a definition of what that means.
I hope you don't mind me asking this. I always feel better when I see official word on something before I go out on a limb and repeat it.
When Apple drops support, they pull it from the OS and the functionality stops working. They will announce that they aren't supporting it when they pull support. One doesn't need them to issue a statement that they are supporting it -- they will tell us when it isn't supported.
You might argue that it isn't very actively supported and I wouldn't quibble.
For APIs like IAA, when new versions of the OS happen it actually requires some effort to keep the functionality working. Some work is needed with major OS versions to keep APIs working and things compiling without breaking.
The proof is two fold: it keeps working (which wouldn't happen without at least some resources), and they have fixed a few IAA related bugs since it was deprecated. In iOS 13 and iOS 14.
I am not suggesting that they are putting a lot into keeping it running but there is more than no effort.
Apple has never said that they stopped supporting it. I think there is a lot of confusion about deprecation -- and people don't realize that Apple has sometimes kept deprecated APIs running for years and years (well over 10 years for some system calls that were deprecated in the aughts and not removed until Catalina).
Having many issues with recording from internally routed IAA apps. It looks like only apps that have IAA bar with record button are able to record audio into Cubasis 3. If I hit record in Cubasis and switch to an external app window and generate sound, no audio is routed back into Cubasis. After stopping recording sequencer area where recorded audio should be is looping a record icon instead, endlessly...
Cubasis still has issues. On another instance today it crashed after stopping recording from one of the micro machines, when reaching the end of selection. Only one audio track was present beside the micro machine, absolutely no audio units, only basic stuff loaded.