You just mean that it displays the note range C1 to Eb6 right? It does for me as well (and in the demo from Ableton) so I’m assuming it’s expected behaviour. Did not bother me but I can understand that it is annoying for some.
Yeah, it is still displaying when you play recorded clips also, so your screen gets overlapped everytime when trying to automate or edit stuff when transport runs. Checked with other max devices: expressive chords is the only one doing this and it really serves no purpose. So hoping this get fixed.
2 Likes
Hmm I don’t think I had that issue unless you are playing a clip with normal note information instead of the note info from chord device?
I haven’t even tried it yet, so can’t tell you whether it’s useful or not 
but, It probably is, if anything it’ll be a fun toy to play with, idk 
I’m arguing about the meaning of words
1 Like
Have you filed in a bug report on Centercode? Clearly the design team & developers didn’t think it was an issue, so they have to be made aware 
Anyone have an idea about CPU usage difference from 12.1?
Both in general, and specifically the new Autofilter compared with legacy?
I’d be replacing around 100 legacy Autofilters with approx 60 new ones (because home-made DJ filters used 2 Autofilters).
I’m a bit scared to update unless CPU is roughly the same!
But you can still use the legacy auto filter if you so choose?
Of course, that’s why I said in general , too.
I’d like to change to the new Autofilter, especially to reclaim one MIDI CC per filter, but that’ll be a big job I’ll do at some point.
But if it’s a big CPU difference, I prob wont bother updating, not needing the other features… plus I value stability.
But if it saves me CPU by changing to the new filters… then I definitely want to.
So I kind of need to know before I change anything!
If some kind soul could just duplicate many filters (with a sound running thru), then compare new to old…
How can one compare (the “in general” part) if the installation overwrites the old? Only someone in your position, before upgrading, could theoretically create a test, upgrade and then compare the results
Okey then I understand!
I just did a test on an Mac M1 max, 100 instances on the default setting with some added low pass cutoff
• Legacy auto filters run around 16% cpu
• The new auto filters run around 55% cpu
• The new auto filters in DJ mode run around 58% cpu
2 Likes
there is a separate folder now called Legacy effects, you can use the old effects whenever you want. The new autofilter also has a “high quality” option, so oversampling, I guess it can consume much more resources than the old filter
1 Like
When the expressive chord device is on a track, it does this when playing chords or playing a clip. So all the time, basically.
Will do, cheers.
2 Likes
Thanks to the gods of code for this beautiful functionality 
1 Like
That doesn’t sound right.
Are you sure you’re doing like-for-like comparison, i.e. using the exact same features on both?
Yes I loaded them up, default setting, turned the cutoff down a bit. No high quality setting or drive or anything like that
2 Likes
Thank you so much!
Pretty much what I expected tbh, as it’s a more complicated filter.
So 2 legacy as a DJ filter = 32%, new DJ filter = 58%, won’t be upgrading yet then!
Much appreciated for doing that, saved me a lot of time installing and uninstalling etc. Cheers!
1 Like
No problem!
Did another test just to confirm, with legacy filter high + low cut pairs (200 in total) and get around 33%
1 Like
Aortan’s stress test used 100 x Auto Filter devices, not 1. You won’t see anywhere near those CPU results in normal use.
So, for your example, my results on a 2018 intel mac are:
2x legacy as DJ filter = 5%, 1x new DJ filter = 5%
2 Likes
I’m having a ton of fun with expressive chords tbh. I’ve made a little setup where I record different voicings (triads, 7th, whatever) in different modes into midi clips generating my own 48 ‘chord packs’. I can then play around with MPE with all the inversions, strums etc. Lots of fun
6 Likes
I’m probably not the best example of normal use tbh… my main Mac runs a project for live jamming, has over 700 tracks currently.
I think around 94 Autofilters (many as DJ filter pairs).
Main Mac is an M4 Pro, still have to carefully manage CPU usage as there’s a lot of other stuff going on besides the filters!
1 Like