I'm wondering if there are known issues with the audio cutting out when Boom is run on the 10.9 developer seeds? I know it's still beta status but wanted to figure out if it's something specific to my machine or a known issue.
Yes, we have come across few bugs/defects of Boom in OS X Mavericks. Glad that there is someone out there concerned about it. It would be really helpful if you could keep us informed for any other bugs found. Your help is appreciated.
I had trouble installing the Boom Audio component and getting it to run properly under Mavericks. After reinstalling it several times without luck, I found that removing the the /System/Library/Extensions/BoomDevice.kext and then reinstalling the component worked.
I'm running the 13A569 build and don't have any issues with audio cutting out. Hopefully the above will help your situation.
When installing Mavericks I got the alert message Boom was incompatible, and Mavericks removed the Boom app (but not the BoomDevice.kext). I removed the BoomDevice.kext and tried to install Boom again. But I didn't come past the point where it says "Preparing your Mac for Boom". So I tried that a couple of times. Finally (after about 5 minutes wait) I got an alert window saying "Installation failed due to and internal error. Please click ok on Install to retry" So I did, and this time it worked. Seems to be working so far...
The times it didn't work I got this every 10 seconds in the console log:
23.10.13 23:48:14,000 kernel[0]: CODE SIGNING: cs_invalid_page(0x102643000): p=2459[python] final status 0x0, allow (remove VALID)ing page 23.10.13 23:48:14,651 com.apple.launchd[1]: (com.makerbot.conveyor.daemon[2459]) Exited with code: 1 23.10.13 23:48:14,651 com.apple.launchd[1]: (com.makerbot.conveyor.daemon) Throttling respawn: Will start in 10 seconds
Thank you for providing us with the error logs. We are working on a new update for Boom. Current version of Boom is not compatible with Mavericks. We apologize for the inconvenience. An update will be released soon. Thank you for your patience.
@Mandlanne, thank you for sharing the link. We are reviewing all the cases, plus trying our best to fix them too. Hopefully we can push an update soon. But we were surprised that users seldom say it's Boom causing some sound issues when it's quite clear that native OS X is posing problem. iTunes EQ had problems with stuttering and Apple released iTunes 11.1.3 explaining the fix for that issue. But long before that, everyone said Boom is causing it (!) while the actual problem of Boom was with 'QuickTime'!!
Comments
Yes, we have come across few bugs/defects of Boom in OS X Mavericks.
Glad that there is someone out there concerned about it.
It would be really helpful if you could keep us informed for any other bugs found. Your help is appreciated.
I'm running the 13A569 build and don't have any issues with audio cutting out. Hopefully the above will help your situation.
Thanks for the info. We will look into it.
I removed the BoomDevice.kext and tried to install Boom again. But I didn't come past the point where it says "Preparing your Mac for Boom". So I tried that a couple of times. Finally (after about 5 minutes wait) I got an alert window saying "Installation failed due to and internal error. Please click ok on Install to retry"
So I did, and this time it worked. Seems to be working so far...
The times it didn't work I got this every 10 seconds in the console log:
23.10.13 23:48:14,000 kernel[0]: CODE SIGNING: cs_invalid_page(0x102643000): p=2459[python] final status 0x0, allow (remove VALID)ing page
23.10.13 23:48:14,651 com.apple.launchd[1]: (com.makerbot.conveyor.daemon[2459]) Exited with code: 1
23.10.13 23:48:14,651 com.apple.launchd[1]: (com.makerbot.conveyor.daemon) Throttling respawn: Will start in 10 seconds
Thank you for providing us with the error logs.
We are working on a new update for Boom. Current version of Boom is not compatible with Mavericks.
We apologize for the inconvenience. An update will be released soon. Thank you for your patience.
There is also a discussion going on here: https://discussions.apple.com/message/23767464?ac_cid=tw123456#23767464
I sincerely hope you can solve the issue as your app is fantastic!