Thanks for clarifying. The terms are highly ambigious (see the sibling answer https://news.ycombinator.com/item?id=40930298), that's why I asked. Personally, I would rather use the terms "audio pipeline" or "audio graph" instead of the generic "bus".
> In all these cases, you need to assume that all processing code that isn't yours needs all the time that you can leave for it and just make your own code as efficient as is reasonable.
Yes. For audio programmers that is obvious, in particular when it comes to plugins, but for novices it might be worth pointing out!
> In all these cases, you need to assume that all processing code that isn't yours needs all the time that you can leave for it and just make your own code as efficient as is reasonable.
Yes. For audio programmers that is obvious, in particular when it comes to plugins, but for novices it might be worth pointing out!