I've had no trouble with Unify on my main music computer. My PluginGuru account show that the license has been authorized once, with two additional authorizations available. But when I installed it on my laptop and cut and pasted my license number in response to the prompt, it said the license number is invalid. The laptop is running Windows 10 with the latest updates and has no (other) trouble with my internet connection.
Has anybody else encountered this problem? Does anyone know the solution? Thanks in advance!
It's authorized now. The only thing I did differently was to cut and paste the serial number from the PluginGuru email rather than from my account page on the website. It's possible that the website HTML code embeds some invisible characters that make the string invalid even though it looks find on the page.
The software we use to drive the pluginguru.com web site generates codes for things like payment confirmations, which look very similar to license codes, so it's easy to get them mixed up. We hope to make this less confusing eventually, but it's not our software so it's a challenge. I'm glad you got it figured out.
@getdunne, the license key I copied and pasted from the website looks identical -- character for character -- to the one I copied and pasted from the email receipt. The second one worked, the first one didn't. And my hypothesis about embedded HTML code is wrong. Using the "view source" function of my browser shows that the license key doesn't have anything embedded in it. I still don't know why it failed one day and worked the next.
Thanks for clarifying. I'll bear this in mind and be on the lookout for anyone reporting a similar issue in future.
There were major issues with PlugInGuru.com around then, due to a server migration, which could have caused such temporary failures.
@getdunne, if "around then" refers to Friday or Saturday (I forget which), then that's a very likely explanation. Thanks!
@getdunne, if "around then" refers to Friday or Saturday (I forget which), then that's a very likely explanation. Thanks!
Yep, that was it. Issue started on Friday and was not fully resolved until mid-day Saturday.
Thank you for this post. Getting ready to do the very same thing myself. Main PC for recording and my Surface Pro for live performance.