BlackHole
BlackHole copied to clipboard
ExistentialAudio
[BUG] Blackhole keeps disappearing
Hi,
I'm using latest blackhole-2ch installed via brew (blackhole-2ch: 0.2.10) on macOS 12.1, MacBook Pro (14-inch, 2021), M1 Pro.
Unfortunately, the blackhole audio device keeps disappearing after some time. Only my script to restart audio helps:
sudo kill -9 `ps ax|grep 'coreaudio[a-z]' | awk '{print $1}'`
It might be related to Xcode and/or simulator, because I'm using blackhole to redirect input/output from the simulator. Without the blackhole I'm often hearing some strange crackles caused by the simulator, that's why I installed the blackhole.
Could you check this?
I'm getting this issue as well. Thanks for your script, I had been resorting to reinstalling Blackhole every time it disappeared. I am also on a 14-inch M1 Pro MacBook.
Just adding my two cents that I'm getting the same issue on my MacBook Air M1 (2020) with Monterey 12.1
Thanks for the script, it also did the trick for me!
@devinroth I'm using version from brew. Why 0.3.0 is not available there?
I ran the package but the installation failed (twice). It didn't give me any details though so I can't say anymore. Cheers!
From: Devin Roth @.> Sent: Wednesday, February 2, 2022 9:48 PM To: ExistentialAudio/BlackHole @.> Cc: Wirkes Shane @.>; Comment @.> Subject: Re: [ExistentialAudio/BlackHole] [BUG] Blackhole keeps disappearing (Issue #524)
BlackHole2ch.v0.3.0.pkg.ziphttps://github.com/ExistentialAudio/BlackHole/files/7989561/BlackHole2ch.v0.3.0.pkg.zip Can you try this version and see if it makes any difference.
— Reply to this email directly, view it on GitHubhttps://github.com/ExistentialAudio/BlackHole/issues/524#issuecomment-1028298925, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACKDD63JWO33L45TYTFQU4DUZGDBDANCNFSM5MJQ426Q. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you commented.Message ID: @.***>
I'm also seeing blackhole disappear. I can see it's listed under the devices I created but is disabled. It's unclear how to turn it back on again without reinstalling.
Just release v0.4.0. Should solve this but reopen if you continue to run into issues.
Hi. I'm also getting this issue with the release v0.4.0. MacOS Monterey.
Same issue on macos m1 12.6.1. blackhole-2ch and 16ch (i have both) .v0.4.0. reinstalling with home brew makes it reappear.
I get the exact same behaviour as described above (M1 MBA, macOS Ventura, v0.5.0). @devinroth, could you please reopen this issue?
Sure. But I need details. How to reproduce? Any relevant information from Console (logs, crash reports) anything that contains BlackHole.
Thank you for the prompt response. It has happened again but I see no records in Console. There is nothing in logs/crash reports with key words Existential Audio nor BlackHole. If I do a clean install, should it log anything? I will do that to start clean and I would also use this opportunity to test my ability to find relevant logs.
Other than that, what I can think of: I am using BlackHole in multi-output device config, the other output device being a Focusrite audio interface connected to my HP monitor via USB. I am connecting my MBA to the monitor via USB C, so the monitor serves as a dock and gets disconnected (both while MBA is active and while it's sleeping) often. Do you think the connection/disconnection scenarios are worth testing on my side? Or maybe asking others that haven't specified what machines they're using whether they have this issue on MacBooks or whether anyone has it on a desktop Mac as well?
I guess anything you can tell me at this point will help. As you stated I don’t have a whole lot of information to go on.
I’m going to build an app that will scan core audio to see if anything interesting pops up. I’ll keep you updated on that.
Devin On Jun 10, 2023 at 11:08 AM -0700, kovac254 @.***>, wrote:
Thank you for the prompt response. It has happened again but I see no records in Console. There is nothing in logs/crash reports with key words Existential Audio nor BlackHole. If I do a clean install, should it log anything? I will do that to start clean and I would also use this opportunity to test my ability to find relevant logs. Other than that, what I can think of: I am using BlackHole in multi-output device config, the other output device being a Focusrite audio interface connected to my HP monitor via USB. I am connecting my MBA to the monitor via USB C, so the monitor serves as a dock and gets disconnected (both while MBA is active and while it's sleeping) often. Do you think the connection/disconnection scenarios are worth testing on my side? Or maybe asking others that haven't specified what machines they're using whether they have this issue on MacBooks or whether anyone has it on a desktop Mac as well? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you modified the open/close state.Message ID: @.***>
While doing some work on cubeb-coreaudio-rs I've observed this issue on github actions, which uses Blackhole.
The setup is as follows:
- A BlackHole2ch virtual device D
- An aggregate device A (not private) with input D
- An aggregate device B (private) with input from A and output from D
- An HALOutput AudioUnit with input and output from B
Removing A (simulating a device being unplugged) seems to bring down D too. What's more is that we seem to be able to enumerate A still, although we cannot read its UID.
Having one AudioUnit with input from A and another AudioUnit with output from D works.
By removing BlackHole I assume you’re rebooting CoreAudio too. That definitely doesn’t simulate removing a device and is going to cause all sorts of problems with your tests.
Devin On Oct 13, 2023 at 7:00 AM -0700, Andreas Pehrson @.***>, wrote:
While doing some work on cubeb-coreaudio-rs I've observed this issue on github actions, which uses Blackhole. The setup is as follows:
• A BlackHole2ch virtual device D • An aggregate device A (not private) with input D • An aggregate device B (private) with input from A and output from D • An HALOutput AudioUnit with input and output from B
Removing A (simulating a device being unplugged) seems to bring down D too. What's more is that we seem to be able to enumerate A still, although we cannot read its UID. Having one AudioUnit with input from A and another AudioUnit with output from D works. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you modified the open/close state.Message ID: @.***>
Got it. I just was confused with how you said “A BlackHole”. Lol.
I’ll take a look but if the issue is the aggregate device there’s nothing I can do about that. Aggregates are full of bugs.
Devin On Oct 13, 2023 at 7:43 AM -0700, Andreas Pehrson @.***>, wrote:
We don't remove BlackHole. We destroy the aggregate device on top of BlackHole. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you modified the open/close state.Message ID: @.***>
@Pehrsons could you give me the core audio errors/warnings from Console when this happens. On another topic, there's a better way to test adding remove an audio device that doesn't include buggy aggregate devices. Use BlackHole but simulate adding and removing an audio device by setting kAudioBoxPropertyAcquired.
And I recommend not using Aggregates at all since they've only ever caused me problems. Apple unfortunately doesn't seem to care about fixing them.
Unfortunately I've only been able to hit this on Github Actions (where I suppose the biggest difference to my machines is that there's no hardware device to fall back to), and afaik I cannot access any sort of system logs there. I'll try a bit harder locally to see if I can get lucky.
We're seeing similar things re aggregates sadly, thanks for the advice!
I also tried to reproduce on my computer without any luck. The main difference was I didn’t use a hidden aggregate. I’ll try again when I have more time.
Devin On Oct 16, 2023 at 3:04 AM -0700, Andreas Pehrson @.***>, wrote:
Unfortunately I've only been able to hit this on Github Actions (where I suppose the biggest difference to my machines is that there's no hardware device to fall back to), and afaik I cannot access any sort of system logs there. I'll try a bit harder locally to see if I can get lucky. We're seeing similar things re aggregates sadly, thanks for the advice! — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you modified the open/close state.Message ID: @.***>
Also had / have this issue several times - from brew version - always have to reinstall. Without device aggregation
Any crash logs in terminal?
Devin On Dec 18, 2023 at 12:31 AM -0800, robmimi @.***>, wrote:
Also had / have this issue several times - from brew version - always have to reinstall. Without device aggregation — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you modified the open/close state.Message ID: @.***>
I too have noticed that BlackHole audio devices disappearing while my MacBook sleeps and then wakes up.
Other virtual audio drivers (VB-Cable and SoundDesk) continue to work.
What crash reports do you see?
Are you able to reproduce this?
Devin On Mar 4, 2024 at 7:03 AM -0800, JChin @ Ria Health @.***>, wrote:
I too have noticed that BlackHole audio devices disappearing while my MacBook sleeps and then wakes up. Other virtual audio drivers (VB-Cable and SoundDesk) continue to work. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you modified the open/close state.Message ID: @.***>
No crash reports that I can see. It silently disappears and we only notice that the input (in my case) disappeared and defaulted to the built-in mic.
This happens after the Mac has been idle. Duration is random. Sometimes after a lunch break, sometimes overnight.
NOTE: this has been happening for months now. We thought it was an OS issue, a hardware (USB) issue, and we've tried upgrading all of those without luck. It was recently that I noticed it was only the BlackHole driver that was the common issue and pretty much see it across apps (seen it disappear from Chrome browser, mostly, and sometimes also from OBS)
I haven’t had this happen to me. But if it happens to you regularly then it’s good news, I can have you do a bunch of testing if you’re willing so we can figure this out.
Devin On Mar 4, 2024 at 8:04 AM -0800, JChin @ Ria Health @.***>, wrote:
NOTE: this has been happening for months now. We thought it was an OS issue, a hardware (USB) issue, and we've tried upgrading all of those without luck. It was recently that I noticed it was only the BlackHole driver that was the common issue and pretty much see it across apps (seen it disappear from Chrome browser, mostly, and sometimes also from OBS) — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you modified the open/close state.Message ID: @.***>
By the way, I have the issue right now. Blackhole 2ch is not available in Chrome or Google Meet. I have not restarted the Chrome browser or coreaudiod. Blackhole 2ch is still seen in Audio MIDI Setup and OBS, and Zoom.
LadioCast still sees Blackhole devices
AudioPick (Chrome extension) does not see Blackhole (except for the system device, see Audio MIDI setup screenshot).