iLok looks to be optional now with Soundtoys

[Lesha]

How widespread is this issue for other devs? I've never had a problem with uhe and iLok and I use both all the in my work. I'd love it if uhe products were iLok as well. Machine auth is too risky and annoying to me.

Two other devs I am in touch with know about this problem.

[Urs]

How widespread is this issue for other devs?

It gets reported to us several times a year. We do not know about the incidences where people do not report it.

I've never had a problem with uhe and iLok and I use both all the in my work. I'd love it if uhe products were iLok as well. Machine auth is too risky and annoying to me.

We don't do machine authentication. We use simple serials. If you lose them, you can retrieve them from our website. Built-in zero downtime at no extra cost.

[plexuss]

We don't do machine authentication. We use simple serials. If you lose them, you can retrieve them from our website. Built-in zero downtime at no extra cost.

As a musican and customer I don't care about the tech. What I care about is a system where I can spend the LEAST amount of time recovering my tools if I have a catastrophic system failure that breaks authentication. Sounds like your system and iLok meet those requirements. Too bad so many other's do not...

The last time I had to go through I remember that your products re-authed on the new machine with no issues, just enter the serial. Great! Also all my iLok dongle protected products required 0 effort. iLok has saved me much time and frustration.

[RobGee]

Lol at all the iLok haters, install software, plugin iLok, done…

I think I’ve had one issue with it in the 10+ years I’ve been using it.

We have recently found out that an issue that users have reported for many years was related to iLok. Randomly, projects would not open because our plug-ins - which are not iLok-protected - would crash. What happened? Users had an iLok protected plug-in in the project and the host would load that plug-in right before our plug-in. And the iLok software would somehow corrupt the memory that our plug-in was living in, and then our plug-in crashed. This also happens with plug-in of many others. No word from PACE if this was ever addressed or ever will be.

I applaud Soundtoys for moving away from this thing.

Never had this issue and I’ve used multiple ilok and U-he products for years, infact the only time I’ve had U-he products not load was because they don’t support vst2 to vst3 migration

[HcDoom]

Only bad thing about the iLok is too high license transfer rate.

[plexuss]

Only bad thing about the iLok is too high license transfer rate.

Something to consider: $25 is close to PA's $20. Most iLok licenses and transferrable as well, unlike "most plugins" in general with are plaqued by NFR restrictions. Granted the fee is not $0 or even $10 but the iLok transfer policy and fee are, IMHO, an ok comprimise. So... a different opinion, as to be expected.