To all 'Save as VST' users -> Remember your VST2 licence
- KVRian
- Topic Starter
- 1091 posts since 8 Feb, 2012 from South - Africa
Just a reminder to everybody who uses any 'Save as VST' format, remember to get your official VST2 licence paperwork done. After October anybody without a licence will not be able to make a VST2 legally. And no new licences will be issued after October.
Here is a SE link for the paperwork:
http://www.synthedit.com/vst2-licensing/
Here is a SE link for the paperwork:
http://www.synthedit.com/vst2-licensing/
- Beware the Quoth
- 33177 posts since 4 Sep, 2001 from R'lyeh Oceanic Amusement Park and Funfair
They're f**king desperate to kill off VST2 arent they?
Surely this affects all VST2 plugin creation, too, including native code?
Surely this affects all VST2 plugin creation, too, including native code?
my other modular synth is a bugbrand
-
- KVRAF
- 35439 posts since 11 Apr, 2010 from Germany
You need to be a big optimist to think there's any chance for a new plugin format to establish itself in a market which is so slow to conform to new standards. Look at MIDI. Look at VST and other formats. No chance. Developers will either continue developing VST 2.4's, or VST3's. There's already loads of developers providing both for their plugins.imrae wrote:On the bright side, this is a great opportunity for non-Steinberg formats like LV2 to get some more interest...
- Beware the Quoth
- 33177 posts since 4 Sep, 2001 from R'lyeh Oceanic Amusement Park and Funfair
Also; is there a specific reason that this is the license agreement for an older version of VST3, not the current one or the VST2 one; the VST2 license agreement document is still separately contained in the current (VST3 with VST2) SDK download.
my other modular synth is a bugbrand
-
- KVRAF
- 1579 posts since 14 Oct, 2002
Should we fill both the "Licensee" fields at the end of file? Or is intended for a third party license owner?
It is not so clear...
It is not so clear...
- KVRian
- Topic Starter
- 1091 posts since 8 Feb, 2012 from South - Africa
Yeah, fill in everywhere it says "Licensee", think the "technical contact" is written that way for companies that have more that one employee. If your a one man show like most of us, just fill in all fields.lalo wrote:Should we fill both the "Licensee" fields at the end of file? Or is intended for a third party license owner?
It is not so clear...
-
- KVRAF
- 1579 posts since 14 Oct, 2002
- KVRAF
- 9077 posts since 28 May, 2005 from Netherneverlands
That's such a wrong way to push new technology "standards".
If the new technology is good enough then the market would turn it into a new overall accepted standard by itself.
If the new technology is good enough then the market would turn it into a new overall accepted standard by itself.
No band limits, aliasing is the noise of freedom!
-
- KVRAF
- 35439 posts since 11 Apr, 2010 from Germany
Not necessarily. Unwillingness to learn something new, especially when it is not well documented, and allegedly gives no advantages, when most hosts don't support the extensions anyway, could also be a reason to stick with what you know well. I'm pretty sure if all hosts supported all that VST3 is offering, then we'd see more VST3's as well.Nielzie wrote:That's such a wrong way to push new technology "standards".
If the new technology is good enough then the market would turn it into a new overall accepted standard by itself.
Anyway, in Steinberg's positions, i'd close that chapter, develop VST4, make it easier for developers, then the new format would be more successful too. I just doubt that will happen, because they would have to spend valuable ressources on something which isn't 100% adding to their daily business. Not even sure who is responsible for VST3, and what they do in their daily job at Steinberg.
- KVRAF
- 9077 posts since 28 May, 2005 from Netherneverlands
That's why open standards in software or on the internet are so important. Now one of the many audio companies tries to dictate which way the developments of a market standard should go. They sucked/locked "us" in and developers/users can't go back that easily because everyone is using it already.chk071 wrote:Not necessarily. Unwillingness to learn something new, especially when it is not well documented, and allegedly gives no advantages, when most hosts don't support the extensions anyway, could also be a reason to stick with what you know well. I'm pretty sure if all hosts supported all that VST3 is offering, then we'd see more VST3's as well.Nielzie wrote:That's such a wrong way to push new technology "standards".
If the new technology is good enough then the market would turn it into a new overall accepted standard by itself.
Anyway, in Steinberg's positions, i'd close that chapter, develop VST4, make it easier for developers, then the new format would be more successful too. I just doubt that will happen, because they would have to spend valuable ressources on something which isn't 100% adding to their daily business. Not even sure who is responsible for VST3, and what they do in their daily job at Steinberg.
No band limits, aliasing is the noise of freedom!
- KVRist
- 323 posts since 19 Jul, 2008
-
- KVRist
- 487 posts since 21 Nov, 2012 from Sitting in front of my PC
I read through the license agreement.
The wording explicitly states the gender his when referencing the licensee.
So in the strictest legal sense does that mean I am ineligible to apply.
Kirsty
The wording explicitly states the gender his when referencing the licensee.
So in the strictest legal sense does that mean I am ineligible to apply.
Kirsty
- KVRAF
- 2117 posts since 24 Feb, 2004 from Germany
Let's sue them for violating gender equality laws! (if we can not do it for their software policy)kirsty roland wrote:I read through the license agreement.
The wording explicitly states the gender his when referencing the licensee.
So in the strictest legal sense does that mean I am ineligible to apply.
Kirsty