Under The Microscope

Mistakes We’ve Made

Audio Hijack 2.0.1 has just been released, and as with any X.0.1 update, it’s primary purpose is to address problems. First of all, it fixes many minor bugs relating to path names, preset targeting, and threading of our post-processing to iTunes. The update is recommended for everyone who downloaded Audio Hijack 2.

However, besides the usual bug fixes, Audio Hijack 2.0.1 addresses a problem of conceptions, or misconceptions, among our customers. This was a problem we created, and now, it’s one we’re trying to ameliorate. To put it simply, Audio Hijack Pro users wanted Audio Hijack 2 access. In more detail, it went like this:A long time ago, in a year far, far away (September of 2002), we released Audio Hijack 1. This was quickly followed by Audio Hijack 1.5, then 1.6, then 1.6.5. After this, we began work on Audio Hijack 2. It was a massive rewrite and redesign, and along the way, we realized we had a whole new product. In March of 2003, what began as Audio Hijack 2 became Audio Hijack Pro 1.0. Two different products, one more powerful (and more confusing in its power) than the other. AH Pro was updated several times to 1.2.4.

Then we again began working on Audio Hijack 2. Again, it was a redesign, but it was designed with the basic user of AH/AH Pro in mind, as a superior audio recording system. We worked to streamline the process of recording Internet streaming audio (no pun intended), and add a few new features. On August 31st, we released this. It was a disaster, at least in terms of my inbox. You see, we keep our registered users up to date on our major releases and updates. So, we hit the list with the news of Audio Hijack 2, and suddenly, I had hundreds of emails asking why the hell their codes didn’t work.

We quickly realized Audio Hijack Pro users were trying to use Audio Hijack 2, and failing, because they were two separate products. Our front page was pretty clear in the AH 2 was a separate product from AH Pro (both products were still there), but our registered users were flummoxed. Perhaps it was Audio Hijack’s higher version number of “2” over Audio Hijack Pro’s 1.2.4. Perhaps the Pro designation had never really been noticed at all. Whatever the reason, we realized we had to do something about our many, many confused users who felt they should be able to use this application.

They’re two separate products, and AH Pro does much more than AH2. AH2 only has one or two features AH Pro doesn’t. So we asked ourselves, “Would anyone who bought AH Pro actually bother paying for AH2?” Our course of action became clear – give AH2 to AH Pro users for free. We sent out a second user list posting to this effect, and the emails ceased.

So here it is – Audio Hijack 2.0.1 now accepts Audio Hijack Pro codes. If you paid for Audio Hijack Pro, we think you should stick with Audio Hijack Pro. AH 2 doesn’t offer nearly as many features, and almost everything it does can also be done in AH Pro. But enough Pro users wanted AH 2 that we decided to let you have it. As always, communication (and over-communication) with our users led us to our conclusion. Any questions?

Comments for this post have been closed. Thanks for reading!


Our Software