Ableton Forum

…first and mostly only advice: set ableton‘s buffer size to 128…or even 64 samples…under ableton preferences - audio…

...afaik the advice is you should avoid mixing different formats of one single plugin...whereas there shouldn't be problem if you have chosen different formats of different plugins...regarding stability: i avoid using vst3 plugins since i had some problems with this format in the past...

@sqlmusic: i have the exact same setup like you (m1 pro with monterey) and the performance is absolutely awesome...have you set the buffer size to 128 samples?...

...ah...i reckon i understand your problem now: you don't have a scale selected on your bass and therefore switching to the bass-clip changes the "overall scale" to "nothing"....but why don't you have a scale selected on your bass track?...you could also put a scale device on this track and when you ...

...isn't it a "global scale" when one scale (that you can select from push or from the transport bar) transmits to all tracks with a scale device on it that has scale awareness active?...but yes...maybe the confusion is because of the naming...

"THAT SAID :
M4L API allows us to set the scale and the root note. So, I guess someone (me ?) could write a device that selects a given scale when you select a given track. Would it work for you ?"

...i think this is possible with this device: https://www.soundmanufacture.net/devices/scaleomat ...

...i just tested it again and imo there is a "global scale"...when you insert the scale-device on a track and active scale awareness on it it follows the scale that you select with your push respectively with "global scale" on the status bar...even recorded chords change when you switch e.g. from ...

…what is not clear to me: do you use ableton‘s „scale“ device on the tracks?…and if so…are these set to have scale awereness?…

...i have the same computer (m1 pro) and i run into kinda this issue when i have the plugin window (respectively more than one instance) of "duck" open....i found out that this draws a lot of gpu (!) power that makes live behave sluggish...so maybe next time this happens to you check your gpu with ...

…when ni is involved you can bet the solution to a problem is on their side…

…yep…ni traditionally doesnˋt care about anything…like…they‘re always the last when it comes to compatibily updates…so sad…

...just a thought...: i have a similar behaviour when i open the plugin window of the vst "duck"...i found out that "duck" uses a lot of gpu resources so having 3 or 4 instances open could bring my m1pro's gpu to the knees...open apple's "activity monitor" when the lag happens and look for the gpu ...

...they also say push 3 sounds more analog than push 2...: https://www.youtube.com/watch?v=tT1w9p_O17s

...unfortunately no midi only version...i don't have a need for standalone but i like the modular approach though...

...what is the "that" in your question?...