Yeah, that's exactly why you saying so is tautology.
Ah, your various little ad hominems again. You always get there in the end, well done.But, you already know that anyway. You just disagree for the sake of it. Doesn't even have to make sense.
Yeah, that's exactly why you saying so is tautology.
Ah, your various little ad hominems again. You always get there in the end, well done.But, you already know that anyway. You just disagree for the sake of it. Doesn't even have to make sense.
It's actually the way YOU always behave in an argument. Because you can't argue without being abusive. Which shows what kind of a person you are. And how weak your actual argumentation is, if you feel the need to get abusive the whole time.whyterabbyt wrote: ↑Thu Jan 20, 2022 12:57 pmYup, this is how you always behave once you know you've lost the argument.
Says the guy desparately digging his little hole deeper, instead of actual argumentation.
Ah, the 'pesky kids' argument. But you were still Old Man Bollocks-talker all along.
What's your actual point there? That you responded to me just as many times in the exact same timeframe ? That you posted twice as much as that in this one thread before I even responded to you? That you resort to childishness when you cant win an argument?
Well what do I know!!! That is great newswhyterabbyt wrote: ↑Thu Jan 20, 2022 12:41 pmWhy dont you head over to the repository and count them, instead of making assumptions?Sindikhate wrote: ↑Thu Jan 20, 2022 12:07 pm ClAp probably does not even have 100 lines of code yet?
https://github.com/free-audio
but that's basically what Steinberg want, though; they're trying to completely prevent people from developing in the VST2 format:
Lets be clear here; the plugin industry pretty much exists as it does because of VST2. But if Steinberg had been doing then for VST2 what they are trying now wrt VST3, we probably would already have an alternate format.some guy on page 1, apologies for not copying the name wrote:Steinberg has made it clear that they don’t just want to drop VST2 support from their own products. They want the entire ecosystem of VST2 software to go away. They’ve made all kinds of legal threats against VST2 compatibility projects and really anything that uses the name “VST” in a way that they haven’t approved through the SDK license agreement, such as websites that host plugins. They’ve even taken over a few of those in recent months. And last spring they tried that stunt with the clause in the VST3 SDK terms of use that revoked VST2 licenses.
Not everyone is trying to create a closed ecosystem, though.Sindikhate wrote: ↑Thu Jan 20, 2022 1:43 pm I find it bizarre that no one mentions that almost everyone wants to create their own ecosystem.
That's always going to be a thing where your competition controls a key part of the ecosystem you need to use. The solution, which works elsewhere, is genuinely open protocols. Most of those protocols do originate from a single company, but they share, properly. For example, in the 3D software industry, Alembic, USD and, most recently, MaterialX...UAD with Luna, U-He/Bitwig and whoever else are doing their own thing, sample library companies try to move away from Kontakt by making their own players (Spitfire, 8dio, Orchestral Tools, Cinebrass and whoever else). Steinberg is forcing things, Avid/Digi always had their own world... But the current shift seems to be towards working alone rather than working together in a way. Many developers are boosting their legal teams as we speak so the future does not look very good from where I stand at least.
I totally agree. I still have some vst2 plugs that will definitely not be adapted to vst3 anymore. That means either two DAW'2 or away from Cubase. Steinberg would have to release a mega update that would make me update to 12. I don't miss vst3 but I can well imagine that the power users and producers have been waiting for it. For example, I have the Spectral plugin from LinPlug and also the plugins from PPG. I don't want to miss them.Markus Krause wrote: ↑Thu Jan 20, 2022 7:19 am Not a very smart move by Steinberg. This is what will happen:
1) Steinberg will get a huge shitstorm when their customers won't be able to load their old song-projects containing vst2 plugins
2) Most Cubase users will refuse update and stick with the last VST2 compatible version
3) People will use wrappers that adapt VST2 to VST3. This will result in more instabilities
4) Steinberg will loose customers, since they will move to other DAWs
© KVR Audio, Inc. 2000-2024
Submit: News, Plugins, Hosts & Apps | Advertise @ KVR | Developer Account | About KVR / Contact Us | Privacy Statement