Just asking
Some info…
There is a lot more info out there if you google it.
Myself, after reading up on this it appears to offer a lot of advantages with multithreading and processing when it comes to Vst’s does anyone from the Cubase Dev/support squad know if this is being looked into?
Best regards
Sin
I would be shocked if the inventors of VST would help this new standard forward. Most certainly the makers of CLAP are saying all the things I want to hear. If you are going for CLAP right now I think Bitwig is the DAW that is pushing it forward the most.
Yup, it would appear that way but on what I understand there is growing support and if what is being written it holds a lot of promise for the future.
More info for any folk interested in finding out…
Regards
VST3 is already MIDI 2.0 compliant. It does it by having the host do all the necessary work in regards of supporting MIDI 2.0. The plugins themselves don’t have to do anything special. In other words: if your DAW supports MIDI 2.0 then your VST3 plugins support it automatically as well. All of them.
In that regard the MIDI 2.0 part of your topic title is already done in Cubase 13, so all that’s left is asking for Clap support.
Chances for that to happen are close to zero, I’d wager.
No problem, kind of ? I wouldn’t take yor bet!
Maybe Steinberg have a monopoly to protect, rather than a service to musicians and studio folk. I dunno the head in the sand mentallity is not a good look in my mind.
The benefits of better thread handling and the polyphonic advantages are very appealing
I am not stressing about CLAP no matter how good it sounds. For now, it is new and I don’t feel I am missing out at all. I am sure Steinberg is following this and will continue to develop VST more going forward
I am not stressed about clap, I would like it to be available if it works as is suggested. Having a Vst architecture that offers more stability etc. is something I would hope we all want.
As I said just askin.
I’d prefer Steinberg fix the existing audio problems first.
@Barry_Ford
What if CLAP could be a route/aid to fixing some of the existing audio problems, wouldn’t that be worth it?
Software and Tech have developed vastly since VST was introduced and most if not all DAWs use Vst. I hope most folk want to have a user interface and tools that make making music a pleasure.
If something can aid in that venture I would like to be able to take advantage of that tech.
Regards
Sin
What if not?
BTW - this kind of question technique was used by TV show “Ancient aliens” so much that it turned into a meme show.
Let me try to put my suttle hint from above into different words: Why don’t you change the title of your topic to “Clap integration: is it on the horizon”?
The MIDI 2.0 part made me think “I don’'t need Clap for MIDI 2.0, I have it already with VST3”.
CLAP may indeed be a great platform for audio applications, but given that Steinberg invented ASIO and VST and still can’t get them working reliably in Cubase, I don’t look to Steinberg for leadership in CLAP. I’m updating to REAPER 7 rather than Cubase 13.
@Johnny_Moneto
That’s fine by me if you don’t need it, seems a moot arguement. Why bother commenting?
Perhaps I have a different perspective about what Midi 2 brings to the table.
I wish you well and best regards.
Sin
The beauty of a DAW that can host plugins, is that there is usually more than one 3rd party option out there.
Grab something like Bidule, and you can then host (or maybe a better word is bridge) CLAP into just about any DAW or Scoring Suite on the market.
Utilities like that have been among the best software investments I’ve ever made. I get ‘features and abilities’ right away that people have been requesting in their main host apps for years and still don’t (and might never) get.
@Brian_Roland
I’ve never tried or used Bidule, I will have to look into thanks for the heads up.
Kind regards,
Sin
A weird but powerful thing it is. Sometimes the graphical/modular thing can get tedious and annoying, but the possibilities of what you can build with it are endless (one can also get a dev kit if its prefered to invent bidules using ‘code’ instead of working with the graphical bidule ‘thinggies’).
The simplest ‘monitoring and diagnostic’ abilities alone are worth the price to me. Using it as a simple chainer and plugin ‘bridge/chainer’ is the whipped creme.
Merging half a dozen different plugins into a single ‘super plugin’ can be loads of fun 
Start digging deeper and it’s mind boggling what all it can add, to even the simplest/dumbest of hosts. OSC server/client abilities stands as a pretty interesting example.
I bother because I sense that your perception is not matching how things really work.
VST3 cannot have more MIDI 2.0 support than it has right now. You seem to be intrigued by a new information but VST3 has this kind of support already for years.
There are two different concepts at work:
Clap wants the plugin itself to do the support for MIDI, ie. Clap delivers MIDI messages to the plugin.
VST3 delivers no MIDI at all to the plugin. The host application transforms any MIDI message into a VST event. Therefore if the host supports MIDI 2.0 the plugin will support it, too.
So, the real question is: Does VST3 match the functionality of MIDI 2.0? And the answer is: yes, already for a long time. Clap is very late to that particular party.
@Johnny_Moneto
Fair comment, but I see it in these terms…
Up until now, MIDI 1.0 conversations were a one-way thing: From transmitter to receiver. However, 2.0 now allows for a bi-directional conversation. Your devices talk to each and work together, auto-configuring themselves instantly.
The perspective that it is written in stone that the daw is doing all the heavy lifting, but if CLAP has extended threading abilities and a layer that starts to create future proofing I see it as a benefit.
VST3 already has a bi-directional communcation since it was introduced.
Your VST3 plugins already send all their information to the host, do they not? Things like this:
The capabilities of MIDI 2.0 are no different.
If anything comes close to being written in stone it is MIDI. 40 years of the same limitations. MIDI is only great in one thing: It is understood by all musical instruments and their mother. In every other way MIDI is a shackle that keeps everybody held back. Steinberg tried to get rid of the shackle by introducing VST, VST2 and ultimately VST3. It took the MIDI Association 40 years to come up with something, that VST3 already has for more than a decade.
There are like, how many, 15 significant DAWs out there?
Compared to hundreds of plugins.
I would rather have the few DAWs having to do the work than each and every plugin in the world.
I don’t know how many plugins you have but imagine you’d have to update each of them in order to get this functionality. Imagine you’d have to pay for such an update for quite a few of them. Compare that to just updating your DAW.
I don’t wanna dismiss Clap. There are clever people behind this and they have good ideas.
It is just that the support for MIDI 2.0 is rather a “yeah, finally we have that, too” instead of your perception of “whoo, the revolution starts with us, baby”.
They are just catching up.
I am struggling to get my head around your need to dismiss this question, and the need to … “whoo, the revolution starts with us, baby”, make derogratory statements.
This is just a simple question. I think is worth looking into. This video by the midi Association is gives the information, not me.
I believe Steinberge did some very innovative work back in the eighties and have made huge strides forward, why stop now.
Regards.
Still waiting for all these instruments and plugins to use MIDI 2.0. Until then, there is no point…
Yay CLAP just what we needed, yet another plugin ‘standard’. Probably because someone didn’t like the VST rules or didn’t want to have to pay for a license…