Ian Dicke

Sorry this is a somewhat vague post, but has anyone experienced worse performance with their M4L devices on an Apple M1 machine compared with Intel?

I have a rather complex 4-track MIDI sequencer (Polymath, part of the SEEDS collection, www.novelmusic.org/seeds) that works very well on my Intel iMac (at 128 buffer size) that now spikes the CPU on a MBP M1 Max machine with 64 GB of RAM.

EDIT: It actually doesn't spike the CPU meter, but the individual performance meter for the track goes high and it is accompanied by an audible click.

1) Does anyone else notice poorer performance under M1?

Sorry this is a somewhat vague post, but has anyone experienced worse performance with their M4L devices on an Apple M1 machine compared with Intel? 

I have a rather complex 4-track MIDI sequencer (Polymath, part of the SEEDS collection, www.novelmusic.org/seeds) that works very well on my Intel iMac (at 128 buffer size) that now spikes the CPU on a MBP M1 Max machine with 64 GB of RAM. 

EDIT: It actually doesn't spike the CPU meter, but the individual performance meter for the track goes high and it is accompanied by an audible click. 

Sorry this is a somewhat vague post, but has anyone experienced worse performance with their M4L devices on an Apple M1 machine compared wit

strange-performance-issues-with-m4l-devices-on-m1-apple-silicon

Are you running things under Rosetta or M1 native?

Update: I tried running the Live 11.1.b12 in Rosetta and I still have the same poor performance with Polymath. Now I am really confused.

Another update: Tried running Live 11.0.12 (which only runs in Rosetta) with Max 8.2.1 (M1 native support)...and it works perfectly fine.

So, I am starting to think this is an issue with the way Live runs Max in its M1 Beta and not a Max issue.

Another update: Tried running Live 11.0.12 (which only runs in Rosetta) with Max 8.2.1 (M1 native support)...and it works perfectly fine. 

So, I am starting to think this is an issue with the way Live runs Max in its M1 Beta and not a Max issue. 

I've got a M4L sequencer that is also experiencing difficulty only on M1 macs ... all my debugging has been futile so far, and I've come to a similar conclusion that it's most likely an issue with how Live runs Max on M1 macs. So far, the bug I'm dealing with only appears when Live's Loop Switch is active - otherwise it seems to run alright

Strange that the loop switch is causing issues!

Strange Performance Issues with M4L Devices on M1 Apple Silicon?