You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't think that either of us feels motivated to tackle this, but it is an "issue", so filing as such.
I was reminded of this today upon Steinberg's announcement of a timeline for dropping VST 2 support from their host applications. To be seen whether this influences other hosts to follow suit.
There also is the issue of the VST 2 license, which prevents us from distributing full source code of the Windows versions our plugins, despite our own license stipulating that requirement. VST 3 has a dual license distribution that includes a GPL option.
If we did adopt VST 3, I would be comfortable with releasing that in addition to AU on macOS. It is a far better specified format than VST 2 and, as such, host support is more consistent, making the idea of supporting a second format on macOS not cause me to sad-tired slump.
All of these things make VST 3 compelling, but for the issue that it is not really an "update" to VST 2 but rather a wholly distinct API and therefore would require significant development work from us.
The text was updated successfully, but these errors were encountered:
I don't think that either of us feels motivated to tackle this, but it is an "issue", so filing as such.
I was reminded of this today upon Steinberg's announcement of a timeline for dropping VST 2 support from their host applications. To be seen whether this influences other hosts to follow suit.
There also is the issue of the VST 2 license, which prevents us from distributing full source code of the Windows versions our plugins, despite our own license stipulating that requirement. VST 3 has a dual license distribution that includes a GPL option.
If we did adopt VST 3, I would be comfortable with releasing that in addition to AU on macOS. It is a far better specified format than VST 2 and, as such, host support is more consistent, making the idea of supporting a second format on macOS not cause me to sad-tired slump.
All of these things make VST 3 compelling, but for the issue that it is not really an "update" to VST 2 but rather a wholly distinct API and therefore would require significant development work from us.
The text was updated successfully, but these errors were encountered: