Wave Lab Go 13 instead of Wavelab Pro 13

WaveLab
1

Hi,

I just upgraded from WLPro 12 to WL Pro13.

All fine in my My Steinberg account - SDA has downloaded and installed Wavelab Pro 13 - but when I run the app I get Wavelab Go?

  • System spec in my Bio

Any thoughts?

2

Did you activate it in the SAM (Steinberg Activation Manager)?

1 Like
3

OK - I ran it a second time and got the ā€˜import WL12 settingsā€™ dialogue and WL Pro 13 has loaded correctly.

Weird?

4

Yeah - just needed to run it again - all fine now

1 Like
5

Your lucky, Iā€™ve run it twice and it still only gives me WL13. What a drag.

4X now and itā€™s still not updating to 13 Pro. You would think Steinberg wouldā€™ve had this under control before they released it. I can only hope the WL Pro 13 program works better than the Steinberger Downloader program.

6

There is another thread here that says you need to use Steinberg Activation Manager as well as just the download and install with Steinberg Download Assistant:

I didnā€™t need to do this, but this may be your answer?

7

Downloaded to my MacBookPro no problem but needed to restart WL13 twice for it to switch to Pro mode, however my Mac Studio needed downloading from Steinberg Download Assistant then activating using Steinberg Activation Manager. Not sure why 2 different methods are needed!!

8

The Download Assistant is exactly doing what the name implies, it downloads and installs the software.

The Activation Manager is responsible for activating your license. Usually the Activation Manager is set to Automatic License Management, so that you do not need to open it. But if the license is not automatically detected you can simply start this tool and click on Activate yourself.

9

Wavelab 13 is a multi installer for Wavelab Go, Wavelab Cast and Wavelab Pro.

It boots the first previous licensed version of those it finds, Subsequent boot find the next.

Happened to me with Wavelab Cast, booting that before Pro.

David

10

In how many threads do you want to add the same wrong info.

First of all a reboot of the computer is completely irrelevant to the license activation.

The license is controlled by the Activation Manager, after entering the Download Access Code in the Download Assistant. You can read how the Activation works here.

11

My observations are what I see. I am familiar with Activation manager workings.

What is frustrating to me as a user just intending to updating WL Pro 12 to 13 is

1: No clarity that the Wavelab 13 is a multi installer doing more than Iā€™m asking for.

2: The previous versions of the additional app in the multi installer GO which I donā€™t use and WL cast 13 are separate and distinct apps.

Activation manager shows only 2 licences for me WL Cast 2 and WL12 pro pre upgrade and WL Cast 2 and WL Pro13 post upgrade.

But the first screen presented after the install of WL 13 was meant to be WL 13 Pro not WL cast 13. I am not the only user confused by this so this is lack of clarity in the installer as to what it is doing.

Also had it confirmed that WL 13 installer changed some preference files for my existing WL cast install which stopped WL Cast 2 opening. Clearing the WL cast 2 preferences fixed that.

So auto installer with WL 13 has introduced an issue with WL Cast 2 and confused with lack of clarity.

David

12

FWIW, when I purchased the update from WL12Pro to WL13Pro, I got these instructions emailed to me, which I found rather clear, and which worked immediately without issue:

Follow these steps to download, install and activate

  • Download and install Steinberg Download Assistant for Windows or Mac if it is not already installed

  • Launch Steinberg Download Assistant and sign in with your exiting Steinberg ID or create one

  • Click on ā€˜Redeem Codeā€™ and enter the Download Access Code(s) shown below

  • Select the software under ā€˜My productsā€™ to get a list of download options on the right

  • Click the Download or Install/Install all button to continue

Iā€™m not trying argue or otherwise take away from your poor experience, but from a transactional and technical perspective, everything worked exactly as intended and expected for me. There may have been something else on your end going on. From my observation, all of the ā€œGoā€ issues Iā€™ve seen have been people just forgetting to activate the software after downloading it. Again, just FWIW.

2 Likes
13

This occured to me, but upon starting WL13 (Pro), Iā€™ve been asked to activate it first. I did not read the steps and nevertheless everything worked like a charmā€¦

1 Like
14

For me every step followed as per the list you highlighted. But the install of the Wavelab 13 which was intended just to update WL Pro 12 to WL Pro 3 did two things I did not expect.

1: On install completion it opened automatically as WL Cast 13 not WL Pro 13. I did not invoke WL Cast.

2: I discovered WL Cast 2 my existing version would not open.

Item 2 was caused by the WL 13 install (being a multi installer for GO, Cast and Pro) updating the preference settings for WL Cast as they are apparently shared between WL Cast 2 and WL Cast 13. The change to those files stopped WL Cast 2 opening. This was brought to my attention by PG.

My comment to your post about GO was simply alert you to this multi installer position as itā€™s invisible. I had no idea the install was hitting files outside of WL Pro 12. When I discovered what was being changed the solution became visible. If you fail to activate prior to install the installer prompts that prompt did not appear before Cast 13 opened automatically but did when closed and I actually invoked WL 13 Pro. So like others I wondered why WL Cast (or in your case GO appear to be invoked)

Anyway problem solved. The standard installer does not inform the use of the multi install situation as far as I could see. Given confusing users generates support queries its something Id have thought Steinberg would like to avoid.

Was just trying to be helpful in sharing my experience on this install.

David

1 Like