Boom 1.3 preventing Mac Sleep?

pmcdowall

I have Boom 1.3 running on my iMac now that the sound delay issue is resolved, but it seems to be preventing my iMac from going to sleep after an hour. Without Boom running it sleeps reliably. With Boom running, it will sleep, but then wake again soon after. Does anyone else see this?

System

Hi Pmcdowall,

Could you please write to our Support Team with your system info and also please do elaborate the issue providing a sequence to regenerate.

mbze430

I am having the same problem.. here is the some data you might want

MacBook-Pro:Desktop e430benz98$ pmset -g assertions
7/11/12 10:27:12 PM PDT
Assertion status system-wide:
PreventUserIdleDisplaySleep 0
CPUBoundAssertion 0
DisableInflow 0
ChargeInhibit 0
PreventSystemSleep 0
PreventUserIdleSystemSleep 1
ExternalMedia 0
DisableLowPowerBatteryWarnings 0
EnableIdleSleep 1
NoRealPowerSources_debug 0
UserIsActive 0
ApplePushServiceTask 0

Listed by owning process:
pid 203: [0x000000cb012c0005] PreventUserIdleSystemSleep named: "com.apple.audio.'BoomEngine:0'.noidlesleep"
pid 203: [0x000000cb012d0006] PreventUserIdleSystemSleep named: "com.apple.audio.'AppleHDAEngineOutput:1B,0,1,1:0'.noidlesleep"

T

System

@Pmcdowall,

Thank you for the detailed info.

We will look into this.

mbze430

Also I noticed that Boom locks another process (I don't remember the name, but it has to do with audio core; I have uninstalled Boom) that is always taking 5% of the CPU. Which isn't too bad if you are on a iMac or Mac Pro (desktop) but on a Macbook it starts to eat up a lot of battery

System

@Mbze430,

When Boom is active, it takes up-to 7 - 8% of CPU in MacBook.
In idle state CPU usage gradually decreases and may consume around 0.30 - 1% of CPU.
You always have an option to uninstall & check. For more info, please get in touch with our Support Team.

mbze430

@admin, yes I have uninstalled it. Till you guys fix the sleep issue.

wolfgang123usa

It looks like I have exactly the same issue on MBP 2011 with Mountain Lion

MBP-WB:~ wolfgang$ pmset -g assertions
8/27/12 11:19:55 PM GMT+
Assertion status system-wide:
PreventUserIdleDisplaySleep 0
PreventSystemSleep 0
PreventUserIdleSystemSleep 1
ExternalMedia 1
DisableLowPowerBatteryWarnings 0
UserIsActive 0
ApplePushServiceTask 0
BackgroundTask 0

Listed by owning process:
pid 141(coreaudiod): [0x00000001000007b8] 00:09:46 NoIdleSleepAssertion named: "com.apple.audio.'AppleHDAEngineOutput:1B,0,1,2:0'.noidlesleep"
pid 141(coreaudiod): [0x00000001000007b7] 00:09:46 NoIdleSleepAssertion named: "com.apple.audio.'BoomEngine:0'.noidlesleep"
pid 18(powerd): [0x000000090000012c] 03:51:11 ExternalMedia named: "com.apple.powermanagement.externalmediamounted"

any solution to avoid this?
regards, Wolfgang

ben

Same on iMac 2011 Mountain Lion with Boom 1.5.1
Cant get the system into sleep until uninstall of Boom

Listed by owning process:
pid 97(coreaudiod): [0x00000001000002e8] 00:00:27 NoIdleSleepAssertion named: "com.apple.audio.'AppleHDAEngineOutput:1B,0,1,2:0'.noidlesleep"
pid 97(coreaudiod): [0x00000001000002e7] 00:00:28 NoIdleSleepAssertion named: "com.apple.audio.'BoomEngine:0'.noidlesleep"
pid 2959(helpd): [0x0000000c0000029d] 00:17:16 BackgroundTask named: "com.apple.helpd.sdmbuilding"

System

Hey,

We have noted down the issue and our developers will be looking into the issue.
Thank you once again for reporting the issue. We will look into it.

Note: Instead of uninstalling, you can turn 'Boom volume' off within the app.

Asyd

I'm curious, this was reported in 2011 and I just bought the app and reported the same thing in 2013. It's STILL not fixed? I'm using version 1.7 and the original poster was using 1.3

System

Hey there,

We have notified our developers about the issue and it might take sometime for us to push an update for the issue.

ejg91681

Hi admin,

I am having the same issue... I was wondering how long is it going to take to have an update? Thanks in advance.

System

Hey there,

Exact/estimated time cannot be provided at the moment.
As a work-around, please quit Boom while you let your system to sleep or you can turn Boom off (within the app). Please refer screenshot below.

Asyd

Turning it off doesn't fix the problem...one needs to quit the app totally. I understand that it might take some time but there have been four point updates released 1.3-1.7 since the OP over a year ago. The question isn't the time but whether or not this is a priority issue and, if not, why isn't it a priority when this impacts the proper function of one's device?

ltmayonnaise

Hello, firstly I'd just like to say that I love Boom. Having a system wide EQ is a godsend and the existence of this app is much appreciated. That said, I am experiencing the exact same issue. My mac will not sleep with boom installed. I found "com.apple.audio.'BoomEngine:0'.noidlesleep" listed via "pmset -g assertions" as others have reported.

It's quite disconcerting to see that Boom hasn't been fixed an entire year after the bug report. I simply can't use Boom if my Mac cannot sleep with it running and I consider it unusable as it affects the normal operation of my Mac.

Any updates on the issue?

System

Hey,

Our Engineers have been looking into this sporadic issue. As per their findings, there was a direct API key in OS X 10.6 [kAudioHardwarePropertySleepingIsAllowed] that makes the OS X to override any app and allow the System to goto sleep. The same set of API key exists in 10.7 but that has no effect in its functioning yet the System goes to sleep. In 10.8, the specific API key doesn't exist but does not prevent the System going to sleep. There has been no specific answers or reasons provided to queries posted in the Apple Forums so digging deep into this is kind of limiting after a certain point. Please note, this is sporadic and not affected to every system, having said that, we understand the concern. We will keep looking into this and update this thread when we have got more information on the technical challenge being faced in isolating this issue.

ltmayonnaise

Thanks, I appreciate the update and that you're looking into the issue. Being a developer myself I fully understand the complications and intricacies of this kind of bug, but its still a troublesome issue that needs to be resolved. Having to manually disable boom every time I step away from my Macbook is a real pain.

I've taken a few screenshots demonstrating the results of pmset -g assertations as the Boom Volume and Equalizer toggles are enabled, hopefully it will help you troubleshoot this.