Maybe we are talking about 2 different issues? The issue I had with my M1 Max machine, which did not happen on my M1 mini or my Ryzen 1800X machine, was that there were occasional spikes of the CPU no matter what patch was selected and if Avenger was playing or not. These CPU spikes are not happening on my M1 Max anymore using Avenger 2.0.5.Hanz Meyzer wrote: Thu Dec 14, 2023 7:11 am Guys, I can't currently take you seriously with the statement that spike-problems on arm Macs are gone now... Too much not-so-well-thought rubbish was posted here...
Please post a proof, by posting a screenshot of Bitwig's performance monitor playing Avenger 2.05 and a known-to-spike-preset. Or is this just fake news, just as the many times before?
You seem to be talking about a separate issue where some patches are always spiking? Manuel mentioned earlier in the thread that some functionalities require additional calculations at note start so if these functions are used then there will be short spikes at those events.
This seems like normal behaviour to me. Of course they should try to optimise those calculations as much as they can though. But on my systems I have not run into this being an issue for me yet.msvs wrote: Sat Dec 02, 2023 9:15 am some seem obsessed with spikes.
Short spikes will always be there, since on generation of a sound after note press, there are some parameters to be initialized. The sound/cpu is on hold until this is is finished (just a fraction of a second). The Asio buffer size determines how much time you grant the processor for this task. If buffer is too short or your cpu too slow for that timewindow, it will conflict.
So on most machines you wont even notice. Afaik Hanz has one of those rare machines, where you seem to notice. But unless you bring us your machine, I guess Rene has no idea, why that is the case.
This is the same for some other synths as well. If you have Falcon for example load the Boids Nebulae Sequence in the Factory 2 library in Bitwig, play a note and look at the DSP Performance Graph and see all the spikes show up there. Now disable the Boids script processor and play a note. No spikes. Does this mean that UVI should remove the Boids script or that they must optimise it so that it doesn't cause any spikes when used? Or is that just a natural cause of using the functionality in that script? To me I accept that using that script has that effect and determine if the cost of using it is worth it or not for the patch I am working on.
If it only happens with certain patches in Avenger then it seems that there is not a fundamental issue with Avenger that causes the spikes but rather some specific functions. Maybe you can identify which functions are causing you issues and then contact support to see if there is anything they could optimise in those to help you?
