i'm on Sonoma M3 Pro.

- in Logic 11 it causes an error, it doesn't finish opening and makes a loud unpleasant noise.

- in Live 12 it works VST3 and AU flawlessly.

- in Cubase 14, my main DAW, it only works in the native version...
BUT in Rosetta mode unfortunately it doesn't work, which is the way i use it so that plugins like those from Roland Cloud, ROLI, Splice, Output, etc. can work.

(hopefully they'll soon update those Roland plugins (and others) so they can be used natively on Apple M chips.)

 

I did your test with 8 notes "Ascension" patch for 4 bars in a loop, track armed on my MacBook Air M1 2020 in Reaper 7.16, VST3 version of the plugin at 44.1 kHz, 256 samples buffer size, internal speakers:

Average 8.6%, peak at about 11% when loop restarts.

I can play 4 of these tracks simultaneously showing about 60 to 80% activity on the 4 power cores of the M1 and nearly no activity on the efficiency cores.

When I try to add a 5th track, audio is crackling and unusable.

So it seems the plugin is single threaded and needs a power core to run although Reaper is able to use efficiency cores.

It's very CPU heavy, but the Ascension patch plays 7 sounds layered, multiplied by 32 notes sums up to 224 voicees.

Without having the tracks armed, I can get 7 tracks to play, that's 392 voices.

 

There is no Rosetta support as stated in the system requirements on Yamahas website:

[OS] : macOS 14.x, macOS 13.x
[Plugin format] : VST 3, AU v2
[CPU minimum] : Intel® Core™ i5 (mid 2017 or later) or Apple silicon (*2), AVX2 support is required for Intel processors (*3)
[Memory] : 8 GB RAM or more
[Storage] : 10 GB free space
[Display resolution] : 1000 × 640 display resolution at least (1440 × 870 recommended)
(*2) Not supported in Rosetta2
(*3) AVX2 support is required for Intel processors (Web site)

 

Yes Reaper is 7.27. Yes is also is playing a more than 4 / 8 bar loop.
The only difference is I have a quantum 2626 as my Audio interface. One is with it armed one is not armed for recording.

What CPU / Audio interface are you using?
Also what patch are you using? Mine is Natural.Women

 

Last edited: Nov 16, 2024 at 2:51 PM

Really no expert in this field, but probably having so much bigger cache results in something...

 

Some more numbers, I tested it on my "Gaming" PC, Ryzen 7 7800X3D (8 cores), 64 GB RAM 6000 MHz, Win 11, Reaper 7.22, 44.1 kHz, 256 samples buffer.

One track averages at around 0.16% in Reaper.

I can get 16 tracks armed to play continuously and 28 tracks unarmed, that's 1568 voices.

But this is far away from a real world scenario, because it peaks at 95% CPU when all notes start playing at once and goes down to only 5% CPU while the notes play.

 

Reaper caches everything that is playing. Unless you disable prerendering there is no way to know how much CPU it takes. The 95% is the building of the cache and the 5% the paying back the cache.

 

In Reaper, it's called "Anticipative FX processing", turning it off results in same performance as having all tracks armed for recording. That's why I have given the numbers "16 tracks armed" and "28 tracks unarmed".

 

the system I tested on is similar to yours and it's using 50% in vsthost