Steinberg Discontinuing VST2 Support in its products

[zvenx]

...
Vst3 plugins will continue to have midi problems that can affect SOME midi and Inst plugins….regardless of whether they are implemented as native vst3, wrapped vst2 or wrapped clap. That is just an inherent flaw in vst3 design that will impact anyone using vst3 plugins of any kind in any host.

...

would you like to tell me what flaws waves vsti's or steinberg vsti's vst3s have for instance?

These broad sweeping remarks of yours again. smh

rsp

[Dewdman42]

Maybe later I will send you a detailed PM. You can also google for many discussions on these points that are already out there explaining these design problems. I’m not sure why you’re mentioning Waves now. Vst3 has design problems in the api regardless of who implements it. The statement I am making is factual. Do your homework and stop evangelizing for Steinberg

[zvenx]

I mention Waves because they have been doing vst3 for over ten years and have vst3 synths...

" That is just an inherent flaw in vst3 design that will impact anyone using vst3 plugins of any kind in any host."

So therefore waves plugins should suffer too..

What I do know is that some not all developers have had issues with vst3.. Some Not All!!! Hence why I am using Waves as an example.

You keep once again saying this things without data to back you up. The last time I asked you for data to prove your point, you did not provide any such to put it mildly.
No need for PM, put it here where everyone can see..



rsp

[nix808]

I'd welcome CLAP,
but just the abbreviation don't sound that cool
..what about SUB?
substrate universal binary
..or OPS
open plug standard/strata

[Dewdman42]

The vst3 design flaws are well known by those that know, which apparently does not include you. Vst3 midi design flaws can affect any manufacturer including waves of course.

It has to do with the fact that vst3 does not process raw midi. There are a number of issues that have come up related to that. For example, there are certain use cases where the serial nature of midi is lost because of the way they abstracted it and this can cause problems in some midi use cases. Other problems too, all stemming from the loss of raw midi processing. You can use google yourself and find plenty of stuff written already on this topic and problems that developers have had with vst3 midi, I’m sorry but it’s not my responsibility right now to re explain it to you in detail.

[zvenx]

It is not the explanation that is the issue for me, it is your broad,.. ALL.. and indeed that is not the case, yet you continue to use it like you know this with 100% certainty.

That is my issue with your statements.

Some? of course.. All.. hell no.

But that wouldn't stop you from pontificating.

rsp

[Dewdman42]

Well I don’t really care what your problem with me is I am being factual. Do your homework and stop arguing endlessly over how you interpret my words.

[zvenx]

yep.. cause once again, no evidence required.
Carry on.
Preach the 'facts' some more.

rsp

[sQeetz]

would you like to tell me what flaws waves vsti's or steinberg vsti's vst3s have for instance?

These broad sweeping remarks of yours again. smh

I can tell you one which you are aware of since you've been on the thread about Backbone
Steinberg's Backbone doesn't like MIDI 2.0. It refuses to work while it is on

[pdxindy]

It is not the explanation that is the issue for me, it is your broad,.. ALL.. and indeed that is not the case, yet you continue to use it like you know this with 100% certainty.

That is my issue with your statements.

Some? of course.. All.. hell no.

But that wouldn't stop you from pontificating.

rsp

You are starting to get really aggro and rude.

[Music Engineer]

@zvenx: well, he literally said that "SOME" midi effects and instruments will be affected - where the all caps is part of the original quote...which you even quoted yourself. perhaps those plugins that don't have any problems use only a subset of midi that happens to be unproblematic in vst3?

[zvenx]

would you like to tell me what flaws waves vsti's or steinberg vsti's vst3s have for instance?

These broad sweeping remarks of yours again. smh

I can tell you one which you are aware of since you've been on the thread about Backbone
Steinberg's Backbone doesn't like MIDI 2.0. It refuses to work while it is on

ooh, but from what I understand a lot of plugins don't work with midi 2.0 yet...but isn't that issue in logic using au?
I meant steinberg vst3 plugins.
My bad.
rsp

[zvenx]

@zvenx: well, he literally said that "SOME" midi effects and instruments will be affected - where the all caps is part of the original quote...which you even quoted yourself. perhaps those plugins that don't have any problems use only a subset of midi that happens to be unproblematic in vst3?

mind showing me where I had quoted that some (not at all saying I didn't, just not finding it easily).
rsp

[sQeetz]

ooh, but from what I understand a lot of plugins don't work with midi 2.0 yet...but isn't that issue in logic using au?
I meant steinberg vst3 plugins.
My bad.rsp

Not a single plugin I have (and I have a lot) doesn't work with MIDI 2.0 on Logic left on. It's just Backbone which doesn't. MIDI 2 is backwards compatible.

[Music Engineer]

here: viewtopic.php?f=7&t=576589&start=438