You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps will reproduce the problem?
I have my Mac Mini set to never fall asleep. The display is set to go to sleep
after 20 minutes. I will start Soundflowerbed and it works okay (not as well
as it did on 10.8, as the volume up and down are a bit jittery but it does
work). As soon as the display turns off, and I come back to the computer,
Soundflowerbed has quit and the sound will not work until I open Soundflowerbed
again.
What is the expected output? What do you see instead?
I expect, as it did before the Mavericks 10.9.2 update, for Soundflowerbed to
be open and the sound to work after the display has gone to sleep. Instead,
after the display times out and I come back to the computer, Soundflowerbed has
quit and the sound will not work until I open Soundflowerbed again.
What version of the product are you using? On what operating system?
Soundflowerbed v1.6.6b on OS X Mavericks 10.9.2
Original issue reported on code.google.com by gillia...@gmail.com on 25 Mar 2014 at 12:40
The text was updated successfully, but these errors were encountered:
Same issue here, but when the display (TV) is rewoken from sleep. I suspect it
is because there is a new (HDMI) audio device present that causes
soundflowerbed to freak out.
I've set Soundflower to output on the MiniMac's digital out - so the HDMI audio
is not in use itself.
Original comment by per.kris...@gmail.com on 12 May 2014 at 5:45
I'm able to reproduce this issue, too, mostly in the same scenario (HDMI
output, monitor going to sleep, crashing when waking up, OSX 10.9.4 Mavericks)
One variation: after the display is awake, Soundflower auto-selected "None" as
the output. When selecting back "HDMI", it crashes.
Note that the display should be really sleeping, going into screensaver/blank
screens doesn't produce any issues.
Original comment by sergio...@gmail.com on 16 Jul 2014 at 2:13
Original issue reported on code.google.com by
gillia...@gmail.com
on 25 Mar 2014 at 12:40The text was updated successfully, but these errors were encountered: