Lush 2 behaviours in Logic Pro
Posted: Mon Jun 23, 2025 9:40 am
Greets on the board,
Just completed a little detanglement running Lush2 as AU in Logic and thought to share this in case of others having similar issues.
Early on when starting out with Lush 2 I must have stored an AU default preset in the AU library not realising that that Multicore Support was turned on. This meant that more recently - after learning from Sebastian that I needed Multicore Support defeated on my machine - I could no longer store the synth setup. For some reason MCS would always revert to being on.
Result: CPU was spiking like crazy on a silicon M2, not good.
As soon as I deleted the AU default preset I was able to save the Lush2 setup and have it stay saved.
Just completed a little detanglement running Lush2 as AU in Logic and thought to share this in case of others having similar issues.
Early on when starting out with Lush 2 I must have stored an AU default preset in the AU library not realising that that Multicore Support was turned on. This meant that more recently - after learning from Sebastian that I needed Multicore Support defeated on my machine - I could no longer store the synth setup. For some reason MCS would always revert to being on.
Result: CPU was spiking like crazy on a silicon M2, not good.
As soon as I deleted the AU default preset I was able to save the Lush2 setup and have it stay saved.