December 26, 2013


by Chris Randall

As you no doubt know, especially if you are a Logic user, there are Big Changes coming down the pike, in the form of a sandboxed version of Logic, most likely before the middle of 2014. Developers have been given a preview copy of Logic X Sandboxed, so we can test our products to see if they will work when the update occurs, and make necessary changes. The current Garageband X is already sandboxed, so you can do a quick test to have a gander at how many of your current AUs will work in Logic X Sandboxed.

The short answer is "hardly any."

There are some very big problems with sandboxing something like Logic, from a developer's perspective, and almost no benefit to the end user. (In actual fact, it harms the end user, because products he was able to use previously, and may have come to rely on, will suddenly cease to work.) We could talk in circles all day long about that sort of nonsense, but at the end of the day, it is what it is.

While this stands a very real chance of having a consumer backlash something on the order of what occurred when Final Cut X was released, that's neither here nor there in the scheme of things. Our concern at Audio Damage is to maintain a seamless transition, so our customers aren't affected. And, let's be honest, there is nothing we like more than dropping everything and spending a couple months re-building our entire product line every time Apple has a fit of the Shinies.

In that light, we had a difficult decision to make. The only thing preventing our products from working in Logic X Sandboxed (and Garageband X, for that matter) is the erstwhile copy protection. For a decade now, we've had the simplest, least intrusive copy protection that we could have and still call it that. It has done very little to prevent piracy, and is the number one (and two and three and four and five and six and seven) source of support problems. It is, in short, a gigantic fucking pain in the ass that doesn't do what it's supposed to. And now it prevents our products from working in the Apple hosts.

So, we're taking it out.

We'll begin rolling out updates next week that will eventually encompass our entire product line, removing the DRM and updating the installers and UIs (and doing some bug fixing along the way), in order of popularity. The license control mechanism in the store will continue as-is, but the current reg codes will basically become serial numbers, and will not be required during the installation process. We'll also be able to deliver the bundles as one-click installs instead of 22 separate packages, which will no doubt please our bundle customers immensely.

This is obviously a pretty big risk for us, but we think it will be a good solution in the long run. We have long been of the opinion that there are people that care about supporting a company and its endeavors, and people that only care about themselves. Both Adam and I make a living on the former sort, and we hope that will continue to be the case. I can't speak for Adam, but I'm really shitty at blanching fries.

Anyhow, my Twitter feed and the Audio Damage RSS feed are the places to watch for updates as they're rolled. If you have a specific bug report that you think we might not know about, email it to [email protected] and I'll put it in the list. We'll be doing the products in order of popularity (with shiny new digitally signed installers, natch!) so expect Dubstation, Eos, Replicant, and Discord3 to be the earliest recipients of this treatment, and so on down to the perpetual tail-end Charlie, Ronin.


Page 7 of 7

Jan.14.2014 @ 2:11 PM
automap was horrid. tried it w/the nocturn. was awful.

Jan.15.2014 @ 12:12 AM
I'm definitely with boobs on the Automap thing. I still use a Novation master, but Automap is pleasantly absent from my system. It was always super-clunky and felt like a bad hack.

Jan.15.2014 @ 6:30 AM
Chris Randall
I hated Automap from Day One of its existence. I never like wrapping solutions. If you're automapping an AU, you're triple-wrapping a plug-in, and frankly, it's just stupid and hacky to do all that just so you can expend _MORE_ effort turning a knob than mousing a control.


Jan.15.2014 @ 10:05 AM
Yeah, not a good time "triple" wrap. My producing partner's system got so messed up with Automap on a system level, uninstalling was a nightmare (even with Clean App etc), I think it required a clean install...(granted this was awhile ago...), slowed everything to a crawl, didn't work, etc... Anyone here try VSL in terms of plugs etc? My friend Bon loves it, but it's expensive, and seems like more stuff to keep track off, harkening back to the real OTB days with keeping multiple scsi drives to k2000's, akai's, nord patches etc... I'm definitely a set it and forget it guy now.. especially with analog gear (duh)... print the best part you come up with, because you really don't need to go back as often as you think, and carve/modify later if you have to.. I like to automate parameters a lot, which is why Automap on paper looked good at the time, but just control m in ableton is fine for me now...not sexy, but i know it works. There is not a way to save those mapped parameters (outside of saving something within a rack of some sort) to the AU/VST, but whatever... I am probably overlooking something.

Page 7 of 7



Sorry, commenting is closed for this blog entry.