Update! I reviewed Boom in Jul 2011, and had to remove it because of severe system problems and frequent crashes. I recently updated to the latest version and after using it for 2 weeks, it appears that the developer has corrected all the problems that I experienced. So far, no crashes, no problems.
I can now state that this is a very useful app for a variety of audio needs. I'm particularly fond of the EQ function. I'd prefer that the graphic interface show frequencies or octave bands, but it's easy enough to set the EQ by ear or just to one's own preference without needing the technical details of frequency and bandwidth.
Beware! I had Boom installed as a login item, so it loaded whenever I stared up, along with several other login items and startup programs that I use every day. I didn’t notice any problems at first but one day started experiencing a sudden, spontaneous log-out and reboot problem: I'd be working on the computer doing nothing in particular and suddenly get a blue screen and be rebooted to the login screen. This is not a kernel panic but, rather a sudden total shutdown and restart.
I tried all the usual troubleshooting techniques (repair permissions, test RAM, test HD, run Diskwarrior, Applejack, etc.) and couldn't find the problem. I checked crash logs but couldn’t find a consistent cause. I, then, disabled my login items, one at a time, over several days, and traced the problem to Boom. I uninstalled Boom and have not had a problem since.
This is a potentially good and useful utility, but the developer needs to find a better way to implement it, rather than with a kernel extension (kext) that appears to cause a kext conflict.
Just to reconfirm, it has now been over two weeks since I removed Boom from my computer, and I have had no further problems; no more spontaneous log-out and reboot events. I was very methodical in my troubleshooting and diagnosis of the problem: I removed ONLY Boom and made no other changes. Since removing Boom completely solved my problem, I'd have to conclude that Boom caused the problem. Again, I hope the developer finds a better way to implement this: Boom "could" be a very useful utility, but not until it's safe to use.
I have a Mac Pro, 1.1, dual-core Intel Xeon.
9GB RAM
OS 10.6.8
I did not keep the crash logs or console logs. I trashed them after I discovered the problem and removed Boom (over 2 weeks ago). I no longer have Boom and won't try it again until you change the way you implement it, i.e., not using a kernel extension.
There are currently no troubleshooting comments by this member.
Please login or create a new MacUpdate Member account to use this feature
Boom
MuSonics reviewed on 19 Jan 2012
I can now state that this is a very useful app for a variety of audio needs. I'm particularly fond of the EQ function. I'd prefer that the graphic interface show frequencies or octave bands, but it's easy enough to set the EQ by ear or just to one's own preference without needing the technical details of frequency and bandwidth.
Bottom line: This is a very useful audio utility.
Boom
I tried all the usual troubleshooting techniques (repair permissions, test RAM, test HD, run Diskwarrior, Applejack, etc.) and couldn't find the problem. I checked crash logs but couldn’t find a consistent cause. I, then, disabled my login items, one at a time, over several days, and traced the problem to Boom. I uninstalled Boom and have not had a problem since.
This is a potentially good and useful utility, but the developer needs to find a better way to implement it, rather than with a kernel extension (kext) that appears to cause a kext conflict.
I did not use the Hot Keys option.
I have a Mac Pro, 1.1, dual-core Intel Xeon.
9GB RAM
OS 10.6.8
I did not keep the crash logs or console logs. I trashed them after I discovered the problem and removed Boom (over 2 weeks ago). I no longer have Boom and won't try it again until you change the way you implement it, i.e., not using a kernel extension.