From 22783f7e418cf02c659fe021966b6c1d1a3848a8 Mon Sep 17 00:00:00 2001 From: Alexandre Prokoudine Date: Wed, 5 Oct 2022 18:02:26 +0300 Subject: [PATCH] Less drama as per @x42's suggestion --- include/io-plugins.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/include/io-plugins.html b/include/io-plugins.html index 9a929908..7e9043ca 100644 --- a/include/io-plugins.html +++ b/include/io-plugins.html @@ -18,8 +18,8 @@ The rationale for pre-processing with I/O plugins is that it's a more lightweight way to do it as compared to busses. Much of that is because busses have automatable parameters such as fader and panner positions, as well as - plugins' parameters. Evaluating automation (even when there's none) is - expensive in terms of CPU use. However I/O plugins are not automatable, so + plugins' parameters. Evaluating parameter automation (even when there's none) + adds additional load to the CPU. However I/O plugins are not automatable, so there's no evaluation happening. As far as Ardour is concerned, they are almost like JACK audio server clients running alongside Ardour.