ardour/manual
13
0
Fork 0
Code Pull Requests Releases Activity

Less drama as per @x42's suggestion

Browse Source
This commit is contained in:
Alexandre Prokoudine 2022-10-05 18:02:26 +03:00 committed by Paul Davis
parent e66a7d50d6
commit 6036e3f09f
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
include/io-plugins.html
View File

@ -18,8 +18,8 @@
The rationale for pre-processing with I/O plugins is that it's a more 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 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 have automatable parameters such as fader and panner positions, as well as
plugins' parameters. Evaluating automation (even when there's none) is plugins' parameters. Evaluating parameter automation (even when there's none)
expensive in terms of CPU use. However I/O plugins are not automatable, so 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 there's no evaluation happening. As far as Ardour is concerned, they are
almost like JACK audio server clients running alongside Ardour. almost like JACK audio server clients running alongside Ardour.
</p> </p>