AirSonos + High Sierra - Githubissues

dubzeebass commented 7 years ago

Hi there,

Got everything all loaded, the hashes show up in the Terminal app, but I can't select output to any of the Sonos in any Sound dialog in 10.13.

Anyone have any ideas for a workaround? Im thinking it has to do with AirPlay 2. Love to find a workaround!!!

crhuber commented 7 years ago

Im having the same problem

dubzeebass commented 7 years ago

I have 2x Sonos Play 3, and 1x Sonos Play 1. All on the same network. They aren't showing up! Any ideas?

I, too, am using SonoAir.

dubzeebass commented 7 years ago

The LED button in the settings for those different speakers does turn on and off the LED, so they're talking to each other. OSX just doesn't see them as an AirPlay speaker.

miho commented 7 years ago

SonoAir uses airsonos for the audio stream, i.e., airplay while the code for controlling the sonos speakers (volume and LED) is implemented in Java. miho/SonoAir#24

MorsePacific commented 7 years ago

I'm having the same issue; just installed AirSonos after finding out about it, but upgraded to High Sierra a few days ago. Install seemed to go just fine but I can't select any speakers from MacOS.

pwhitey commented 7 years ago

Have reinstalled homebrew, node and airsonos and can report the same problem. Sets up the tunnel for my two devices but they don't show as output devices.

DigitalCaveman commented 7 years ago

Having the same problem! Weird thing is that when I quit airsonos with 'ctrl+c' my sonos PLAY:1 shows up for a second but doesn't when airsonos is running.

kilsen commented 7 years ago

Having the same problem. MacBook Pro with Mac OS High Sierra. Tunnels are opened, but they don't appear on my Mac as available output devices. My iPhone shows them, but when I attempt to select one on my iPhone, airsonos crashes on the Mac with the following error:

crypto.js:238 this._handle.initiv(cipher, toBuf(key), toBuf(iv)); ^

Error: Invalid key length at Error (native) at new Decipheriv (crypto.js:238:16) at Object.Decipheriv (crypto.js:235:12) at Object.decryptAudioData (/usr/local/lib/node_modules/airsonos/node_modules/nodetunes/lib/helper.js:141:25) at RtpServer. (/usr/local/lib/node_modules/airsonos/node_modules/nodetunes/lib/rtp.js:32:23) at emitTwo (events.js:106:13) at Socket.emit (events.js:191:7) at UDP.onMessage (dgram.js:540:8)

philippe44 commented 7 years ago

As @stephen does not seem to maintain it, you can try my version here https://github.com/philippe44/AirConnect. I don't know if it works on High Sierra, I have not tested

pwhitey commented 7 years ago

@philippe44 I can give it a test - does AirConnect install through npm or brew? thanks

miho commented 7 years ago

@philippe44 congrats! Works fine for me. I also like the amount of work you put into the CLI. I am thinking about adding AirConnect support to SonoAir as an alternative to airsonos.

@pwhitey just use the binaries in the bin folder. After downloading/cloning this repository the following commands should be sufficient:

cd /path/to/AirConnect/bin
chmod +x airupnp-osx-multi
./airupnp-osx-multi

kilsen commented 7 years ago

@philippe44 Very nice! . . . I tried it with my High Sierra. The Sonos speakers appear as audio output devices. The IP address of each Sonos speaker pair appears, but not the room name. I can surely work around that. Once I select a Sonos as the output device, the sound comes through. (I did notice that with a YouTube video, the sound is very "choppy" -- it's as if someone is continuously toggling it on and off. But this does not happen with other audio; perhaps it's related to buffering.)

philippe44 commented 7 years ago

Yes, it's probably related to buffering. Did you set the latency parameters to at least by adding -l 1000:2000 to the command line? About the names, you can produce a config file and then change the name under which the player appear in AirPlay

rkpatel33 commented 7 years ago

@philippe44 Works great for me too on macOS HighSierra, thanks! The responsiveness is very snappy.

It was a little unclear how to use it, would be worthwhile dressing up the README a bit, but thanks for this!

philippe44 commented 7 years ago

Can you help me by telling what was unclear in the README? What should I change?

[edit]: I've tried to update it a bit, hope it's better now. I've removed all dependency to other shared libs (except openSSL, but I expect everybody has it now) but I can't build an install package for each system, this is too much work

rkpatel33 commented 7 years ago

For me, it was not clear that there were runnable binaries in the bin/ folder, so I keep looking for installation instructions. So maybe just some explanation on that, including these commands:

cd /path/to/AirConnect/bin chmod +x airupnp-osx-multi ./airupnp-osx-multi

Maybe even instructions on re-compiling for those who are not familiar with it.

Rishi Patel | mail@rishinyc.com

On Sun, Nov 5, 2017 at 11:21 AM, philippe44 notifications@github.com wrote:

Can you help me by telling what was unclear in the README? What should I change?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/stephen/airsonos/issues/383#issuecomment-341997779, or mute the thread https://github.com/notifications/unsubscribe-auth/ADn5wdg6O6MVdWEfnegb1USN8kQt-wcuks5szgrWgaJpZM4Pok_T .

kilsen commented 7 years ago

@philippe44 I added "-l 1000:2000" to the command line and that seems to have solved the buffering issue. I also produced a config file (using "-i") and then edited the names in the XML file so that they reflect the "friendly" names of the Sonos speakers (i.e., the Rooms). Note that the "-x" command line option seems to require that I also specify the name of the config file; if I simply name the file "config.xml" in the current directory (the default according to the -h command line help), I get a Segmentation fault: 11.

philippe44 commented 7 years ago

The -x switch requires a filename. If you want to use "config.xml" which is the default, don't specify -x at all. I agree that it should not segfault, still :-) I'll correct that in next release