IPad Air 2 Ram?

[CEIsar]

This problem only shows up if you hit the roundabout 45% cpu mark on Air 2.Works fine before but i have always bigger projects (very often roundabout 20 tracks) with a lot of plugins open (Fabfilter,PSP,FXpansion...) and i'm always way over that mark.And getting this"low cpu"warnings like crazy then,especially in the mixer view.Sometimes i can scroll a bit left/right before it occurs,other times it even stops when i just look at the mixer (or a plugin window).

[Mucci]

iOS 8.1.3 is out. If the problem is within the iOs itself (as I guess Rim had mentioned somewhere) maybe this update will fix it. Anyone tried?

[levispeights]

So, did 8.1.3 fix this problem?

[Rim]

No, Apple still hasn't fixed the issue. They're still "investigating" the problem...

Rim

[CEIsar]

This is a very interesting video from Audiobus dev Michael regarding the scrollview bug and his solution to avoid the problem:

http://forum.audiob.us/discussion/7624/ ... lks#latest

[Rim]

Yes, I've talked with Michael about this last week. It's definitely related. Auria doesn't use Core Animation, but the workaround I already have in place uses the same trick he discovered.

Rim

[CEIsar]

Yes, I've talked with Michael about this last week. It's definitely related. Auria doesn't use Core Animation, but the workaround I already have in place uses the same trick he discovered.

Rim

Hi Rim,

with"a workarround already in place"you mean the"fix"that you had in version 1.154 but pulled again in the current version?

I'm glad to see this gets more and more attention,i just hope someday apple will wake up and realize that an Apple watch integration is not everything they should pay attention for

Here's comparison video with Gadget.It starts to heavy glitch with just EIGHT tracks running:

http://youtu.be/p9v8q9kKiXw

[Rim]

The fix I have in place right now is the best compromise I can find. I tried several workarounds, and this one strikes a good balance. The first workaround (in 1.154) was much too drastic, slowing the mixer and editor to a crawl. While it got rid of more of the CPU warnings, it made the screens very choppy and difficult to use.

Rim

[CEIsar]

I'm thankful for ANY improvements so it's great to read you could improve your workarround.Thanks!

[eustressor]

Yes, I've talked with Michael about this last week. It's definitely related. Auria doesn't use Core Animation, but the workaround I already have in place uses the same trick he discovered.

Great minds thinking alike? Pleased to hear the devs of my two most essential apps, Auria and Audiobus, have an open line of communication

[stevencirile]

Rim
Being. Fan of the most horsepower available when it comes to my audio rigs is it worth the upgrade from air to air 2 at this time in your honest opinion? With aurias current release. And for the forthcoming new pro version of auria
Thanks
Steven Cirile

[duncanm]

The fix I have in place right now is the best compromise I can find. I tried several workarounds, and this one strikes a good balance. The first workaround (in 1.154) was much too drastic, slowing the mixer and editor to a crawl. While it got rid of more of the CPU warnings, it made the screens very choppy and difficult to use.

Rim

Not currently a user, but pro is likely going to tip me over, but out of interest, as an air 2 user, because of this issue, are any gains seemingly made because of the increased ram and processor power basically lost? I mean, I'm not about to throw this thing out, but was thinking more about whether I should be expecting it to run umpteen instances of twin 2 or any other instruments played through iaa or...not so much?

[Rim]

More RAM and CPU horsepower always help when it comes to audio apps, and Auria is no exception. My goal is to make Auria Pro use no more RAM than Auria does now when using the existing feature set.

Rim

[duncanm]

Great, thanks for your reply.

[Rim]

I can't talk in detail about the iOS beta, but I will say that you're going to be very happy with the results we're seeing here!

Rim