This is why Steinberg requires the physical eLicenser for Cubase Artist/Pro (which hasn't been cracked since v5).įor those companies, not using Physical iLok is like you renting an apartment and the landlord requires you to hang the keys on the outside of the front door. I honestly don't know how most people can get away without having at least the Soft iLok installed on their machines ?Ĭompanies with some of the best plugins on the market routinely require the physical dongle, as hardware copy protection is a lot harder to crack than software. but, copy protection is pretty run of the mill for commercial audio products. If you're the type of person who's been using mostly freebies, iLok may seem shocking. Most people who do music production have either iLok License Manager or a Physical iLok dongle, because so much requires it. If I was smart I would have just converted one plugin to iLok and tested it out first but I didn't, like most people I've got multiple things competing for my time & attention and I just wanted get it done so that I could move on to the next thing unfortunately I didn't imagine that iZotope would do iLok differently than everyone else does. So now I'm looking at spending an unknown extended amount of time individually authorizing all my current iZtope plugins via the Product Portal and the olders one using SaviHost or something similar. I just didn't feel like going through the process of grabbing another screen shot).īTW all my other iLok plugs are working fine. (yes image shows Nectar 2, same thing happens with Nectar 3 and the rest of my iZotopes. **iZotope's implementation is different than other vendors as in addition to authorizing on the iLok you still have to authorize each plugin on each machine you will be using them on.Īs shown in the image below from the iZotope Product Portal - the plugin is authorized to iLok but still requires computer authorizationĪnd when you fire one up. I've contacted iZotope support and they've said basically (to paraphase) "Yup, that's the way it works." Even with iLok you still** have to manually authorize each plugin and if you engage the iLok option on an existing system using iZotope plugins you'll have to reauthorize each iZotope plugin again. Planning on getting a new computer I thought that going the iLok route would make my iZotope migration fairly painless - as using their Product Portal takes most of the pain out of the installation and it's the authorization process that the real pain (having to click past multiple screens for each individual plugin).īut. (if that one does not work it would be a surprise.).Heads up on iZotope plugins if you're considering engaging the iLok option.ĭon't, unless you're going to be using it on multiple machines (as with studios or clients) that already have the iLok licensing authorized/activated for the individual plugins.īeen using iZotope for ages and after going through several different suite upgrades now have over 100 of their plugin haunting my system.
Try reinstalling Vinyl again.ĭo a full clean Windows install on a spare partition, install ILM and Pro Tools and nothing else and try again with Vinyl there.
Reinstall ILM and Pro Tools and minimal audio driver needed, nothing else. Uninstall all Windows C++ runtimes packages etc. Uninstall ILM and Pro Tools and all plugins. Removing all plugin files from the plugin folder, restarting Pro Tools, letting it put back the standard plugins, then installing Vinyl again. I think all basic troubleshooting has been tried right?Īnd all I could think of doing there is. That is why iZotope are likely the only folks who can really help here, and they may just not be able to get far without being able to reproduce the problem in-house.
That is where things are failing, in the low-level initialization/licensing code for that. aaxplugin files and tries to load/initialize those plugins at startup. Did not workĪnd it should not have been expected to. I cannot try "offline authorization" because i cannot even get to the autorization page.