Quote:
Originally Posted by
undertone
โก๏ธ
iLok is definitely an expense for the developer that uses it. I've read this many times and from developers themselves. For exact costs you have to contact iLok, prove you're a developer and ask for this information.
Feel free to post actual numbers or links to real information you've seen on this. Until then, the jury will remain out on just how significant an expense it is. I personally have no idea, as it could be anything from a nominal one time fee, to crippling ongoing royalties. You'll have to be more specific though if you feel the expense is relevent.
Quote:
Originally Posted by
undertone
โก๏ธ
If iLok 2 works, all the better. I have two myself because I want to run the software they protect, not because I like the iLok. I'd much rather just deal with serial numbers, but I do understand why iLok exists. I don't think a lengthy iLok discussion belongs in this thread.
Seeing as how it's my thread (I'm the OP), and it's a big part of the topic I've raised, you don't really get a vote.

It's a huge part of this topic, and of any discussion on plugin licensing.
Quote:
Originally Posted by
undertone
โก๏ธ
Things that bug me about re-installing music software:
1. Software that don't allow you to cut and paste the complete serial number, or only allows copy/pasting of smaller groups of letters. Why?
Me too. Very annoying. Not an issue with iLok, thankfully.
Quote:
Originally Posted by
undertone
โก๏ธ
2. Software that you can't get authorized because they use challenge-response and the company has gone out of business. BTW, if your iLok holds licenses for companies that no longer exist and your iLok dies, can you get those licenses back?
This is a total non-issue. Here's why: If a plugin company has gone out of business, then regardless of whether or not you can still get your licenses back at the moment, you have to eventually face the reality that one day those plugs will no longer work. The OS and DAW will move on with newer versions of their software, and you will eventually upgrade your hardware. You will do all of this to stay competitive, and because eventually they
all will become outdated and stop working, unless you update them.
Using plugins means maintaining an ongoing relationship with those companies. If they go out of business, it's just like finding out that the studio you mixed a project in no longer has a certain piece of gear. Who cares if you can't do an exact recall of that mix in 5 years? If the sound of that plugin was
that unique/critical to the mix, you should have printed it. Otherwise, it's just a tool like many others, and you'll find a adequate substitute if need be.
Quote:
Originally Posted by
undertone
โก๏ธ
3. Companies that change their website so all your old links to software downloads are no longer valid.
Any legit plugin company should be maintaining a website that is easy enough to navigate so that it's as simple as logging in and downloading the most recent version for your system. I never trust old links, as even if they work, there's often a newer version that I ought to be using instead.
Quote:
Originally Posted by
undertone
โก๏ธ
4. Companies that change the authorization system on you, requiring you to get a new installer and possibly a new authorization code or serial.
All the more reason for an industry-wide standard to develop (like iLok) where you can handle all of your authorizations in one place.
Quote:
Originally Posted by
undertone
โก๏ธ
5. Companies that require you to log in before you can download your installers. Especially troublesome if you don't visit them often and you've forgotten your user name, password, or both...
I agree with you there. I think the only reason for this though is to take yet another step towards fighting piracy. I guess it makes it that much harder for would-be crackers to access an installer. Hopefully with a better iLok (2), they won't feel the need to restrict access.
Quote:
Originally Posted by
undertone
โก๏ธ
6. Companies that don't label software version numbers in their installer names. Now this one I really don't get and it's very annoying!
Agreed... But, if you just go download the current installer specified for your system, it's a nonissue.
Quote:
Originally Posted by
undertone
โก๏ธ
7. Installers that don't tell you EXACTLY what folder they're going to install to and don't tell you if they'll be installing on that folders root or within another folder. Some installers will let you point to your plugin folder, and then either install the plugin in several nested folders within the folder you chose or in the root of that folder, which can get messy if many files and subfolders are involved. Look, it's really simple: let me install the plugin within the path I chose, show me the complete path the plugin will be installed in, and tell me if you'll be installing a bunch of files, a folder, or just a dll... it would be nice to know in advance .
Hmm.. I haven't run into that much. Most of the installers simply put the plug or a folder of stuff in the plugins folder. There are exceptions (like Waves) that put a Waves folder in you applications folder, but I haven't found it that bothersome. Full disclosure, I'm running PTHD9.0.5 on a Mac- maybe it's different in Windows world?
Quote:
Originally Posted by
undertone
โก๏ธ
8. Installers that insist on installing a whole suite of plugins when you've only purchased a license for one of them, requiring that you spend time uninstalling the ones you don't want. Devs, please keep promo out of your installers!
Yeah, that's obnoxious. Who's doing that?
Quote:
Originally Posted by
undertone
โก๏ธ
9. There should be a standard way that documents for software is installed. Sometimes they're included in the installer home directory in Program Files; sometimes they're installed in the VSTplugin folder along with the dll; and sometimes they're nowhere to be found and must be downloaded as separate files from the dev's site, and then you're not sure where to put them.
I guess that answers my question above about what platform you're on. Seems like things are a bit messier with VST and Windows.
Quote:
Originally Posted by
undertone
โก๏ธ
10. Companies that require you to have an active paid subscription to their support system for ANY installation issues you may be having with some of the older versions of their software; otherwise you're dog poop.
I think this hits on a much bigger issue surrounding the nature of plugins, licensing, and payments. We don't "own" these plugs, and they don't come with a warranty that says they'll work flawlessly on all future systems. I can understand that keeping them up to date does cost the companies time and money, and that it's reasonable to charge a
modest update fee from time to time. However, it's also very much in the hands of the plugin developer, and DAW/OS developers how MUCH has to be changed to make the next incarnation work, and I don't support paid updates just for the hell of it, or because they added some silly new "feature" to justify the charge. Getting off topic, but Quickbooks is one of the worst offenders I've ever seen when it comes to planned obsolescence, and forced paid updates with overblown new "features" that really are just facelifts. But I digress...
Quote:
Originally Posted by
undertone
โก๏ธ
I have to admit that the re-installation of iLok protected software is easier because it bypasses most of the re-authorization issues.
Yes!
Quote:
Originally Posted by
undertone
โก๏ธ
However, it also is a one-software/one-machine model of software licensing that I profoundly disagree with; I believe in the one-user model. Serials and challenge/response are more of a hassle on installation, but the freedom of use gained by them is immeasurable.
Huh?

You've described exactly the
opposite of the iLok model. The iLok model
is a "one-user" model. If I need my plugs to work at another studio, I just take along my iLok, run the installers when I get there (if they're not already installed), plug in my iLok, and go! Challenge/Response would be
so much more time consuming in that situation. In fact, the One User/ Many Machines aspect of iLok is one of the best parts about it.
The overwhelming majority of my plugs already use iLok; I just hope they can get the remaining bugs out with iLok2. FWIW, I'm now running an iLok 2 (as of about a month ago), and I didn't have a single problem with authorizations on any of the well over 200 plugs that are using it. I just wish the whole reinstallation process didn't take so damn long. :