Its good.How's the CPU usage looking? I bought cycles, but I get into serious CPU issues using a single patch on my 2013 mac pro. Hopefully will be upgrading to the M chips when they sort ram limitations out, but until then...
You can go crazy with it if you start layering up for example, a fast arpeggiator with 4 voice harmonisation and long envelopes and then start modulating the spatial perspective and multiple dsp effects etc, but the general baseline use is way less cpu intensive than Cycles.
Cycles has been weird as whilst it was always going to be cpu intensive with its engine being based on realtime time stretching and polyphonic granular synthesis it seems to be really unpredictable as to how well it runs on different computers.
We have users that run it pretty well on Macbook Pro 2012 (some of our vids were made with one of those in fact) and then others with maxed out 2020 Mac Pros that have issues. We've looked into ourselves and with NI but cant seem to understand why. Some of the variables that seem to effect things are DAW (Logic's poor multithreading not helping for example), audio buffer size and sample rate, but even then results arent entirely consistent.
Havent heard from anyone how it runs on the M1s, would be interesting to know...