Been using desktop Scaler2 for a bit, now trying out the iOS version on an iPad 8th gen (all iOS and apps mentioned are up to date)
I’ve set up a very basic session in AUM, with Scaler2 on an audio track, a basic piano on another audio track, and Atom2 Piano Roll on a MIDI track.
In scaler2 I have a single 4-chord progression set up, with no performance turned on. It’s left on the Pad screen. I use AUM to MIDI route Scaler to control the piano.
In Atom I have a single looped pattern set up that just plays the control notes (C3, D3 etc) that play the 4 chords in the Scaler chord sequence, and the Atom MIDI routes to Scaler.
I’m kind of assuming that this should make sense (similar logic to how I use Ableton midi tracks to control scaler in there). It works for a few loops But very quickly the DSP / CPU usage AUM reports hits 99%, 100%, MAX - and Scaler stops sending out MIDI to the piano. If I have saved the session and I reload it in AUM, it’s at MAX DSP and not working from the start and nothing fixes it except completely removing the Atom instance. But - AUM reports that it’s definitely Scaler2 that is using the 99%+ CPU.
Sorry if this is covered by something simple / RTFM, but I’ve been searching for an answer for a while, am I fundamentally wrong in using Atom to try control Scaler like this in AUM? Have I set up some kind of circular MIDI processing without realising? Any other ideas?
Note: similar thing happens if I set this up in Audiobus too; it happens with all the other variants of Scaler available in AUM (ScalerControl etc); it COULD be iPad gen8 is slow for present day, but it seems to do alright with a bunch of simultaneous samplers / Borderlands Granular etc in AUM…
Unfortunately not - I think I had that off to begin with but I double checked in an entirely new AUM session - this time as simple as I can make it just Scaler2 on one track using the internal Felt piano audio output, and Atom to drive the Pad chords/chord-sets. Audio detection definitely turned off!
This time I can isolate the behaviour: Atom correctly triggers the chords and chord-set changes the first time I hit play on Aum‘s transport; scaler plays sound correctly, CPU at 25% or so. If I hit pause on the transport, CPU hits max and there’s a buzzing sound from speakers /headphones. Nothing can fix that except a close of AUM etc.
MIDI Panic doesn’t help (in iOS, that’s tapping on the MIDI word top left, right? It produces a little pop-up saying MIDI Panic anyway) - CPU usage is unaffected, still at 98%-MAX; AUM still reports that is all taken by Scaler even when nothing is happening (no AUM transport etc)