How Propellerhead’s New “Ignition Key” Authorization for Record Works
Propellerhead’s upcoming Record has attracted a lot of attention and discussion, but some of the forum chatter has centered on the new authorization scheme. Record will in fact use a hardware dongle as a key. Propellerhead obviously anticipated a response, as on their own site, they concede: “Wait – a USB device? You mean… a dongle? Are you insane?” But in the current description, and the teasers over the weekend, they also promised a “different” way of doing authorization – a promise that in the short term may have made people even more confused.
At the risk of causing a flame war, let’s at least look at exactly how the authorization works. Authorization is, of course, always annoying to paid users on some level, and I expect some of you will still be unhappy with the USB key approach. Looking at it on balance, there are some advantages in certain situations, when compared to software-only authorization, and disadvantages in others.
This is a preview only of a non-shipping product, based on information Propellerhead has shared and my own experience. It’s also not intended to be an opinion piece; I just want to look at the big picture in the hopes that the online discussions can be better-informed.
First, to clear up a misconception: the authorization does not slow down boot time. In fact, Record is one of the fastest-booting audio apps I’ve seen. (Note: any comment about performance is just speculative, as we don’t have a final build yet. But this is partly objective; remember, by not supporting plug-ins, Record doesn’t have to slog through your plug-in folder, something you can leave to other tools.)
The first time you load Record, you’ll see something like this if your USB key isn’t plugged in:
/* Buy links if custom fields not null and not in cat or search results */ ?> /* End Buy links if custom fields not null and not in cat or search results */ ?>







