KVR Audio

arakula · Post by **arakula** » Mon Jan 30, 2012 3:13 pm

How about contacting Steinberg support instead of trying to revive a nearly 19-month old thread?

rexone1 · Post by **rexone1** » Tue Jan 31, 2012 5:18 am

^I did. The e-mail address provided does not work either.

dentnile · Post by **dentnile** » Thu Sep 19, 2013 9:26 am

I'm having the same problem, the link for activating the account does not work. What is the solution?

dentnile · Post by **dentnile** » Thu Sep 19, 2013 9:28 am

Steinberg Support wrote:Hi everyone,

thank you for posting the troubles you are experiencing at the moment with the successful completion of the 3rd Party Developer account registration.

@Meffy: I have read your post on the mailing list as well, thanks for letting us know.

We are already aware of this issue which only affects a part of the accounts.
We are working on a solution.

In the meantime please drop us a short email at info@steinberg.de describing your problem (please include your username and registered email address) and we will set you up manually.

UPDATE: You may also try this workaround if you like before contacting us:
In the activation link you will see this part:
company/3rd_party_developer/sdk_download_portal

replace it with:
mysteinberg

Example:
The original link is:
http://www.steinberg.net/de/company/3rd ... g_pi1[hash]=... and the actual hash code

The modified link would be:
http://www.steinberg.net/de/mysteinberg ... g_pi1[hash]=... and the actual hash code

SECOND UPDATE: We have fixed the problem for any new users signing up for a developer account starting now (June 14th 2010, 2 pm GMT+1). These users will already receive the correct activation link.

If you have signed up before you can try the workaround or of course contact us.

Thanks and sorry for the inconvenience!

Best regards,
Sebastian

Steinberg Technical Support
________________________

I received the "fixed" link in my activation email. It does not work.

whyterabbyt · Post by **whyterabbyt** » Thu Sep 19, 2013 9:49 am

dentnile wrote:
Steinberg Support wrote:Hi everyone,

thank you for posting the troubles you are experiencing at the moment with the successful completion of the 3rd Party Developer account registration.

@Meffy: I have read your post on the mailing list as well, thanks for letting us know.

We are already aware of this issue which only affects a part of the accounts.
We are working on a solution.

In the meantime please drop us a short email at info@steinberg.de describing your problem (please include your username and registered email address) and we will set you up manually.

UPDATE: You may also try this workaround if you like before contacting us:
In the activation link you will see this part:
company/3rd_party_developer/sdk_download_portal

replace it with:
mysteinberg

Example:
The original link is:
http://www.steinberg.net/de/company/3rd ... g_pi1[hash]=... and the actual hash code

The modified link would be:
http://www.steinberg.net/de/mysteinberg ... g_pi1[hash]=... and the actual hash code

SECOND UPDATE: We have fixed the problem for any new users signing up for a developer account starting now (June 14th 2010, 2 pm GMT+1). These users will already receive the correct activation link.

If you have signed up before you can try the workaround or of course contact us.

Thanks and sorry for the inconvenience!

Best regards,
Sebastian

Steinberg Technical Support
________________________
I received the "fixed" link in my activation email. It does not work.

Then contact Steinberg.

aciddose · Post by **aciddose** » Thu Sep 19, 2013 10:29 am

It should be noted that after certain legal cases in both Europe and the United States you can download the headers required elsewhere and actually no longer need the "official SDK" or to enter any contract to build VST 2.x plugins.

You can find these available online as part of many open source projects.

Note also that even if for some reason a GPL header appears in these headers, the headers themselves containing only descriptions of the interface are not eligible to fall under copyright protection in either the European Union, United States or other locations where the legal precedent applies.

For example: http://www.google.com/search?q=aeffect.h

The "aeffect" struct and the headers containing other structs and defines/constants are all you actually need to create a VST 2.x plugin. Those do not fall under copyright because they describe an interface which can only be described in one way and so while the specification of the interface itself may be "creative", once it exists these headers are merely collections of facts and so do not fall under copyright protection.

There have been several cases but the landmark cases were Oracle v. Google in the US and SAS Institute Inc. v. World Programming Ltd in the EU.

http://en.wikipedia.org/wiki/Oracle_v._Google
http://en.wikipedia.org/wiki/SAS_Instit ... amming_Ltd

You have to get on some programming-related copyright mailing lists and read various news sources that carry this sort of thing to hear about what is going on legally.

dentnile · Post by **dentnile** » Thu Sep 19, 2013 11:07 am

whyterabbyt wrote:Then contact Steinberg.

That is a great idea!

From http://www.steinberg.net/en/support/sup ... ntact.html

EMAIL SUPPORT
In the countries/regions listed below, we provide a support request form for registered users in MySteinberg.

My problem is I cannot validate my registered account so I cannot login to MySteinberg to get any help with this. I fail to find an email address on their site, maybe I'm looking in the wrong place? Any ideas?

It is also not possible to PM the KVR "Steinberg Support" account that posted the fix here.

dentnile · Post by **dentnile** » Thu Sep 19, 2013 11:09 am

aciddose wrote:It should be noted that after certain legal cases in both Europe and the United States you can download the headers required elsewhere and actually no longer need the "official SDK" or to enter any contract to build VST 2.x plugins.

You can find these available online as part of many open source projects.

Note also that even if for some reason a GPL header appears in these headers, the headers themselves containing only descriptions of the interface are not eligible to fall under copyright protection in either the European Union, United States or other locations where the legal precedent applies.

For example: http://www.google.com/search?q=aeffect.h

The "aeffect" struct and the headers containing other structs and defines/constants are all you actually need to create a VST 2.x plugin. Those do not fall under copyright because they describe an interface which can only be described in one way and so while the specification of the interface itself may be "creative", once it exists these headers are merely collections of facts and so do not fall under copyright protection.

There have been several cases but the landmark cases were Oracle v. Google in the US and SAS Institute Inc. v. World Programming Ltd in the EU.

http://en.wikipedia.org/wiki/Oracle_v._Google
http://en.wikipedia.org/wiki/SAS_Instit ... amming_Ltd

You have to get on some programming-related copyright mailing lists and read various news sources that carry this sort of thing to hear about what is going on legally.

Thanks for that info! Would be nice to be able to do it their preferred way too though so still looking for help with activating the account. Thanks!

aciddose · Post by **aciddose** » Thu Sep 19, 2013 11:28 am

Well the preferred way while it technically avoids some potential legal complications it also requires you to agree to a contract which adds additional complications.

I was going to link to a project that implemented a clean-room version of the header you need but I'm unable to find that now...

http://en.wikipedia.org/wiki/Clean_room_design

I've seen several versions of what were claimed to be "clean-room" implementations but some of them seem to have disappeared recently.

If anyone wants to do a new one I'd be up for writing a specification. Would just need someone who has never been contaminated by the official sdk.

In fact it would be easy to just read the specification I write and write your own header in ten minutes.

dentnile · Post by **dentnile** » Thu Sep 19, 2013 9:16 pm

I have a solution.

On this page on this page http://www.steinberg.net/en/company/developer.html
...Instead of registering by "create a new Steinberg 3rd Party Developer account", first create a MySteinberg accound and then extend that to a 3rd Party Developer account. The activation link in the email for the MySteinberg account looks completely different and works.

aciddose wrote:Well the preferred way while it technically avoids some potential legal complications it also requires you to agree to a contract which adds additional complications.

I was going to link to a project that implemented a clean-room version of the header you need but I'm unable to find that now...

http://en.wikipedia.org/wiki/Clean_room_design

I've seen several versions of what were claimed to be "clean-room" implementations but some of them seem to have disappeared recently.

If anyone wants to do a new one I'd be up for writing a specification. Would just need someone who has never been contaminated by the official sdk.

In fact it would be easy to just read the specification I write and write your own header in ten minutes.

What additional complications, what I am missing?

aciddose · Post by **aciddose** » Thu Sep 19, 2013 11:24 pm

Did you bother to read the license terms when you signed up for the "developer" account?

dentnile · Post by **dentnile** » Fri Sep 20, 2013 12:48 am

Yes. Other than I have to send a signed copy of the agreement if I release something using VST technology I think it's pretty standard, no? What is the problem with it in your opinion?

VST SDK download impossible? [now with a fix, direct from Steinberg]