So, looking at whats happening in the code right now - there seems to be an effort to map eq and compressor controls in a dedicated way for the MCU control surface… Wouldn’t this be exactly where such a mapping system could come in handy, even with ardour-internal mappings for certain eq/dynamics plugins?
Because of our intimate relationship with mixbus, we decided to have a “well known controls” API that provides access to a set of pre-defined controls/parameters in a track/bus. In Ardour, these all return null pointers, because there are is no defined DSP (plugins) there. In Mixbus, these things are known (they refer to the Mixbus channel plugin present in every track and bus).
The well known controls API is only used with Mackie Control if the device is switched to the “dynamics” or “eq” subviews. It is not used in the “plugin parameter” subview.
1 Like
This topic was automatically closed 91 days after the last reply. New replies are no longer allowed.