Yes it is a PreSonus extension. I suppose Ardour ought to test if it’s available for a given Plugin before replicating VST3 plugin instances.
Regretful for sure. You’ll note that at no time did Todd mention I should post on the Ardour forum, and indeed never mentioned you were involved. I found out on THIS forum when you explained. I’ve also encouraged the MixBus team to help us all know when which forum needs addressing.
If they did not mention it to you, I recently posted (Mac sub-forum) other plugin related issues, and have been doing so on that forum for quite a while. Today’s post seemed similar, so I posted. I’m told today, however that this thread and my issue are not similar after all and that I should NOT have posted here. Go figure.
h
1 Like
Now knowing this I would like to ask you Robin if you will work on the plugin self-reconfiguration issue and so a possible correction will be available in the near future or this is not a priority issue for Ardour so should I look for adaptive ways to make things work for my case?
There is the inverse problem when there is no way to remove additional unneeded linked instances.
When I would like to do corssovered multiband mastering using the LSP Crossover and Mixer plugin and placing between them for example a compressor for band 1 and another for band 2 with different settings then for a 4 band stereo setup I can’t use a vst3 plugin with one instance because Ardour will force 4 instances.
The removed option for the manual plugin instance setup was a really suboptimal decision.
It looks like this, and the manual config for Audio Input Pins does nothing, will not add and will not remove.
