Ableton Forum

I heard back from support (quite a while ago, I just never got an email about it):

Point taken, reproduced and forwarded to the Max for Live Team for potential improvements.

Context from their input:
What might look as a simple MIDI processor, can easily be much more under the hood. The ...

I did file a support request, I haven't heard back yet. I'll update here when I do

Certainly not, the meter indicates CPU spikes over 100% when Expressive Chords is the only device in the entire project. When I add any instrument after it I get clicks and dropouts, and when I remove EC and play the chord manually, playback is smooth and CPU is nominal.

I've filed a bug report ...

> adding Expressive Chords (with no instrument) and plaiyng with this was not caused increasing cpu load at all

Interesting, thank you for taking a look. Did you specifically try holding down a note that triggers a chord? That's when my CPU goes haywire. I also wonder if your CPU meter is set to ...

Yeah it's at small buffers (64/32) that it becomes straight up unusable on a Macbook M1 Max, which just doesn't seem right for a device whose only inputs and outputs are MIDI data.

How does it look for you at those buffer sizes?

Ah I noticed that opening the editor introduces 2048 samples of latency this must account for the drop in CPU usage.

It's pretty surprising (and disappointing) that M4L MIDI effects that don't even process or generate sound would take up so much CPU as to be unusable at buffer sizes that native ...

The plot thickens. Moving over to the M4L forum viewtopic.php?p=1836204#p1836204

Following up on a previous thread https://forum.ableton.com/viewtopic.php?t=253103 ...

I've got a new (to me) MacBook M1 Max with 64GB ram, a fresh install of Sequoia and Live 12.3.2 and I've noticed that at least some Max4Live devices CPU usage increases dramatically as the buffer size is ...

Ope, never mind, I forgot to set my buffer back to 64 samples.

So it seems like a buffer size issue - for Expressive Chords and Melodic Steps at least, CPU usage goes up dramatically as I change the buffer size from 256 to 128 to 64. Native devices (I tried Drift & Meld) don't seem to suffer from ...

I had issues with (at least some) M4L devices using absurd amounts of CPU - see viewtopic.php?t=253103

Edit: never mind, see follow up in that thread

Update: it's a Tahoe thing.

I noticed a few other M4L devices causing crazy CPU usage as well (Melodic Steps for example).

I downgraded to Live 12.2, which is what I was running on my old machine without issue - no luck.

I downgraded from Tahoe to Sequoia (that was an adventure) and everything ...

I downloaded it from within the Live browser, it's the version with the Learn function so I'd assume it's the latest but not sure how I would verify?

I just got a MacBook M1 Max and installed the latest version of Ableton (12.3.2) and Expressive Chords is using a crazy amount of CPU.

A set with an instance of EC and nothing else (no instrument) hits 32% CPU when I hold down a note. As I hold down the note, CPU meter drops down to 2% over the ...

I see that with Push 3 it is possible to change the pitch of a note when editing a MIDI clip, something that I couldn't believe was missing when I bought my Push 2.

Is there any hope this functionality ever getting backported to Push 2? That alone would get me to upgrade to 12, if that's what it ...

Assuming you have Scale after Arpeggiator, I'm wondering what happens if you put Scale before Arpeggiator?