New version submitted and approved - 1.154

[CEIsar]

No,i even didn't try it it with audio on.Just slowly moving the mixer with a finger to the left/right side and it behaves like having just 10-15 frames.The CPU meter shows"0"while doing this (on an enpty project),so audio might be ok (i'll report later after further testing) but it's definitely wrong.Scrolling left/right in the mixer was always smooth,no matter what device,even on an old ipad 2 .And having such a Dia show makes me sick when looking on it

[Rim]

That's on purpose. In order to work around the iOS bug on the Air 2, I was forced to add a small delay to the scrollview. This fixed the CPU issues. As a result, the mixer and the editor are a little less responsive on an Air 2, but that's a good tradeoff for not having those CPU issues. Hopefully Apple will address this in a future update so I can remove this workaround.

Again, this only affects the iPad Air 2. No other models use this temporary workaround, as the iOS bug doesn't seem to affect other models.

Rim

[CEIsar]

ah well...it's really a neverending story with Aurias GUI.

It's not only"a little less responsive",it's definitely worse for my taste.Just in case apple doesn't fix it:Will the new GUI change this back to normal?

[Rim]

The new GUI is the same in this respect. It's any app that uses a scrollview control and works with real time audio. We're really at the mercy of Apple at this point.

Rim

[Washboy]

The new GUI is the same in this respect. It's any app that uses a scrollview control and works with real time audio. We're really at the mercy of Apple at this point.

Rim

Would it affect GarageBand? If so, maybe Apple will get on the case more promptly than otherwise

[Rim]

In theory, it should affect all audio apps on an iPad Air 2 which use a UIScrollview. Not sure if they use one. But they don't have a CPU meter, so it's hard to know. And it's difficult to really load down an app like Garage band with a lot of CPU intensive effects.

[CEIsar]

So,what magic is cubasis doing then?Scrolling the editor or mixer is smooth as butter and doesn't do anything to the CPU meter.

[theconnactic]

CEisar, I think it's the same case of Garageband: Cubasis' effects palette doesn't begin to be as CPU-intensive as Auria's.
My two cents.

[Rim]

I don't know what Cubasis uses for their scrolling, but it's probably something custom. You can usually tell if it's a UIScrollview because of the way it bounces when it hits the end, and in the way it decelerates. Think of the way the iOS mail application works - that's a standard scrollview.

Rim

[Washboy]

Sorry for having butted in on this. I'm still sitting on the fence about upgrading to an Air2 due to these sorts of issue. I'm trying to get my head around the significance of this particular one.

Does it only occur if the project is already CPU intensive or does it apply regardless? If the latter, then why doesn't it affect GarageBand? I notice that GarageBand must be using a UIScrollview (according to your "tell"s, @Rim).

<confused>

[Rim]

I don't really know. Every app is a black box to other developers, and no one knows much about this iOS bug. The issue only affects iPad Air 2, and it adds 10-20% to the CPU usage at random times during movement of a scrollview. So if you're only using 50%, you probably won't notice it, but if you're near 70% or more, it'll result in a CPU overflow without my workaround.

Rim

[Washboy]

Thanks for the clarification, Rim. I'm slightly reassured by the implication that it's solely an iOS issue and not one of those unfixable hardware-related ones (such as got the iPad3 labeled a lemon). That means there's at least a chance it'll get fixed

[Rim]

I didn't mean to suggest that, sorry. I really have no idea whether it's a hardware or software issue. I've got requests in to Apple to help sort this out. In the mean time, I've implemented a better workaround that's more robust (uses a larger delay), and also smarter. It'll only kick in when the CPU is over 40% and the transport is playing. Should help minimize the choppiness.

Thanks,
Rim

[mtingle]

in my testing before I upgraded I could only get the CPU bug in the mixer screen and not the edit window indicating it may only be related to that window.

cpu load 60%

[CEIsar]

CEisar, I think it's the same case of Garageband: Cubasis' effects palette doesn't begin to be as CPU-intensive as Auria's.
My two cents.

the behavior doesn't change even with heavy IAAs loaded and Cubasis has a CPU meter that you can observe while scrolling.

edit:Cubasis scrolling behaves dfferent than the standard apple thing (no"bounce back"when reaching the end of the mixer etc.) so it's like Rim said,they seem to use some custom stuff.