Plini update 2.0: Sample latency/CPU usage

I did a lot of measurements and analyzes, with different settings, taking each time the average CPU usage for the measured setting, and waiting for a minute in order to be sure that there is no interference from Windows background tasks.
Each setting use either an existing preset for concrete comparison, or a very specific part of the plugin in order to detect where the increases occurred.
Each test use 10 instances in a row of a same setting in order to have a better precision and to simulate the situation of multiple instances in a project. The results here are already divided by 10, even if it doesn’t change anything for comparison purpose.
Since an empty plugin instance with all the upper icons disabled has a CPU usage, it has been substracted for component one by one results in order to reveal the component proper cost.

Here is my Reaper audio setting (setup for low-latency/live playing):
image

Version 1.0.2

  • Presets
    • Default preset 7.6%
    • Every Piece Matters - lead 7.8%
    • Electric Sunrise - riff 5%
  • Components one by one
    • Nothing activated (all the upper icons are disabled) 0.2%
    • Compressor 0.08%
    • Overdrive 0%
    • Amp 1 0.9%
    • Amp 2 1%
    • Amp 3 1.1%
    • Equalizer 0.15%
    • Cabinet with 1 mic 1.4%
    • Cabinet with 2 mic 2.9%
    • Delay 0.5%
    • Reverb 2.2%

Version 2.0.1

  • Presets
    • Default preset 8.5%
    • Every Piece Matters - lead 8.8%
    • Electric Sunrise - riff 5.8%
  • Components one by one
    • Nothing activated (all the upper icons are disabled) 0.4%
    • Compressor 0.1%
    • Overdrive 0%
    • Amp 1 1%
    • Amp 2 1.3%
    • Amp 3 1.4%
    • Equalizer 0.15%
    • Cabinet with 1 mic 1.7%
    • Cabinet with 2 mic 3.2%
    • Delay 0.5%
    • Reverb 2.8%

Comparison v1.0.2 -> v2.0.1

  • Presets
    • Default preset +12%
    • Every Piece Matters - lead +13%
    • Electric Sunrise - riff +16%
  • Components one by one
    • Nothing activated (all the upper icons are disabled) +100%
    • Compressor +25% (but very small)
    • Overdrive +0%
    • Amp 1 +10%
    • Amp 2 +30%
    • Amp 3 +27%
    • Equalizer +0%
    • Cabinet with 1 mic +21%
    • Cabinet with 2 mic +10%
    • Delay +0%
    • Reverb +27%

In addition, I have checked a real-life situation with one of my projects which contains 2 mono Plini instances, 2 stereo Plini instances, and nothing else.
The project has a total CPU usage of 43% with v 1.0.2, and 59% with v2.0.1.

My conclusion:

  1. Total CPU usage increase in a real project is around 30%
  2. CPU usage for a single instance is around +15% for complex presets, around +30% on simple presets that mostly rely on amp and 1 mic
  3. CPU usage increase is well distributed between most of the plugin components
  4. An increase appears even with everything disabled in the plugin

Hope it helps :wink:

1 Like