1.3 Held Back
• Chris Liscio
• Chris Liscio
I promised to give an update about what I did all the extra coding for. First, some background. </p> <p> I spent the last two weeks on vacation – far away from my home. This fact helps explain why the big outage affected me for a few days rather than only a few hours. I got in touch with a good friend back home, and he helped me get piggy back on its feet. </p> <p> While away, I got to spend some quality time with FuzzMeasure's code. During this quality time, the feature list for 1.3 grew a little. I did not have plans to work on FuzzMeasure at all during my vacation, and instead I wanted my users to spend extra time testing 1.3 so I could plan for a release when I returned. Boy did I ever get in over my head. </p> <p> Field Recording Support </p> <p> You can measure a lot of things with FuzzMeasure, but certain things do not measure so easily. Case in point – I do not have a line-in for my car's audio system. Most people don't. How could I possibly test how well my car's cabin sounds, or if EQing will help? </p> <p> With FuzzMeasure 1.3, I decided to add the ability to export stimulus signals for field recording, and import the recorded response to the stimulus for processing. Now, I simply burn a CD with the stimulus signal I wish to use (a simple task using iTunes), and play back the signal in my car as I record the response using my iBook. Then, I go to the Tools menu in FuzzMeasure, and select Import Field Recording to get my results. </p> <p> Using this method, I have successfully measured the frequency response of my iPod! I also plan to measure the response using the iTrip in my car, as it seems to add quite a bit of bass to its signal. Soon, I can get some hard evidence to prove (or disprove) that this happens! </p> <p> Sound Device Correction </p> <p> Not all sound devices have flat frequency response curves. This proves true especially in cheaper models. Now you can correct for the response of your sound device, and get higher-quality results in the end without requiring higher-quality equipment. Many people asked for this, and finally I figured out how to deliver it. Unfortunately, I have some work to do on the UI for this. </p> <p> Microphone Compensation </p> <p> Do you have a calibration file for your microphone? If so, please send them to me via email. In the meantime, I have most of this feature worked out, but need a better idea of what format people normally keep their microphone compensation files in so I can better handle the import feature. In the meantime, I also have work to do on the UI for this feature. </p> <p> FRD Consortium Export </p> <p> Some of you asked for this, and I figure that the time has come for me to finally get the feature written. If you wish to design crossovers for speakers using readily available software and spreadsheets, this will help you greatly. If you do not need to design crossovers for speakers, or have no other use for FRD files, then you might want to export your frequency response data directly into a third-party application for graphing outside FuzzMeasure. </p> <p> As you can see, I spent a lot of time working on FuzzMeasure, and I plan to work even more on 1.3 before I get it out the door. Many of you really enjoy the smoothing feature, but I feel I need to provide much more than that this time around. Also, the price will finally hit the final target on August 1st, so I would like to release 1.3 very close to that time. It feels like the right thing to do. </p> <p> Until I inform you of a new beta version available, keep plugging away at 1.3b1. Fire me any bug reports, or new feature ideas if you have any. </p>