Unforseen Problems

• Chris Liscio

It would appear that FuzzMeasure 1.1 does not play nicely with certain audio devices. Unfortunately, since I have yet to own every audio device in the world, I am unable to verify that they'll all work properly with FuzzMeasure. Upon learning that FuzzMeasure is incorrectly discarding certain devices from the device selection list, I immediately ordered two more USB audio devices so that I can get on top of cleaning up my audio device selection code. </p> <p> I know how to fix the issue, but I am hesitating to release a 1.1.1 version until I can verify for myself that the fix is going to work properly. If any of you out there are having issues with FuzzMeasure 1.1 and your audio devices, please let me know. I can help you get up and running with your preferred device. </p> <p> Because my audio devices won't arrive for a little while, I may have to just accept the fact that the 1.1 release is a little bit wonky, and push forward to get 1.2 completed. If you're registered with the forums, you probably already know that 1.2b0 has been released, and you can start banging on it. In fact, if you already know that, you're probably already banging on it now. ;) </p> <p> 1.2 is moving along quite rapidly. I have my impulse response selection UI working, and the results are very promising. Unfortunately, the constant Q transform isn't working as well as I'd hoped, but I will probably leave it in as an option for the user to explore. It's slower than I would have liked, and I'm not convinced that I'm processing the results properly. Also, I have implemented pink-filtered MLS output, but as with the constant Q transform, I'm not overly happy with its usefulness. :) </p> <p> So now, your job is to play with the 1.2 betas, and my job is to keep making 1.2 excellent, and the best release ever. </p>