I'm working at home on FuzzMeasure for only a week, and now I have FuzzMeasure 3.0.1 ready to go out the door. Coincidence? Hardly.
I fixed some pretty nasty issues (broken AIFF exporting of impulses and stimulus signals), along with some harmless...
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...
John Atkinson, editor of Stereophile Magazine, has written up an article about the measurement equipment he uses to produce the measurement sidebars (example) for Stereophile's equipment review articles. According to John, FuzzMeasure is increasingly...
A few days ago, I was featured on Apple's download site and have received a huge torrent of download requests (for FuzzMeasure, anyway).
The 'killing' part happened last night, when Apache just stopped accepting HTTP connections. After some investigation...
Today only, FuzzMeasure is 20% off (for a total of $120). For the rest of the month, FuzzMeasure will be 10% off. Time to buy your favourite audio engineer or hobbyist a fancy gift they will love!
Note that this discount only applies to full license...
A customer approached me about a week ago looking for ways to use DRC-generated pcm files with convolvers other than BruteFIR on Linux. I realized that this wouldn't be an easy feat for a user to handle on their own, seeing how the pcm files aren...
I stumbled across these acoustics tutorial videos the other week, and was excited to see a solid resource for people new to measuring acoustics. Originally I caught the video on YouTube, and then Ethan himself pointed me at these higher quality versions...
Improving FuzzMeasure to take advantage of Leopard under the hood was an exercise in patience and self-discipline. When I first learned about Objective-C 2.0, I wanted to just leap in and change every single accessor to use properties and turn for into for-each loops.
However, I didn't have the time to do this, and I was smarter than that — mucking around in code that already works isn't necessary. That said, there are benefits to ripping out code when you have the opportunity — less code means less bugs!. Also, converting to Objective-C 2.0 buys you other benefits behind the scenes, such as enhanced thread safety, proper memory management, faster enumeration, etc.
How does the one-man shop deal with balancing this lack of time with a mounting pile of important, but not time-sensitive, work? You page it in!