Are you aware that you can load up a track with a VST plugin (Such as Scaler 2) and then use that as a MIDI input for another track with your VST Instrument loaded? It’s the same effect as having a MIDI insert, but the routing just makes it a little more complicated.
Absolutely. That would’ve been embarrassing.
The same could be said for most of the 3rd party devs. Just a matter of a few extra steps and you have the same result at the moment.
What intrigues me is the future though,
Now that plugins like Scaler and Modalics Arp can operate as inserts I would hope/imagine the companies would start working to utilise this newfound feature moving forward.
To the point where scaler could possibly become indiscernible from a stock plugin.
And if all of this is due to the plugin format allowing it then I think we are missing out.
Plus I’m think I’m correct in saying Inserts do not count towards your plugin slot limit so you also Save 1 or however many you use of those that would usually be dedicated to a plugin.
This is a CuBase forum. We are not here to build up freeware. And no one should suggest that Steinberg has not contributed to the community. VST and ASIO has been good for the entire industry. Replacing MIDI would make it a trifecta. They’ve got Yamaha’s hardware muscle behind them. They can do it.
Supporting CLAP is just having the new 800 pound gorilla help Reaper out. You’re asking them to share the ProTools spoils with open source?!? No.
What an odd reply(?).
Firstly, there was no mention of freeware; Fabfilter, TAL and Reaper all offer ‘paid for’ commercial products.
Secondly, there was no suggestion that Steinberg has not contributed to the community.
Studio One 7 seems like it’s getting CLAP support based on a few reports.
Very interesting to see the amount of DAWs supporting the format in such a short amount of time if this is true.
It’s also good to see an open format building up strength, for myself I think it’s much better for the end user. It’s not good when you see, read or hear of developers pulling in a different direction to the platform owners.
Studio One 7 is also going with a new subscription based plan that is making quite a few of its users rethink their DAW…
Where is this vast amount of support aside from Bitwig (who helped invent the standard) and Reaper? Avid mentioning they are ‘looking into it’ doesn’t mean a thing, they’re not about to kill their own ecosystem, just like Steinberg and Apple arent… We got two whole DAW’s that support it, one of them is the creator of the standard, and that’s it.
Not quite.
They’re moving to a bitwig-like 12 month maintenance /update plan, which is what Steinberg will likely be doing in the near future. The subscription option was always there, as most know.
And with both options, it’s a perpetual license. Though what relevance this has on the subject matter, is a little dubious. Let’s try to keep on topic please.
The following FOUR mainstream hosts are going to be supporting it:
FL Studio, Reaper, Bitwig and now Studio One.
Plus a number of smaller hosts, which is great for those wanting alternative/cheaper options.
On top of that plugin developers like Fabfilter, u-he, Audio Damage & TAL all have products on end users rigs. It’s very promising, you should check it out as your knowledge seems very out-dated! 
Uh oh outdated by about a month or so! Sorry my host only supports VST3, which is working just fine for me, so I could care less about using CLAP. We all know its never coming to Cubase, and thankfully, so Steinberg can focus on their own products.
Yes, it’s progressing fast, this is why I said you should check it out (the info online) or you’ll be engaging in a topic that you’re uneducated on. It just saves people time, as i’ve had to do, in correcting you.
Albeit, you’ve come back and said you don’t care anyway… So a waste of time really.
Hey-ho! 
I know it stands for “CLever Audio Plug-in” but still sounds wrong. Has SD vibes to it. “The clap” is a common nickname for gonorrhea, a sexually transmitted infection (STI) caused by the bacterium Neisseria gonorrhoeae. 
That reference was already noted a year or more ago a few posts in.
At any rate, I only half-perused the original Clap pr release….which takes 5 paragraphs before even beginning to describe what the clap protocol actually does.
In the meantime since the op, the vst3 protocol is now completely open-source as of this past week or whatever….so ..does clap even matter longterm?
I personally don’t care 
There was an interesting discussion on the KVR DSP forum regarding the implications of VST3 becoming open source. One educated bit of speculation was that, now VST3 is open source, a CLAP wrapper could readily be written that would provide the CLAP API anywhere VST3 was implemented … best of both worlds according to some opinions.
Old hat now. SyphilVST dropping soon.
CLAP is a perfectly good standard (not a good name though!), and I applaud the developers for their great work and good ideas, but I think now with the open sourcing of VST3, we won’t see the progression (or momentum, depending on who you talk with) for CLAP that we did before. Nothing against CLAP, but open source VST3 was a brilliant move and I think it will cause some settling of standards TBH. CLAP won’t go away because some people will always love it (and it does have some good ideas), but I think VST3 gained a lot more gravity with the open source move. And like @dmbaer mentioned, we’ll have a CLAP wrapper soon (if not already, I might have missed it).
The main thing with the open sourcing of VST3 is that, to me, it signifies another forward step in the evolution of Steinberg, and it’s a GOOD thing they did it. Perhaps it took the pressure of CLAP to make it happen, who knows? But any time you see Steinberg start to consider open source, that signals some good things at Steinberg IMO. Bravo to Steinberg, and congrats to the CLAP team too, and maybe even kudos to the CLAP team for indirectly pushing Steinberg to starting thinking about open source…. it’s all good if you ask me! 