VST 2 SDK no longer available, will it affect plugs?

[whyterabbyt]

And exactly how does that affect the ability of a developer to update the plugin? What capacity for updating has been prevented?

Oh come on, I specifically said it prevents them from updating their plugin to any new format such as VST2.5 (if that ever happens) or VST3.

yes, you introduced that, but my statement was not specifically constrained to that, so its fundamentally irrelevant to my statement.

its simple logic... either plugins can be updated or they cannot.

the fact that they cannot be ported to a different API has no effect on whether any other updates are possible.

if other updates are possible, then my assertion was correct.

Of course that is true, I think you're just being a little more disagreeable than necessary here!

Does it prevent existing plugin authors from updating their existing products or creating new ones? No of course not, but it does have its little gotchas that I don't think should be brushed off quite so quick.

It was a very black-and-white assertion, and my answer was predicated on it being a shades-of-grey issue. There wasnt anything being brushed off other than the false dichotomy itself.

[aciddose]

Well when I read his post I didn't immediately assume he meant any sort of patch or change to an existing plugin. He used the word "upgrade", which to me actually means something changing significantly. Since we're on the topic of plugin interfaces I actually went ahead and assumed he was referring to an upgrade of the interface.

If he meant only whether patches could be issued... I don't know, that seems patently false doesn't it? I can't see him asking the question meaning solely that.

[whyterabbyt]

Well when I read his post I didn't immediately assume he meant any sort of patch or change to an existing plugin. He used the word "upgrade", which to me actually means something changing significantly.

Sorry, but he very absolutely did not use the word 'upgrade', which is why Ive been saying he said 'update' all along. You even quoted it, so Im not sure why youve got that so wrong.

So if a dev I have bought a plugin from doesn't enter into the agreement, I can't expect that plug to be updated?

[aciddose]

Well when I read his post I didn't immediately assume he meant any sort of patch or change to an existing plugin. He used the word "upgrade", which to me actually means something changing significantly.

Sorry, but he very absolutely did not use the word 'upgrade', which is why Ive been saying he said 'update' all along. You even quoted it, so Im not sure why youve got that so wrong.

Okay, sorry then. It means the same to me though, what I said is still valid.

Update, upgrade, not "continue releasing their existing plugins" or "patch" or whatever. The more important thing for me was the context he said it in, regarding the changes of the interface.

I would've just gone with a nod regarding "it won't influence updating existing plugins with the old sdk" or similar. To say it's entirely incorrect to think it might have an influence on updates of plugins however I think is going too far. It could very well have an influence. A new version of a plugin might no longer be allowed to carry a VST logo in advertisements, for example.

More importantly from my point of view, if new plugin authors get the sdk via the VST3 package they'll need to agree to the new license which may carry further restrictions.