The long and short of it
My Lynx L22 audio driver is not agreeing with my OS, in my case Windows XP Pro SP3. The last software I installed before my recent woes uses PACE copy protection.1
My supposition and arugement
PACE copy protection software has somehow altered the fundamental workings of my operating system in such a way that is incompatible with my Lynx audio driver’s control software. I can’t say with 100% certainty that PACE specifically hosed my system; but I will say with 90% certainty, if not more, that it was this notorious copy protection that took me down.
The history
First, let’s step into the Wayback Machine: 2002, music tech writer Rip Rowan documents PACE kernel driver taking down his system. (This page was also written about the same time.) Obviously, ancient history in computer audio terms. I mention it here because this was written shortly after I had undertaken my journey into computer-based home production. Along with other DRM concerns happening at more or less the same time, it helped shape my software investing habits.
More recently, Adam Schabtach (1/2 of Audio Damage) took to his blog and chronicled his grief-by-PACE and vowed to boycott their products. That he is a professional in the audio software field gave the post a little more traction and punch than these things get. After being picked up by CDM it really began to take on the first whiffs of smoke.
(While looking to cure my problems, I also came across this. So computer audio musos aren’t the only ones who are occasionally taken down. Gamers are also another group you’ll frequently see dealing with PACE copy protection gone awry.)
PACE and Me
Sometime last week I was across town on Big Box Store Road, checking out the new Trader Joe’s. (Yes, I like it. Though no booze. Damn New England blue laws!) And so I stopped by the local MegaLo Guitar Mart and wandered around. (Yes I am a gear slut, even if I’m just flirting.) In the “Pro Audio” section in the “bargain”/used cabinet I was lured by fancy M-Audio packaging and what looked to be a good deal.2 And honestly, I did look to see if there was an a dongle requirement, or if it said anything copy protection; there wasn’t and it didn’t.
Also, a note on software packaging: boxes are fucking stupid.3
Anyway, during the install, after agreeing to the licensing and choosing my folders and it installing the dll and supporting files, up pops a PACE-branded window asking me if I want to register an iLok or via digital signing. Sure, kudos to the developer for the options, and he/they maintain the PACE digital registration is not a kernel-level driver. I am only reporting on my own experiences; draw your own conclusions.
In for a penny, in for a pound, I finished the install, and opened it up in Sonar in demo mode; I even generated my key to send for activation. But in a fit of indecision, I uninstalled the plugin while I deciding if this was a copy protection I wanted to invite myself in on, considering it’s history of randomly singling users out to f**k with. I was paying particular attention the PACE directories in the C:/Documents and Settings/. I figured an uninstall/reinstall will tell you a good amount about how any software reacts to your system in the long run. Unfortunately, I didn’t test how said uninstall would play out. In the same way I took a chance on the install, I took a chance that it would uninstall.
Friday night my friend/band Mark came over and we were plugging him in and I went to launch the Lynx L22 mixer, which is a direct access of driver, from the system tray. Sure enough XP decides to reboot. No BSoD, no error logs. Just straight to the BIOS resetting itself.
When it comes back on, Windows can’t find the device driver. Even after re-installing the latest driver package from Lynx, nothing. The L22 driver will not register, even manually, and the device sets to unknown in the system devices.
My guess, some other software I have uses some iteration of PACE driver digital signing, and the version this installer uses triggered or caused an instability or conflict, the direct result of which was causing my audio driver to become unstable. Something is happening at the core level of my OS that has caused or revealed a vulnerability with my audio driver.
I’ve tried all the usual recipes for bailing myself out of this. I’m relatively resourceful when it comes to operating Windows. I even managed, after a bit of mucking about, to use system restore to an earlier point, before I installed. Nope. For a brief second Windows remembered the Lynx, all it took was for me to launch the Lynx mixer to re-boot the system. Now it’s gone again.
I don’t need this headache.
Frankly, with the wealth of software out there, and the amount of time I’ve put into tweaking and fixing and upgrading my DAW, a piece of software better tickle my balls and freshen my coffee before I’m willing to put up with the aggravation of it fundamentally altering my system. And with all due respect to the coders, certainly not a VA VSTi. There are enough developers around that make quality software, at a reasonable price, or at least with a native copy-protection scheme, that I can make a stance that is both principled and practical.
I’m inclined to think is the last straw. Whether it was actively this PACE installer, or some other software, or even some other system driver falling over, I pretty done paying to be a beta tester. Now more than ever, I’m interested paring the system down to only what has historically worked, by and large, for me. What is the essential free/payware that I use on from session to session. Not the software I think would be cool to use; not the software everyone else thinks is essential. I will invest only in those products I know to be viable, support projects I think are worthy. I want my machine to be 128 track computer workstation. Sure it will crash, but at least I can limit the variables to a smaller pool.
Anyway, just adding my voice to the public record of what PACE iLok drivers can potentially do to your system. Like I said, draw your own conclusions.
–
1For the one or two people who might happen upon this that might not already know about it, PACE is a company that makes and licenses software copy protection. They make several different flavors of poison but they’re most known for their iLok USB dongle. They also have a pure software version that works by digital marking your machine and keeping track of said digital mark. Historically, the digital signing is invasive and clandestine.
An argument sometimes made in favor of PACE/iLok by users is that it somehow protects the user, making it simpler to recover from crashes, as if this somehow makes it more viable in the long run than other C/R systems. But as a whole PACE faults can be triggered by software/hardware changes you could make on your machine tonight, let alone 2 years from now. In fact, I’d go so far as to say that one of the biggest failings of any DRM system is that they are invariably *not* future proof. For them to be effective they have to continually be updated to maintain effectiveness. Dongles do not ensure against obsolescence, they insure that you don’t “loan” your copy out to your “friends.” As in, insurance for the company.
Companies need to keep track of how many users are out there - I will support those companies that to it with the least possible hoop-jumping and margin for error for me. While I find DRM to be a digital folly, I fully see the need for online registrations and activations. And, honestly, we’re not talking about Verizon or GE here - these are small companies with a comparatively small profit margins that count on the revenue from their products. They do not have huge corporate accounts like say, Adobe or Avid/Digi, to offset the rampant piracy of their software. Having some sort of digital signing or registration in place cuts down enormously on casual piracy - friends passing around software - installing, say, iZotope software on a buddy’s laptop. Unless you go primarily open source there is little way around it, esp. if you want to use a certain level of product.
But let’s not kid ourselves, there’s a lot of variables for error on a digital system, and shit happens. With any software, at some point you may just be SOL. This is why we’re all licensing software not buying it, right? Those EULAs we all merrily click through aren’t about protecting us, no?
2Out of respect for the producers of this software, because he/they genuinely seem like decent individuals who are interested in supporting their product, I’m not going to call it out the name. Obviously, distributed by M-Audio, a VA that’s not produced by GForce/GMedia. It seems like a fairly clever software, but, alas I will never really know. Also, it turned out to be not much of a bargain and more the standard going rate for it. So, impulse buy.
3This box contain a pamphlet “user’s guide” with a serial number sticker on it, and the CD tucked against the side. It would have fit easily in a envelope. Companies should just make one display box for a store, and then cut out all that stupid packaging.