search

philippe44 / AirConnect

Use AirPlay to stream to UPnP/Sonos & Chromecast devices
Other
3.44k stars 217 forks source link

Terminal not running after these lines #359

Closed dennisyjz closed 2 years ago

dennisyjz commented 2 years ago

Hi,

I'm running on the latest version of Mac OS Big Sur and it seems that after following the guide, the executable only runs three lines and then gets stuck. What might be going wrong here? [19:59:54.815479] main:1420 Starting airupnp version: v0.2.50.5 (May 24 2021 @ 15:14:58) [19:59:54.816141] main:1428 no config file, using defaults [19:59:54.817051] Start:1130 Binding to 192.168.1.125:49152

philippe44 commented 2 years ago

It's not stuck but no device is detected

shmkane commented 2 years ago

Wanted to add that I'm having the same results on a Windows 10 Home (OS Build 19042.1052).

Running through WSL Ubuntu 20.04 produces the same output as well. I've tried disabling my Firewall as well as allowing the ports listed, no difference. 

Edition Windows 10 Home
Version 20H2
Installed on    ‎12/‎3/‎2020
OS build    19042.1052
Experience  Windows Feature Experience Pack 120.2212.2020.0

Output when running aircast-win.exe

[17:36:10.781] main:960 Starting aircast version: v0.2.50.5 (May 24 2021 @ 15:12:29)                                 

[17:36:10.781] main:968 no config file, using defaults                                                               

[17:36:10.781] Start:720 Binding to 192.168.64.1

Worth mentioning that the PC this is running on is wired (ethernet). What I'm trying to do is open the airplay menu on my apple devices and look for something new, but I only see my current devices.

UPDATE: Seems to be working fine on my Mac mini that's wireless. Wonder if being wired has something to do with it. Wondered if @dennisyjz is also wired

pwt commented 2 years ago

Wanted to add that I'm having the same results on a Windows 10 Home (OS Build 19042.1052). ... UPDATE: Seems to be working fine on my Mac mini that's wireless. Wonder if being wired has something to do with it. Wondered if @dennisyjz is also wired

[Edit: the following applies to airupnp, not aircast, but something similar may apply.]

For some reason, your speakers are not being discovered. This is usually because the SSDP multicast discovery packets aren't reaching the interface that AirConnect is bound to. Typical reasons for this:

  1. Firewall
  2. Defective router that does not forward multicast packets between its wired and wireless interfaces
  3. Sonos system on a different subnet or VLAN

Obviously, in your case, I'd check out No. 2.

philippe44 commented 2 years ago

Closed for inactivity