AirSonos + High Sierra

[dubzeebass]

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]

Im having the same problem

[dubzeebass]

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]

[dubzeebass]

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]

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]

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]

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]

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]

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]

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

[miho]

@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

[pwhitey]

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

[kilsen]

@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]

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]

@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]

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]

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 | [email protected]

On Sun, Nov 5, 2017 at 11:21 AM, philippe44 ***@***.***> 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 <#383 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADn5wdg6O6MVdWEfnegb1USN8kQt-wcuks5szgrWgaJpZM4Pok_T> .

[kilsen]

@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]

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

[Cristhian12T]

@philippe44 Hello, I've seen that it worked for soo many people, your solution must had been great, I tried to run everything you explain but I am not very familiar with most of the things you talk about, I BEG YOU, CAN YOU PLEASE EXPLAIN IT TO ME STEP BY STEP, I WOULD BE SUPER HAPPY IF U CAN HELP ME.
This is my mail: [email protected]
Whatsaap: +34608426735
Please contact me, thank you...

[philippe44]

Can you describe your OS and at what stage/step you are stuck

[Cristhian12T]

Hi, thanks for replying. I literally don't know how to start, I downloaded everything you have in the website but I need help to make it run.

[Cristhian12T]

@philippe44 I answer the message in the prevues comment, I forgot to tag you. Thanks.

[philippe44]

I'm not a Mac OS expert, but you should download the airupnp.zip (the latest version) and probably, put it in any folder and click on it or right click on it so that it opens. There you should be able to extract the airupnp-osx-multi. The I suggest you google 'macOS how to make a file executable' and follow the instructions you find. If you don't find anything suitable, google 'MacOS how to open a terminal' and then go to the folder folder where you have extracted the file and follow the instructions again on the readme

[Cristhian12T]

Thank you @philippe44 I will try it tomorrow as soon as I can, I will let u know how it goes, thanks.

[Cristhian12T]

Ok I dowloaded the airupnp.zip, I opened it and executed the airupnp-osx-multi, now from this step what alse shall I do... @philippe44

[Cristhian12T]

@philippe44 please help me with a video tutorial showing how u do it please...

[Cristhian12T]

@miho Hi Michael, please can you help me understand the steps I have to follow in the solution of @philippe44, you would make my life very happy, I cant use the sonos unless it be with the app, and it is crap... thanks

[stephenjharrington]

Have now gotten AirConnect working very nicely on my MacMini running macOS 10.12.6.

@miho said "I am thinking about adding AirConnect support to SonoAir as an alternative to airsonos".

This would be a GREAT development and would be much appreciated Michael. Your SonoAir GUI front end and @philippe44 's AirConnect macOS code could be the perfect pairing?

StephenH

[igrek8]

I can confirm that osx 10.13.1 and airsonos 0.2.6 finds the device, but nothings seems to show up in the output devices.

[philippe44]

@Cristhian12T: you're using the wrong application. This one (AirCast) is for ChromeCast devices; Use airupnp-osx-multi instead and you should be good to go

[pulokidy]

I tried mine, and it didn't work as well, my imac is mid 2011, would that be the problem? i have updated to latest OSX.... using airupnp-osx-multi

[psyenz]

Got everything loaded and running but with a caveat: the latency adjusts in the wrong direction. If I set http latency to anything greater than 0, the audio gets further out of sync. If set to 0, there is about a 2 second delay. If I try setting to a negative number, then there is no audio. Any ideas? (this is on a MacBook Pro)

[philippe44]

if you're talking about airconnect, this is the wrong place. But even if this is about airsonos, you cannot have audio/video synchronization with such solutions. It's simply impossible due to the nature of the bridging being done (sync RTP to async HTTP)

[wesleymostien]

when you disconnect, the device tunnels briefly appear in the sound setting dialog

[abulgatz]

Is there any work being done to get AirSonos working with macOS 10.13 High Sierra?

[rafale77]

Finding these reports very weird... I am not able to reproduce the problems you are seeing. I have been using Airsonos with High Sierra and all the other OSX versions before this without any problem. No SonoAir, No Airconnect... just launched the server on a headless ubuntu VM.

[pockey04]

I have followed this thread and have been able to add the play 1 to output. However, when I exist out of the terminal (Osx high sierra) the sound disappears and when it does play its very choppy despite the addition of -1 1000:2000. Any recommendations?

[philippe44]

It's letter l (L) not the number -1

[pockey04]

Wow! Thanks so much. Will make the changes. Will that also resolve the exit issue? Thanks G

…

On Feb 28, 2018, at 2:20 AM, philippe44 ***@***.***> wrote: It's letter l (L) not the number -1 — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.