Notifications
Clear all

New computer installation is a PITA

9 Posts
2 Users
2 Reactions
111 Views
mschiff
(@mschiff)
Member
Joined: 4 years ago
Posts: 455
Topic starter  

My DAW computer died last week, so I got a new one. The hard drive was fine, and I found a great program that allowed me to transfer everything from the boot drive (Windows 10) to the new computer (Windows 11), including programs. So I was in fat city. It worked a treat, and most of my VSTs worked, except for Unify. I sent a message to support, and Taylor very promptly replied that he had reset my Unify registration counter, so I thought I was again in fat city. But NOoooo. I tried a few libraries and no sound. Not only did I have to reauthorize Unify, but also the 30 libraries that I had purchased that required authorization. So I spent another 40 minutes searching the website for the codes one at a time. (BTW Shane, the auth lock icon is very helpful for that). I know that you need to protect your libraries from piracy, but there MUST be a better way than that. 


   
Quote
(@getdunne)
Illustrious Member Admin
Joined: 5 years ago
Posts: 4437
 

I will speak with Taylor. He should have been able to send you all of your authorization codes and an XML file for each one, to trigger the authorization dialog.

I'm working on making this almost completely automatic for a future release of Unify, but this will take some time.


   
ReplyQuote
mschiff
(@mschiff)
Member
Joined: 4 years ago
Posts: 455
Topic starter  

Thank you, Shane, (and Taylor). Had I known that this was an option I would have asked Taylor when he responded by resetting my Unify authorizations. Actually, when I emailed him about re-authorizing Unify, I had not tried any of the sound libraries yet as Unify was not working without the authorization. I guess he did not realize that I would have to do that as well. I didn't find out that it was needed until I tried to play some of my libraries and got no sound. All the libraries were there, but the ones that require authorization did not play.

As a programmer, I realize that this is not trivial to do, so I understand that it will take some time with everything you have on your plate, and all that you do is greatly appreciated. 

Taylor did mention this to me in an email today, and he has been very responsive. I am very pleased with Unify and the support. 

Hopefully, I will not need to use another new computer for MANY years, so I hope not to need this again. But for others, I am sure it will be appreciated.

Anyway, everything is working properly again, and I am a happy camper. Since I use Unify in every piece I compose, I guess 40 minutes was not much to spend for its fantastic benefits.

I should mention that I had to re-authorize a number of my other VST libraries as well, but most of them was a matter of just opening their installation software and clicking on a button for each of their libraries. The only other one that was kind of a pain was Spitfire. I had to run repairs on all of their libraries, even though they were still there and in the proper place. Since I now have 3Gb internet service, and a 2.5Gb NIC card in my DAW, I was able to run the repairs on the numerous libraries I have from Spitfire (hundreds of gigabytes) in a very short time comparatively.

One thing I realized, is that I am addicted to purchasing VSTs, and I need to think more clearly about buying more until I have used the ones I have.

FWIW, I also had to reinstall PACE software's ILOK manager as well. It was telling me that my key was not installed, when it was clearly working. I almost bought another one thinking it was somehow broken, but by reinstalling the software (even though it was already there and working), it worked perfectly again.

One suggestion about the authorization process. It would make sense to blank out the authorization code after a successful authorization. At first, I did not realize that the paste button would do that, and I was selecting and deleting the code so I could paste another one. I can't think of any reason that the code would be needed in that control after a successful authorization.


   
getdunne reacted
ReplyQuote
mschiff
(@mschiff)
Member
Joined: 4 years ago
Posts: 455
Topic starter  

@getdunne Maybe I am misunderstanding you, but triggering the authorizations was not a problem. Your licensing icon does that beautifully. Each time I click it, the next library needing authorization automatically goes into the authorization process for the next unauthorized library, until there are none left. It was just looking up the auth code for each one and pasting it that took the time.


   
ReplyQuote
(@getdunne)
Illustrious Member Admin
Joined: 5 years ago
Posts: 4437
 

@mschiff

The XML files are needed to trigger the authorization procedure.

The licensing icon only appears if XML files are present, and the specific XML files are used to populate the list of libraries needing authorization.


   
ReplyQuote
mschiff
(@mschiff)
Member
Joined: 4 years ago
Posts: 455
Topic starter  

I don't know where the XML files could have come from, as I did not download anything, nor did I ask Taylor for them. However, each time I clicked on the licensing icon, it brought me to the licensing page for another unlicensed library, until all of them were licensed and then it said no more to license. It's still there on the stand alone version interface.


   
ReplyQuote
(@getdunne)
Illustrious Member Admin
Joined: 5 years ago
Posts: 4437
 

Posted by: @mschiff

I don't know where the XML files could have come from, as I did not download anything, nor did I ask Taylor for them. However, each time I clicked on the licensing icon, it brought me to the licensing page for another unlicensed library, until all of them were licensed and then it said no more to license. It's still there on the stand alone version interface.

Did you install the libraries using .guru files? If so, the XML files were included there. You should only need to place the XML files yourself if you copied the library folders from your old machine.

 


   
ReplyQuote
mschiff
(@mschiff)
Member
Joined: 4 years ago
Posts: 455
Topic starter  

I installed the libraries on my original machine using the .guru files. The computer died, but the boot drive was fine. I used software called Zinstall Migration Kit Pro that was able to copy the hard drive, connected to a USB SATA adapter, from a Windows 10 drive with programs and everything associated with them to a new Windows 11 computer. It copied all the files and installed them so that the programs worked on the new computer. All my icons were on the desktop, settings, etc. It wasn't flawless; I did have to reinstall some programs to get them to work 100% properly, but it was far better than having to install everything (all my VSTs, and I have hundreds) from scratch. Unify worked just fine, except for the authorizations. 

I was pretty gob smacked at how well it worked.

 


   
ReplyQuote
(@getdunne)
Illustrious Member Admin
Joined: 5 years ago
Posts: 4437
 

@mschiff

Ah, I understand now. ZInstall would have copied your Unify.settings files, which included all your old licenses. These were invalid for the new PC, so you would have been prompted to re-authorize them.

It's been so long since I worked on that part of the license management code, I had forgotten that it worked this way.


   
mschiff reacted
ReplyQuote
Share: