View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0008920||ardour||features||public||2022-06-01 11:34||2022-08-12 13:44|
|Priority||low||Severity||minor||Reproducibility||have not tried|
|Product Version||Mixbus 8.x|
|Summary||0008920: VST plugin issue with multi-output plugins|
|Description||Sorry if I'm duplicating an entry here. AFAICT it isn't possible to search the entries using text. You need to search for a specific bug ID number (is that just me misunderstanding something..?) Anyway...|
Over on the Mixbus forum there've been reports about VST3 plugins not working if they offer multiple outputs (more than 2 presumably...) The older VST2 plugins support multiple outputs okay apparently.
|Tags||No tags attached.|
Probably not a duplicate, but currently expected behavior, which is also documented in the manual.
Ardour only supports one optional bus for VST3 plugins (usually side-chain input), and does not support variable I/o for VST3 plugins. Addressing this is on the long-term ToDo list.
(VST2 does not support variable I/O, an instrument with multi-channel output will always have all those outputs)
This is not a Windows specific issue, but Ardour/VST3 related.
Conceptually VST3 bussing is at odds with how Ardour internally handles variable-i/o (which is heavily inspired by audio unit). Solving this will require a major internal overhaul.
|2022-06-01 11:34||johne53||New Issue|
|2022-06-02 01:15||x42||Note Added: 0026478|
|2022-06-02 01:16||x42||Priority||normal => low|
|2022-06-02 01:16||x42||Severity||major => minor|
|2022-06-02 01:16||x42||OS||Windows =>|
|2022-06-02 01:16||x42||OS Version||10 =>|
|2022-06-02 01:16||x42||Platform||Microsoft =>|
|2022-06-02 01:16||x42||Additional Information Updated|
|2022-06-02 01:18||x42||Note Added: 0026479|
|2022-08-12 13:42||x42||Relationship added||has duplicate 0008939|
|2022-08-12 13:44||x42||Relationship added||related to 0008855|