BlackHole not appearing in Audio MIDI Setup on new M3 iMac running Sonoma 14.5 #793
Open
5 of 7 tasks
Labels
bug
Something isn't working
Comments
|
Check Library/Audio/Plug-Ins/HAL. Send a screenshot.
Devin
…On Jun 30, 2024 at 12:55 PM -0700, Cornwallis89 ***@***.***>, wrote:
Please Confirm
• I have read the FAQ and Wiki where most common issues can be resolved
• I have searched Discussions to see if the same question has already been asked
• This is a bug and not a question about audio routing or configuration, which should be posted in Discussions
macOS Version
macOS 13 Ventura
BlackHole Build(s) Affected
• 2 channel
• 16 channel
• 64 channel
• other/custom build
Describe the bug
Hi there, I've attempted to install BlackHole 0.6.0 on 2 new M3 iMacs running Sonoma 14.5 using both the package installer and Homebrew, and despite the installations purportedly completing successfully, BlackHole never shows up in Audio MIDI Setup, even after restarting the computer. I've attempted installing both the 2ch and the 16ch versions with the same result, and used the package uninstallers in between each installation attempt.
Is this normal behavior on this hardware or software/OS version? I do have some multi-output devices already configured - could this be causing the issue? Both identical iMacs encounter the same problem.
Now, even after running the package uninstaller attempting to reinstall using homebrew, it gives the error "Warning: Not upgrading blackhole-2ch, the latest version is already installed"
Thanks.
Reproduction Steps
1. Ensure installer and Terminal are granted Full Disk Access in the Privacy & Security tab of System Settings.
2. Install BlackHole2ch-0.6.0.pkg or BlackHole64ch-0.6.0.pkg, or type " % brew install --cask blackhole-2ch" into Terminal with HomeBrew installed.
3. Restart computer
4. Open Audio MIDI Setup, making sure Audio Devices are displayed.
5. Look for BlackHole to no avail.
Expected Behavior
After this process, I would expect "BlackHole" to appear as an audio device in Audio MIDI Setup, but it does not.
Screenshots
No response
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
|
Thanks - here it is! 
|
|
Open Console, search for coreaudiod then reboot coreaudio through terminal. Post the messages here.
Devin
…On Jun 30, 2024 at 1:07 PM -0700, Cornwallis89 ***@***.***>, wrote:
Thanks - here it is!
Screenshot.2024-06-30.at.4.06.53.PM.png (view on web)
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: ***@***.***>
|
|
Thanks - please forgive me, but I'm not sure I understood how to follow your instructions properly. I used Google to try to find a console command to reboot coreaudio through terminal. Attached are screenshots - please advise at your leisure. 
|
|
Yes that’s it. Sorry I should have been more specific.
Click start in Console and then run the command in terminal.
Devin
…On Jun 30, 2024 at 4:18 PM -0700, Cornwallis89 ***@***.***>, wrote:
Thanks - please forgive me, but I'm not sure I understood how to follow your instructions properly. I used Google to try to find a console command to reboot coreaudio through terminal. Attached are screenshots - please advise at your leisure.
Screenshot.2024-06-30.at.7.09.44.PM.png (view on web) Screenshot.2024-06-30.at.7.12.33.PM.png (view on web)
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: ***@***.***>
|
|
Thanks! The result is very lengthy: Log |
|
Interesting. I see I have a diagnosis app. Run this and show me what you see. |
|
Hi there - thanks! This is the result: BlackHole is not loaded. I killed coreaudiod and the result is the same. 
|
|
What about App developer permission? Do you have it set to Apple only?
Devin
…On Jul 3, 2024 at 8:00 AM -0700, Cornwallis89 ***@***.***>, wrote:
Hi there - thanks! This is the result: BlackHole is not loaded.
I killed coreaudiod and the result is the same.
Screenshot.2024-07-03.at.11.00.16.AM.png (view on web)
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: ***@***.***>
|
|
Thanks for the reply! Is this what you're referring to? 
|
|
Yeah.
Devin
…On Jul 3, 2024 at 4:37 PM -0700, Cornwallis89 ***@***.***>, wrote:
Thanks for the reply! Is this what you're referring to?
Screenshot.2024-07-03.at.7.33.01.PM.png (view on web)
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: ***@***.***>
|
|
Thanks for your help and all of you hard work, Devin. I can only assume there's some kind of new compatibility problem with the M3 iMac running Sonoma regarding audio devices. I'll check back in at a later date to see if there are any new developments. |
|
I’m not sure about that. There are definitely users that have installed on the M3.
But since I don’t have an M3 to test I can’t give you any more specifics.
Do you have the ability to build with Xcode and test yourself?
Devin
…On Jul 8, 2024 at 8:54 AM -0700, Cornwallis89 ***@***.***>, wrote:
Thanks for your help and all of you hard work, Devin. I can only assume there's some kind of new compatibility problem with the M3 iMac running Sonoma regarding audio devices. I'll check back in at a later date to see if there are any new developments.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: ***@***.***>
|
|
So the plot thickens. I got my hands on a new M3 MacBook Air and BlackHole installs and runs without any issues so something else is going on. |
|
I can confirm that the update to macOS 14.5 broke BlackHole (16). It's a mystery for me: It worked for almost 2 hours without any problem in OBS (streamed to MS Teams) and suddenly Teams lost the microphone (mute button greyed out) and a warning appeared that no microphone is detected. BlackHole is still listed in the macOS output selector, but your diagnose tool said the same like for @Cornwallis89.
|
|
Alright, restarting Teams (I know that this app is a problem in itself and we all hate it…) caused the whole MacBook to crash with a "Pink Screen Of Death" (the first time I saw this ever). @devinroth Let me know how I can support you. The console logs mentioned the same error like you already saw in @Cornwallis89 ones so I guess this does not help. |
|
The diagnostic tools is only for 2ch.
Devin
…On Jul 19, 2024 at 2:39 AM -0700, Sven Greb ***@***.***>, wrote:
Restarting Teams (I know that this app is a problem in itself and we also hate it…) caused the whole MacBook to crash with a "Pink Screen Of Death" (the first time I saw this ever).
I use a M1 by the first (first generation, 16-inch 2021) so my guess is that the hardware itself is not the root cause but Apple did not mention any change in macOS 14.5 (only security fixes are unlikely to cause this…).
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: ***@***.***>
|
I would like to know how to detect if the driver works or not using APIs. As I have renamed and rebuilt the driver, this utility doesn't seem to work properly. Perhaps you might provide the source project of this utility? |
|
Sure I can open source the tool.
Also worth turning off SIP when doing driver dev.
Devin
…On Aug 26, 2024 at 5:46 AM -0700, Oleg Melnik ***@***.***>, wrote:
> Interesting. I see default 21:53:17.618999-0400 coreaudiod HALC_ShellDevice.cpp:3817 HALC_ShellDevice::_InitializeDriverPlugIn: XX*X Not loading the driver plug-in into coreaudiod Not sure why that is.
> I have a diagnosis app. Run this and show me what you see.
> BlackHoleDiagnostics.zip
I would like to know how to detect if the driver works or not using APIs. As I have renamed and rebuilt the driver, this utility doesn't seem to work properly. Or you may provide the source project of this utility?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Please Confirm
macOS Version
macOS 13 Ventura
BlackHole Build(s) Affected
Describe the bug
Hi there, I've attempted to install BlackHole 0.6.0 on 2 new M3 iMacs running Sonoma 14.5 using both the package installer and Homebrew, and despite the installations purportedly completing successfully, BlackHole never shows up in Audio MIDI Setup, even after restarting the computer. I've attempted installing both the 2ch and the 16ch versions with the same result, and used the package uninstallers in between each installation attempt.
Is this normal behavior on this hardware or software/OS version? I do have some multi-output devices already configured - could this be causing the issue? Both identical iMacs encounter the same problem.
Now, even after running the package uninstaller attempting to reinstall using homebrew, it gives the error "Warning: Not upgrading blackhole-2ch, the latest version is already installed"
Thanks.
Reproduction Steps
Expected Behavior
After this process, I would expect "BlackHole" to appear as an audio device in Audio MIDI Setup, but it does not.
Screenshots
No response
The text was updated successfully, but these errors were encountered: