![]() You will not be able to properly activate your new product without access to the old license. If you don't already have a Steinberg Shop account, you can create one during the checkout process.Īlso, make sure that you have Steinberg eLicenser Control Center installed on the computer where you plan to run Cubase 12, and that the Cubase license you plan to upgrade is available. You only use the Steinberg Shop for eCommerce transactions (paying for new purchases, updates, or upgrades), while you use your Steinberg ID for everything else (downloads, activation, forums). If you use different passwords for the two sites (like I do), make sure you have both. Your Steinberg shop account is separate from your Steinberg ID/MySteinberg account. If you have ever used the Steinberg Shop before, you will want those credentials on-hand as well. ![]() ![]() You can confirm your credentials by logging into the Steinberg Sign In page. Have your Steinberg ID credentials handy, because you will be logging in to various Steinberg sites and apps along the way. Prices vary depending on the product you're updating/upgrading from- if you are a long-time customer you might have multiple possible choices, so be sure to review all your options. In Steinberg's terminology, an "update" is when you move from an older version number to the latest version (in our example, 7.5 to 12), and an "upgrade" is when you move from a limited flavor of Cubase to a more full-featured one (for example, upgrading from Cubase Elements to Cubase Pro). ![]() Several Steinberg products sometimes come in different flavors (Pro, Artist, Elements, AI, LE) as well as different versions (1-12). I hope to clear up some of this confusion with my complete walkthrough of the update/upgrade process. This is partly because Steinberg is transitioning from their controversial USB eLicensers to their new Steinberg Licensing copy protection scheme, and partly because the update process is complex, involving many steps across a number of apps and web pages. It also means that plugin developers can fix the mess they have already made using different UIDs for VST2 and VST3 without breaking backwards compatibility.ĪLL of this requires the plugin developer to implement it - it’s not a ‘automatic’ thing.Ever since Cubase 12 launched, every Cubase-related message board and Facebook group I visit is full of owners of prior Cubase versions struggling to update their rigs to version 12. Although currently I can only think of NI Kontakt that this VST3 equivalence might be useful for…and that’s because the made a bit of a mess of the plugin name. The latest VST3 SDK means that the plugin developer has more options to tell Cubase/Nuendo that the plugin is an equivalent, not just VST2 > VST3 but also from different version of VST3. It’s possible/probable that those same developers will keep making life difficult by not implementing this new(ish) VST3 feature. Some plugin developers don’t do this unfortunately…and it’s annoying. In fact you’ve probably noticed that if you have a VST2 and the same plugin in VST3 that cubase ‘hides’ the VST2 plugin from you (in most cases!) Most developers used the same UID for VST2 and VST3 and so the transition should have already been seamless. This was already available and working fine in most circumstances. It would make it easier for us to replace older VST2 versions of plugins with newer VST3 counterparts - correct? ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |