Do we need VST 3 compatibility in Cantabile?
I personally am more interested in legacy VST plugin support but what is this new VST 3 plugin future about?
VST 3 standard?
-
- KVRist
- 60 posts since 6 May, 2007 from scandinavia
For processing when mixing, for instance, vst3 will change a lot IMO, (vst 3 features). I'm not sure how important it'll be for cantabile users. I know I'm not gonna need it.
-
- KVRAF
- 8389 posts since 11 Apr, 2003 from back on the hillside again - but now with a garden!
Just had another read through to remind myself of what VST3 says it offers..
..and again, as a dev, I can say that it offers nothing that VST2.4 couldn't give you, other than UTF16 strings (allows for extra character set support, so extra accents, etc, can show in parameter names, etc).
Stuff about silencing stuff is supported in VST2.4 if the host chose to implement it and the plug declared whether it processed 'tails'; surround support, even auto-configurable, was available in 2.4, and will only make a difference if it's been coded in a VST3 plug (plus depends on host support).
What changed with VST3 was the 'architecture', ie how to build/structure the code. Instead of getting a bunch of bricks and building what you need [VST2.4], one now has to purchase vast quantities of supposedly shiny stuff, fit it into blocks that no-one outside of the deep recesses of an ivory tower is entirely happy about, and entry into your new item is only via custom fixed passage which scrapes against the skin of any dev hardy enough to inmplement it.
It's getting some exposure, but is more about re-marketing that innovation.
..and again, as a dev, I can say that it offers nothing that VST2.4 couldn't give you, other than UTF16 strings (allows for extra character set support, so extra accents, etc, can show in parameter names, etc).
Stuff about silencing stuff is supported in VST2.4 if the host chose to implement it and the plug declared whether it processed 'tails'; surround support, even auto-configurable, was available in 2.4, and will only make a difference if it's been coded in a VST3 plug (plus depends on host support).
What changed with VST3 was the 'architecture', ie how to build/structure the code. Instead of getting a bunch of bricks and building what you need [VST2.4], one now has to purchase vast quantities of supposedly shiny stuff, fit it into blocks that no-one outside of the deep recesses of an ivory tower is entirely happy about, and entry into your new item is only via custom fixed passage which scrapes against the skin of any dev hardy enough to inmplement it.
It's getting some exposure, but is more about re-marketing that innovation.
