MacBook apps shows following install names 1: Wavelab 13.app, 2: Wavelab Pro 12.app and 3: Wavelab Cast 2.app) Im assuming the Wavelab 13.app is the full Pro version new name.
How do I fix this error so I get the correct WL 13 Pro start screen?
David
Update observation:
Found how to fix so my question is really about why did the WL 13 Cast screen appear and not the WL 13 Pro screen when installing the update.
Id guess it relates to install processing order checking. (Given the logic of programming may not expect to find Wavelab Cast 2 and WL Pro 12 on the same machine). I assume WL 13 now fully includes Wavelab Cast function as it’s more integrated than the previous WL Pro 12.
So simply seeking peace of mind on the logic used at install and any potential impacts of the potential logic fail. Clearly the Wavelab Cast window should not have appeared first.
No the activation was done first on the first install on the Intel Mac which worked ok. So the second install should have identified the product licence already activated when it was being installed but it appears it didn’t. The download manager was used to download wavelab on the second machine laptop after it was already activated.
To add to @JuergenP’s correct info, this is a GOOD THING. You don’t have to make outbound internet calls for licensing verification this way. Each machine has its own local, licensed copy. No phoning-home, no service daemons, no iLok, etc. Great stuff in my opinion.
That indicates that the Initial Wavelab Cast 13 window can be presented without the Wavelab 13 app being activated. The laptop machine did have the Wavelab cast 2 already activated so perhaps that licence allowed the Wavelab cast 13 elements of Wavelab 13 to work.
When I exited that initial window and reinitialised Wavelab 13 I then got the authentication prompt for Wavelab 13 after that authentication the install process continued as expected.
So it appears the screen presented and Wavelab 13 cast was because of an existing Wavelab Cast 2 licence.
The implication here indicates If a licensed Wavelab cast 2 users can get the Wavelab 13 app without a download code they get Wavelab 13 cast as a free update.
You need to enter the Download Acess Code once on one of your machines to register the license in the Steinberg system. Now you can start the Activation Manager on up to three machines and activate the license, as long as the Activation Manager is logged in with thecsame account.
If you try to activate a fourth machine or using a different mail id the license is denied.
My account has WaveLab cast 2 and wavelab12 Pro already licenced at Steinberg and activated on my 3 mac computers.
I downloaded wavelab 13 and activated on 1 machine.
I downloaded to machine 2 but did not activate prior to install on machine 2,
After install Wavelab cast 13 was presented without any addition activation on that machine of Wavelab Cast or Wavelab Pro. So only WaveLab Cast 2 is shown in Activation manager at the time Wavelab cast 13 was presented for use.
On second boot of Wavelab 13 the WaveLab pro 13 activation prompt was then presented.
Clearly I could run Wavelab Cast 13 after the first install. But perhaps as I got the activation prompt window on second boot if I failed to activate then I would be locked out from Wavelab cast 13.
Whilst I was concentrating only on Wavelab pro 13 activation I hadn’t tested my Wavelab cast 2 boot. Just discovered that now fails to boot despite the licence correctly show as activated alongside WL Pro 13 in activation manager,
So I have another issue to investigate and resolve. WaveLab Cast 2 not opening and the error prompt is pointing me to report error to Apple so an OSX related compatibility crash.
The reason is probably the following one.
If you have run Wavelab 13 in “Cast mode”, then some the Cast settings have overwritten to the WaveLab 13 format.
Now, if you run the WaveLab Cast 2 (which is based on WaveLab 12), then you will experience a crash.
Therefore, you have to reset your preferences.
In the future, you have to either run the “old” WaveLab Cast or run WaveLab 13 in Cast mode.
Just reinstalling now. I did note some file dates looked like they had changed to recent in preferences despite me not having run cast 2 for a while, so that probably the issue.
