audio output switching to Airplay speaker does not work
Hello,
when using the command
(audio output HomePod)
it does not work. Switching to other directly connected outputs does work.
Log:
2021-11-19 15:14:24: ⚪[Homped Audio] Open >>>>>>>>>>>>>>>>>>>>> 2021-11-19 15:14:24: ⚪[Homped Audio] Processing command "audio output HomePod" 2021-11-19 15:14:24: ⚪[Homped Audio] Setting output device to (null) 2021-11-19 15:14:24: 🔴No device found matching (null) 2021-11-19 15:14:24: 🔘Generating status menu
I think this is a problem with how this works on MacOS, I had the same problem with other tools as well. Would still be nice if this would be possible.
It's likely that the HomePod isn't an actual audio device at a system level. I'd need to see what devices a tool like AudioSwitcher showed when the HomePod was connected (I don't have one of my own to test with). If it can't be accessed as a system device, Bunch won't be able to switch to it.
On 19 Nov 2021, at 8:18, Georg wrote:
Hello,
when using the command
(audio output HomePod)it does not work. Switching to other directly connected outputs does work.
Log:
2021-11-19 15:14:24: ⚪[Homped Audio] Open >>>>>>>>>>>>>>>>>>>>> 2021-11-19 15:14:24: ⚪[Homped Audio] Processing command "audio output HomePod" 2021-11-19 15:14:24: ⚪[Homped Audio] Setting output device to (null) 2021-11-19 15:14:24: 🔴No device found matching (null) 2021-11-19 15:14:24: 🔘Generating status menuI think this is a problem with how this works on MacOS, I had the same problem with other tools as well. Would still be nice if this would be possible.
-- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/ttscoff/bunch/issues/170
Yes, that is probably right, its probably not a system device.
If you have a second Mac with Monterey installed, they now work as an Airplay-Target as well. Maybe you could test it with that.
Just coming back to this a couple years later: did you try using (audio output Airplay-HomePod) and did you get different results. I still don't have a device to test with, and thus it's hard to figure out any hacks to work around the issue.