Bye bye VST2

[zvenx]

If Virsyn was the first in Feb 2008, i imagine the first sdk would be in 2017?
rsp

[zvenx]

...

yes, this shit's so easy harry hasn't updated most of his plugins for years. he pretty much just does AU v3 for iOS now.

That could be for economical not technical reasons though.
rsp

[gaggle of hermits]

VirSyn Releases First VST3 Plug-in

Aren't VirSyn currently in a quandry with e-Licenser? Their website links to e-licenser issues when you click on the M1-M2 compatibility link. IMO another example of why it's bad to rely on a third party developer with vested interests in selling the same types of products you sell, plugins and a DAW etc. VirSyns loyalty didn't seem to pay off much.

I don't think elicenser is completely the issue here. a few of the synths use a c/r or serial code. I got the impression that he just found the app market on iPad to be a more reliable source of income so the rest of the product line got left to wither.

there are plugins that haven't been updated since 2014 from what I can tell - well before Steinberg's shenanigans with elicenser.

however, vengeance and Vienna symphonic were doubtless over the moon about Steinberg suddenly deciding to pull any and all support for the dongle. VSL has completed its transition. vengeance is still in beta with its fx suite.

[mi-os]

Yeah, he switched to iOS for the bigger market, i guess. I doubt it had anything to do with VST3. His plugins were very good btw.

[zvenx]

"Nuendo 4 supports Steinberg’s latest incarnation of the VST specification for plug-in effects and instruments, VST 3.
In addition to offering better routing and automation facilities, thanks to the new VST3 plug-in support Nuendo 4’s mixer also supports side-chaining for VST3 plug-ins. Here you can see an audio track’s output being routed to the side-chain input of the included Compressor plug-in.
In addition to offering better routing and automation facilities, thanks to the new VST3 plug-in support Nuendo 4’s mixer also supports side-chaining for VST3 plug-ins. Here you can see an audio track’s output being routed to the side-chain input of the included Compressor plug-in.Cubase 4 was the first host application to support VST 3 plug-ins, and even though it was released over a year ago, until recently Steinberg have remained quiet on the subject of opening up VST 3 to third-party developers. This was somewhat surprising, since the freely available nature of VST was arguably the reason it became so popular in the first place. However, just before Nuendo 4 was announced, Steinberg revealed more information about VST 3, stating that a public Software Developers’ Kit (SDK) that will allow other developers to support the format will be available in January 2008."

https://www.soundonsound.com/reviews/steinberg-nuendo-4

[gaggle of hermits]

...

yes, this shit's so easy harry hasn't updated most of his plugins for years. he pretty much just does AU v3 for iOS now.

That could be for economical not technical reasons though.
rsp

it is. but when your poster child for easy vst3 is a dev who is MIA on the platform...

also, harry had strong reasons for playing nice with Steinberg at that point. that first plugin was a vocoder that absolutely requires side-chaining - the thing that Steiny was keen to push to vst3.

[mi-os]

My guess is they wanted to test it internally before releasing it to the public.

[gaggle of hermits]

January 2008."

https://www.soundonsound.com/reviews/steinberg-nuendo-4

and as I've already pointed out, cubase 4 with vst3 was announced in autumn 2006.

funny how harry was able to do it in a month, isn't it? almost like he had privileged access and support, so hardly a surprise he's happy as Larry in the ensuing press release.

[zvenx]

My guess is they wanted to test it internally before releasing it to the public.

As is reasonable and often the case.
Though I have to admit that I wouldn't be surprised there was also a bit of commercial advantage in doing so.
rsp

[zvenx]

January 2008."

https://www.soundonsound.com/reviews/steinberg-nuendo-4

and as I've already pointed out, cubase 4 with vst3 was announced in autumn 2006.

funny how harry was able to do it in a month, isn't it? almost like he had privileged access and support, so hardly a surprise he's happy as Larry in the ensuing press release.

Or it was as he said easy for him to do..
Didn't some CLAP Developers say they did theirs in one afternoon? Would it be impossible for some vst3 developers to also have been able to do it quickly?

I can't easily find it now, but there was a developer who had said in the other thread why it was easy for some and not for others.

rsp

[machinesworking]

Or it was as he said easy for him to do..
Didn't some CLAP Developers say they did theirs in one afternoon? Would it be impossible for some vst3 developers to also have been able to do it quickly?

I can't easily find it now, but there was a developer who had said in the other thread why it was easy for some and not for others.

rsp

I dunno man, you and others seem to be living in some alternate universe? Developers here at KVR have been talking for 15 years about how much of a mess VST3 is/was for them, how can you ignore that and attempt to use one, maybe two examples of people who said it was easy? How can you ignore multiple developers here saying it's not, in favor of what? What are you defending?

VST3 isn't going anywhere, likely most of us will migrate to it either completely or for the few things it's better than AU for, but it's patently obvious that it's a PITA to code for, that a company that made VSTs and used their e-licenser said it was easy 15 years ago doesn't hold any merit compared to VST3 finally being adopted only more or less fully last year. AU took no time at all to be adopted and it's a single platform tech.

[zvenx]

Because not all developers have found it a mess.
You and others seem to think that since there are some at kvr who says it is a mess that universally it is a mess.
That may not be the case. Clearly it is a mess for some, even many... but I am not sure, and I dont' think you are sure how universal that is.

I beta test for quite a few software developers, it is not universally a mess. Clearly it is for some. Especially the ones loudest here on kvr.

rsp

[gaggle of hermits]

it's all very well saying "well it's only the loudest voices here". actions say a lot. if it was a slam dunk most of the devs would have done the transition years ago, especially anything that benefits from sidechain access. it was pretty much only Steinberg killing the vst2 sdk that made a sizeable difference in uptake.

even so. it's by the by. the point remains it's a stupid move by Steinberg to basically threaten devs out of providing vst2 versions. and we've seen it's actually doing them more harm than good as, had they left it alone, CLAP would have found it way, way harder to get off the ground. no amount of "well vst3 is here now" and "it was easy for these people" is going to change the underlying issue that plugin and host devs are taking a good look at how Steiny might try to screw them over in the future. because they've already shown how willing they are to do it (until this afternoon, I'd completely forgotten about the "so long and thanks for all the fish" episode with elicenser).

[zvenx]

...

even so. it's by the by. the point remains it's a stupid move by Steinberg to basically threaten devs out of providing vst2 versions. ...

.... because they've already shown how willing they are to do it (until this afternoon, I'd completely forgotten about the "so long and thanks for all the fish" episode with elicenser).

and to the first point we are at one...
which elicenser issue? that they changed was a big episode? how so?
rsp

[machinesworking]

Because not all developers have found it a mess.
You and others seem to think that since there are some at kvr who says it is a mess that universally it is a mess.
That may not be the case. Clearly it is a mess for some, even many... but I am not sure, and I dont' think you are sure how universal that is.

I beta test for quite a few software developers, it is not universally a mess. Clearly it is for some. Especially the ones loudest here on kvr.

rsp

OK then why 15 years for saturation? Plus, you named ONE developer who said it was easy, who currently doesn't update his VST3 plugins... I could name a dozen who said it was not. I could name examples of companies that seem to be redesigning their entire line up for VST3 compatibility, but I'm certain you can't name a dozen who say it was easy. What more do you want? Nothing about the transition was easy, in fact in some ways it looks far harder than Intel to Apple Silicon for developers. You're willing to downplay developers concerns for what? loyalty to a company?

KVR is a place where you can actually listen to what developers have to say about coding for various formats, and to come in and deny that they have a point is just arrogant to some level I can't even understand if I tried.