Earlier today, I noticed that piggy had gone down again. Unfortunately, this happened twice since I installed my RAID drives, and the 2.4.11 kernel that went with it. Surely enough, it appears that 2.4.11 didn't have the best track record out there...
Work continues on FuzzMeasure 1.4, and my graphing code has grown considerably since then. I wrote lots and lots of graphing code, and yet so much more code remains for me to write. When will it end? </p> <p> Of course, with a huge load of work should...
I have done some more work on FuzzMeasure the last few days. Unfortunately, the graph code has just got me bogged right down to a walking pace. That said, I know that it will make the display look even better, and help make working with impulse responses...
I got the last of my fixes put into FuzzMeasure for 1.3.2, and they took quite a bit less work than I originally thought they would. </p> <p> I think I like my addition to allow dragging measurement records to the trash the best. Also, I found some...
I have done quite a bit of work on the impulse response display, to make way for more time-domain analysis tools. First and foremost, I threw in support for the graph displaying (which gives us milliseconds on the X axis, and amplitude (V/Vmax) on...
I discovered this fantastic new use case for FuzzMeasure when developing version 1.3. You see, I encountered a bug in the calculation of the graph display. Using AU Lab, I fixed broken resistor measurements by making slight tweaks to the volume level...
I feel like asking random questions to "the crowd". Hopefully I can keep a count in my head so I don't have a hundred question 2s. Email your answers to website@supermegaultragroovy.com </p> <p> Would you ever buy a set of speakers from eBay provided...
I have received many emails since I launched 1.3, and I feel happy to report, in general, that "you will see that feature soon". </p> <p> I actually had a pretty long feature list for 1.3, but had to push a lot of features out to 1.4 due to their high...