This afternoon I released FuzzMeasure 3.2.2, which you can download from http://fuzzmeasure.com.

The largest change in this release is an important one, as I believe I may have finally found a ‘silver bullet’ to deal with widespread confusion about FuzzMeasure’s results. Now, FuzzMeasure will fail gracefully when a measurement is captured incorrectly, rather than giving you bad data.

You see, I get a lot of support emails from customers who are new to FuzzMeasure, and acoustic measurements in general. In many cases, their misunderstanding stems from the fact that FuzzMeasure will happily let you measure silence, and give you a meaningless graph.

Not any more!

FuzzMeasure now checks and ensures that there is a distinct impulse peak that should be well above the noise floor of a signal. This serves as a built-in failsafe that will force you to repeat measurements until you get your levels set up correctly.

Setting levels may be a combination of adjusting the volume of your amplifier to produce a louder input for your microphone, or changing the gain on your microphone preamplifier to pick up more signal. At any rate, you should be sure to use the Level Meter window to keep an eye on how quiet (or loud) your input is being picked up during the measurement.

In addition to this change, you can now also choose to normalize the impulse graph “post calculation.” Just choose Impulse > Normalize from the main menu to enable this feature. This feature basically allows you to view the Envelope Time Curve and Log Squared Impulse Response with their peak at 0dB. Normalizing the record (Measurement > Normalize) would not necessarily guarantee this.

I also boosted performance considerably for users that find themselves viewing lots of Envelope Time Curve graphs. Because that calculation is very intensive, I now use a caching scheme that will stash already-calculated ETCs to disk for faster recall when switching between records.

If you hit any trouble, you can always email support@supermegaultragroovy.com with your concerns.

Today I’ve released FuzzMeasure 3.2 out in the wild for the world to use. Here’s the official press release.

I think this is a very solid update to the app, and I’m happy to finally have it in my customers’ hands after such a long time. For me, the best part is that I now get to focus on all the exciting features I had to fight so hard to keep out of 3.2!! :)

In preparation for the FuzzMeasure 3.2 release, I’ve been working on another rich resource for new (and experienced!) users.

I will be converting my new office location (which is now in my basement) into a home project studio, using FuzzMeasure to help me analyze the space before and after the application of acoustic treatment.

Check out, Measuring and Treating a Home Studio Using FuzzMeasure Pro to read more about the project, and see graphs of my untreated room.

New segments will be added in the coming weeks, as I choose and order my treatments, install them, and measure their effectiveness.

There’s really not all that much to say beyond, “all my products work well in Snow Leopard.”

I highly recommend upgrading to Snow Leopard, as there are improvements across the board that will be apparent in all your applications—especially when it comes to performance. I’ve been running Snow Leopard for months as part of Apple’s Developer Connection program, and it has been solid for a long time.

For FuzzMeasure users on Snow Leopard, I encourage you to check out version 3.2 at the latest build page. You’ll be treated to some speed increases as a result of the 64-bit binary that’s available only to Snow Leopard users. (If you’re stuck on Leopard—don’t worry! FuzzMeasure 3.2 will remain compatible with Mac OS 10.5.)

Today I unleashed FuzzMeasure 3.1 on the world, and I’m pretty excited about it. Actually, relieved is probably a more accurate term.

You can read the FuzzMeasure 3.1 Press Release for further details, etc.

Now I can return to the other projects I’m working on again, and get working on the first of the new features of 3.2…