Pro2 CPU overload message with screen touch

[Sparkle]

Reminiscent of previous Air2 graphics bug causing overload spikes ...

Playing with a four bar midi loop , only Animoog loaded , no fx on .
Dragging bottom right arrow of blue bar of highlighted midi loop to extend / reduce length .
CPU overload message & daw stops . Only 7-14% CPU , after 1 overload Max CPU read 344 %

Closing apps, reopening, new project = repeatable .

Air2 64GB IOS 8.4 buffer 512 ( Animoog buffer 512 )

[Rim]

There is no screen touch bug, that was fixed by Apple a while back in iOS8. It sounds like this is an Auria bug you've found. Are you able to get this to happen every time you do it? If so, can you send me the project, and tell me exactly what to do?

Thanks,
Rim

[Sparkle]

https://www.dropbox.com/s/rudu0uotk7qgo ... 2.prj?dl=0

loop drag overload ^^^ , just hold selected loop right end to extend / contract blue loop whilst loop plays.
I tried a new project , first with z3ta which seemed ok , but then when I loaded Animoog into same slot & started moving loop end backwards & forwards , it gave CPU overload message after 2 or 3 goes . Not moving too quickly .

Please confirm when downloaded so I can delete from dropbox .

[Rim]

Thanks, but I need the entire project folder, not just the prj file.

Rim

[Sparkle]

Remind me how to do that , is there any way without needing itunes /ifunbox ?
I'm away from my computer at mo ...

although the instructions I've given are simple enough , load animoog make a midi loop & start moving end of loop .
Nothing else .

[Sparkle]

https://www.dropbox.com/s/tdvigcwdd16ps ... 3.zip?dl=0

^^^^So I " save project to another app " =dropbox & have a zip with project folder I hope ?

This was a new project 3 . Also get an ocassional graphic glitch where loop content & grid disappears whilst moving end of loop . Please find photo :
https://www.dropbox.com/s/lrqh6nhqmuad9 ... h.PNG?dl=0

[Rim]

Thanks, that will work.

Rim

[Rim]

I've tested your project, and can't get this to happen here. My CPU usage stays around 50% here, no matter how many times I move the locator positions. I'm on iOS9 though, and I see you're on iOS8, so this might be an iOS 8 bug of some sort related to the CPU (maybe a leftover issue related to the scrollview bug).

Rim