A Pro Tools HD 11 system on a Windows 10 laptop started taking about 10 seconds per track to load sessions after an iLok License Manager upgrade, and deactivating duplicate Slate Digital licences in iLok brought that down to about a second.
My client runs Pro Tools HD 11 on a Windows 10 laptop with a lot of plugins, many of them licensed on his iLok. A lot of them are Waves and some are Plugin Alliance. When you have that many plugins and licences depending on each other, a setup that opens and closes without problems and runs smoothly is in some ways the holy grail, and he had one. Then he installed an upgrade to iLok License Manager, I think so he could install some new plugins, one of which was Slate Digital’s Virtual Mix. After that his Pro Tools sessions were taking an age to load.
When I looked at his system I could see each track was taking about 10 seconds to load. He’d already tried a few things himself, such as trashing his Pro Tools preferences and moving his Waves caches, and none of them had made a difference.
Looking at his iLok licences
My suggestion was to look at the information in iLok License Manager, where we could see which licences he had. There were a number of older Slate Digital licences on his system. He’d bought some of those plugins originally and then moved to a subscription for a wider pack, which seems a perfectly reasonable thing to do. My hypothesis was that Pro Tools was taking longer to load because it was finding three licences for those plugins rather than just one.
- Checked which licences were on the system in iLok License Manager.
- Deactivated the unused licences, both in the iLok cloud and on his physical iLok key.
Once he’d done that I was pleased to see Pro Tools loading much more quickly, at about 1 second per track.
The older Waves plugins
My client said it still wasn’t as quick as it used to be, so I experimented further to see if other plugins had licensing problems or duplicate licences, or if there was some sort of conflict elsewhere in the system. We thought Waves was quite likely to be causing problems, because we could see the Waves icon spinning on the Pro Tools loading splash screen, which showed there was some sort of slowdown there. I then noticed his Waves plugins were version 9, an older version, so I think Pro Tools is probably having to access some legacy code to load them.
It’s frustrating that it’s one particular brand of plugins causing the problem, but it is where it is. A lot of my clients are invested in the Waves system, and keeping up means paying for upgrades, which I think is quite painful for them.
My next thought was to experiment with the Waves folders, and we updated one of his plugin licences to V10. After that I was a bit concerned about disturbing too much more of his ecosystem, so we left it there. We’d brought the loading time down and his sessions are now more usable.
Why it slowed down in the first place
Unfortunately I can’t say exactly what happened. My guess is that installing the new iLok License Manager, or something else installed around the same time, introduced some modern code into a legacy system, and it’s causing problems in ways I haven’t pinned down. I think it might be something in the C runtime, and with more research we could probably find out.
Windows 10 is no longer supported by Microsoft, so with a setup like this we may be dealing with a sinking ship.
If you’re running an older Windows 10 system that you can’t afford to have stop working, I would strongly recommend not installing new plugins or any new software on it, unless you’re ready to upgrade the whole setup.
Not sure it’s the same problem? Ask a question first
