I pushed through a lot of outstanding bugs and issues last week—many of which I was working really hard to avoid for a long time. Some issues really seemed larger than they turned out to be, so I was very happy with the speed at which I was able to get these annoying issues dealt with.

I am almost ready to lock down 3.1 for release preparation, though I want to try a few more experiments with the distortion feature before I ship. It’s a real sore point for a lot of customers (graphs aren’t the easiest to read, color choices can make the three lines difficult to distinguish, etc), so I would like to ensure I get the UI sorted out soon.

Check out the latest build page for release notes, and a link to download 3.1b3.

I have been sitting on a handful of plugged memory leaks and an improved harmonic distortion display (now shown in %) for a few weeks now. I put a few more fixes in the past couple of days, and decided I should get this latest iteration of FuzzMeasure 3.1 into my customers’ hands sooner rather than later.

So, get over to the FuzzMeasure latest builds page and download 3.1b2. Let me know if you find any new issues, or notice any performance improvements (or degradations! :P).

I have been working on FuzzMeasure 3.1 for a fairly long time now, but I never made any solid plans about when I would release it, or what features I would add to it. Now that I have some more time to dedicate to FuzzMeasure, I stepped back and realized that I got a lot of work done on FuzzMeasure over the past few months without realizing it.

My list of outstanding issues and features for FuzzMeasure 3.1 has dwindled to nearly nothing, so I think that now is an appropriate time to call on my users to give FuzzMeasure 3.1 a shot, and provide some feedback on their experience with it.

You can check out the latest build page to see what I’ve added and fixed, and download a copy to try for yourself.

If you enjoy living on the edge, and keeping up with the very latest FuzzMeasure developments, you should check out the FuzzMeasure Latest Builds page. There you’ll find the very latest published build of FuzzMeasure that’s not yet ready for public consumption.

Sometimes I fix very nasty bugs that block certain users from getting work done. In order to get these folks up & running as quickly as possible, I need somewhere to put my latest builds that weren’t ready to be released yet.

Because these releases will eventually become final, and more than one user is affected by these fixes, the obvious solution is a public page I can point the affected users at. However, I would also like to get a head start of having some other (brave!) people use and test these builds before I increase distribution further.

If you are one of these brave people, and would like to live life on the bleeding edge, you can set FuzzMeasure up so that it checks for the latest unreleased build automatically on launch. The instructions to do this are at the bottom of the FuzzMeasure Latest Builds page.

In past years, I made a point of declaring an area of focus (similar to a New Year’s resolution). 2006 marked a year of making more mistakes, and in 2007 I focused on refinement. All my declarations hold for the future, so I still plan on making plenty of mistakes, and I will continue to refine the products that I release.

This year I held off on my public declaration due to the sensitivity of what I was proposing — in 2008, I declared independence. I resigned from my full-time job to pursue a career in independent Mac software development. My first day as a full-time employee of SuperMegaUltraGroovy is February 8th, which also happens to be my birthday.

This is huge. I am turning my life upside-down to pursue a dream I’ve had since I was in grade school. When I first started to program, I was interested in designing my own software, and making music with my computer. From that point forward, writing audio-related software on my own would turn out to be the ultimate career goal.

I’ve written a handful of applications to work with sound over the years (ranging from software synthesis to MIDI control applications), but the experience required to ship a complex application just wasn’t there. FuzzMeasure gave me an excuse to carry an idea to completion, though over the past year I’ve grown frustrated with my inability to devote more time to the software I love.

In June 2006, at WWDC, I started to wonder how long it’d be until I could live out this fantasy. I was a long way from making my salary with FuzzMeasure, and 3.0 had a few months left to go. During this time, Andrew grew older, and even more fun to spend time with — I very much prefer playing with my son to writing more code outside of my day job.

When FuzzMeasure 3.0 finally launched, the response was great. A healthy fraction of existing customers upgraded, and plenty of new customers came knocking at my door. I was still short of making my salary, but the upward trajectory of sales and interest was hard to ignore. I knew I had to start considering a move to full-time development of FuzzMeasure and future products, and quickly.

The final decision was made over the holidays. My wife and I deliberated over the sacrifices we will have to make, but we both agree that I have the passion and skill to pull this off. Given the current sales growth, and a possibility for increased revenue with new applications, it seems like the right thing to do.

We have enough savings to sustain us for about 2 years in addition to the current (relatively stable) revenue stream. Of course, I’m planning to revisit the whole strategy much sooner than that in case things start to go badly — I can’t afford to bankrupt my family.

So with some big sacrifices, a proven track record of skill, and a burning desire to create outstanding products, I’m confident that I can make this work. I look forward to bringing the world more SuperMegaUltraGroovy applications, and continuing to make FuzzMeasure the world’s best audio measurement tool.