Steinberg sending DMCA takedown notices for the VST2 SDK
category: general [glöplog]
The files I linked don't seem to have any mention of GPL3.
Quote:
The reason people use VST is becase it's the de facto standard for commercial audio software on Windows.
I do not and I will not! One of the biggest mistakes I did in the past was after collecting and selecting for years Buzz-dll's only (givin a shit about VST like the demoscene-rulez said...lol), using (small, free) VST-dll's together with Buzz-dll's after 4klang VST came out! That thing was terrible incompatible also as Buzz-dll and I had tons of together working dll's. It just started to mess up also when new vstloader and wasapi stuff came out. Sry for ot. I do not want to flame the makers and the massive work from ppl like polac, bero or saga musix aso...! I just warn you: do not believe in "will run 4ever after updating the DAW, Plugins and OS". The stable house of cards will crash! The point in my last Post was maybe wrong because of my bad expiriences with VST-dll's. Thats why I use reason without any third party plugins and I even pay for it sinse version 3,... it just runs and runs and runs while saving very small files compared to other famous stuff. The output would be the same anyway equal what DAW you use... I want it stable and small. The only thing reasin is missing is the downscroller tracker-interface but I'm just too lazy atm. kiss
Quote:
"will run 4ever after updating the DAW, Plugins and OS"
Did anyone actually claim that? :P
Quote:
The files I linked don't seem to have any mention of GPL3.
The licensing terms have changed in more recent versions. The official GitHub mirror of the SDK is here.
Now this is interesting. I read through the latest license agreement, and the fact that it explicitly excludes vst2 and explicitly states vst3 everywhere is new. Well, it gave me a tiny shock, so I compared with the one I have
Older agreemens simply covered "VST Plugins". Steinberg is really serious about phasing out vst2...
Older agreemens simply covered "VST Plugins". Steinberg is really serious about phasing out vst2...
according to the JUCE forum, it's still possible to get a vst2 agreement signed by steinberg though.
Quote:
Did anyone actually claim that? :P
I don't know. I just worry about 'starter-thinking'. :)
Aqu its way worse on the AU side where I dont want to touch with a 10 galaxy long pole... OS says what version you can use, and new versions are not made usually for the older ones because .. you cant. :D
But surely you are right, the plugins need updating from time to time.
But surely you are right, the plugins need updating from time to time.
My perfectly fine and adequate Autotune 5 stopped working in OS X Yosemite. Ok, that problem can luckily be fixed with 100-150 €. I wonder if they coded something like "if OS version number is greater than x, then crash and blame the user", cash cow milking system.
Probably not. If some cracking group found out, it'd look really bad in the news.
Steinberg is good at that. Fixing Wavelab 5 to not crash on Vista+ when opening a file dialog would have been a oneliner. Instead, they wanted people to update to Wavelab 6 instead. A fine person fixed the problem to make it run again (and even documented what went wrong - clearly their implementation was broken).
I don't doubt for a second that their software is riddled with subtle bugs that can be triggered by changes in OS behaviour. That's very different from explicitly checking the OS version and crashing on purpose like yzi suggested though.
Quote:
My perfectly fine and adequate Autotune 5 stopped working in OS X Yosemite. Ok, that problem can luckily be fixed with 100-150 €. I wonder if they coded something like "if OS version number is greater than x, then crash and blame the user", cash cow milking system.
Surely that's apples fault? I'm still running some Vst plugins on my windows 10 box that I used to use in windows XP.
does anyone still have this SDK for me?
At this point, the VST2 SDK is still part of the VST3 SDK.
Oh thanks - their site sort of denies that depending on how careful you read :) I'll go fetch it!
plek: thread me necrofull?
The topic is still very current.
I second that. Since I'm dabbling in plugindev professionally this topic affects me very much. I wonder, are other sceners here doing this for a living?
jco, if you're doing this for a living, you most likely already have the VST2 SDK so this shouldn't be an issue.
The threat to remove the VST2 headers / hide them behind a legal-wall (=> sign a contract with Steinberg) mainly affects open source projects.
There's still the "Vestige" header (a re-implementation of aeffect.h). It's still shipped with at least one (notable) open source DAW.
A legal grey zone ? (I don't think so. It's not "actual" code, and it's sole purpose is to ensure software compatibility)
Anyhow, why wasn't this hunk'of'junk plugin interface placed under the MIT license to begin with..
The threat to remove the VST2 headers / hide them behind a legal-wall (=> sign a contract with Steinberg) mainly affects open source projects.
There's still the "Vestige" header (a re-implementation of aeffect.h). It's still shipped with at least one (notable) open source DAW.
A legal grey zone ? (I don't think so. It's not "actual" code, and it's sole purpose is to ensure software compatibility)
Anyhow, why wasn't this hunk'of'junk plugin interface placed under the MIT license to begin with..
Quote:
Anyhow, why wasn't this hunk'of'junk plugin interface placed under the MIT license to begin with..
Isn't that pretty obvious? Steinberg wants to be in control of their platform.
bsp, sdk and license is fine. I'm curious about what happens with the market in general. From my perspective, every daw should start supporting vst3 asap.
Well that yeah, just wish Ableton would bloody catch up!
Or there should be an open vst API that everybody uses.. where's khronos when you need it..
Quote:
Or there should be an open vst API that everybody uses.. where's khronos when you need it..
An ironic question given the state of OpenGL and Vulkan support by Apple. :)