-
Notifications
You must be signed in to change notification settings - Fork 256
Could not connect to "AirSonos @ Kitchen" #38
Comments
Hey @RJ - In general, these pop up when OS X can't talk to nodetunes properly and gives up on the connection. Would you mind trying the nodetunes example to see if that's working at all? Something like...
You should see |
Heh, funny that @RJ and I have the same issue. o/ |
Selecting "nodetunes stdout" as my airplay target gives an error message like above: It builds fine, the tests all pass if i run gulp. |
oh nodetunes is your project too, hah - was about to file a bug over there :) I'd love to get this working, if you have any suggestions on how to debug i'm happy to dig in. |
I have the same problem and followed @stephen 's instructions. When I try to enable "Nodetunes Stdout" in iTunes I get:
and the server crashes with this error:
All test pass when I run gulp. |
@JasonSuave - that's likely a couple other issues: #27 and possibly #33 (that is - Yosemite isn't supported well right now, and you might be using node 0.11.x). @RJ and @jherskowitz - sorry for the delay here, it seems the core problem is getting nodetunes to play nice with your devices. Unfortunately, I currently don't have great tooling set up in nodetunes for debugging network issues (apart from sticking some Would it be possible to trouble either of you for a wireshark dump of what happens when you try to choose nodetunes from the system audio? Steps would be something like recording on the loopback (lo0) device, and looking for HTTP/RTSP traffic on a port between 5000-5050. You can then right click on one of those items and -> Follow TCP stream, which would come out looking something like the first image here: https://medium.com/@stephencwan/hacking-airplay-into-sonos-93a41a1fcfbb. |
Hey @RJ and @jherskowitz - I've added a --verbose flag that dumps some of the network back and forth that could be useful to debug what's going on here. Would be appreciated if either of you could try this out and dump the output:
|
It's connecting/working now for me, but the audio is pretty distorted and choppy. |
Hm, any ideas what changed (perhaps networking?) between then and now that made it work? Not sure about the distorted audio, but it usually hints at: a) poor connectivity, or b) machine isn't powerful enough for the encoding process (i.e. raspberry pi) (that being said, more intelligent buffering is something that should happen in nodetunes..) |
I was having some bad networking issues (was also causing Airfoil to drop connections repeatedly) that was resolved last week with the OS X 10.10.1 update - maybe related? FWIW, I'm running on a 2011 Macbook Air (1.8Ghz Core i7). |
just tried master, and it's working now 👍 I have an office zone (2x play3+ sub), and a kitchen zone (1x play5) usually grouped together. it doesn't seem to handle groups or zones with multiple speakers too well. It plays out of all the speakers in my office zone once i select the correct one from the list. Not sure if there's a nicer way to handle that via airplay, lmk if you want me to do any other debugging. |
Just released 0.1.1 which should support grouped rooms better. Might be some rough edges to work through though. @stephencwan On Fri, Feb 13, 2015 at 7:17 AM, Richard Jones notifications@github.com
|
I have the same issue, here is the output from the vebose setting: When I select the device, it gives the message "the selected device has no output controls": OS X: 10.9.5 Any ideas ? Searching for Sonos devices on network... |
I tried to run this with the '--verbose' flag and it worked. however, when i ran the server without the '--verbose' flag it keeps disconnecting after I select the SONOS speakers on the iPhone. |
It detects my sonos, but "could not connect" to whichever one i try. I ungrouped my sonos devices and tried to play on a single-device one, but same problem (none of the devices work, same error).
The text was updated successfully, but these errors were encountered: