search

owntone / owntone-server

Linux/FreeBSD DAAP (iTunes) and MPD audio server with support for AirPlay 1 and 2 speakers (multiroom), Apple Remote (and compatibles), Chromecast, Spotify and internet radio.
https://owntone.github.io/owntone-server
GNU General Public License v2.0
2.09k stars 235 forks source link

Pioneer airplay receiver #458

Closed jshep321 closed 6 years ago

jshep321 commented 6 years ago

Hi, My pioneer receiver works fine with airplay from itunes, but not 24.2. Do the log snippets below point to a remedy? The likely problem here: [2017-12-11 12:17:26] [ LOG] raop: No response from 'Pioneer VSX-1130 AE41D0' (127.0.0.1) to OPTIONS request

Full service log (and play attempt at the end):

mdns: Avahi Browser: NEW service '745E1CAE41D0@Pioneer VSX-1130 AE41D0' type '_raop._tcp' proto 0 [2017-12-11 12:17:05] [DEBUG] mdns: Avahi Resolver: resolved service '745E1CAE41D0@Pioneer VSX-1130 AE41D0' type '_raop._tcp' proto 0, host Pioneer-VSX-11 30-AE41D0.local [2017-12-11 12:17:05] [DEBUG] mdns: Avahi Record Browser (Pioneer-VSX-1130-AE41D0.local, proto 0): NEW record 127.0.0.1 for service type '_raop._tcp' [2017-12-11 12:17:05] [DEBUG] raop: Event for AirPlay device Pioneer VSX-1130 AE41D0 (port 5000, id 745e1cae41d0) [2017-12-11 12:17:05] [ INFO] raop: AirPlay 745E1CAE41D0@Pioneer VSX-1130 AE41D0: no pw field in TXT record, assuming no password protection [2017-12-11 12:17:05] [ INFO] raop: Adding AirPlay device 745E1CAE41D0@Pioneer VSX-1130 AE41D0: password: 0, encrypt: 0, metadata: 1, type Other, address 127.0.0.1:5000 [2017-12-11 12:17:05] [DEBUG] db: Running query 'SELECT s.selected, s.volume FROM speakers s WHERE s.id = 127947556930000;' [2017-12-11 12:17:05] [DEBUG] dacp: DACP request: /ctrl-int/1/getspeakers?session-id=1059908915

[2017-12-11 12:17:26] [DEBUG] player: The AirPlay device 'Pioneer VSX-1130 AE41D0' is selected [2017-12-11 12:17:26] [DEBUG] player: Activating AirPlay device 'Pioneer VSX-1130 AE41D0' [2017-12-11 12:17:26] [DEBUG] raop: Building OPTIONS for 'Pioneer VSX-1130 AE41D0' [2017-12-11 12:17:26] [DEBUG] player: Set 160172206178 device 244357356563886 [2017-12-11 12:17:26] [DEBUG] player: Set 215693310745552 device 244357356563886 [2017-12-11 12:17:26] [DEBUG] player: Set 237702317238052 device 244357356563886 [2017-12-11 12:17:26] [DEBUG] player: Set 127947556930000 device 244357356563886 [2017-12-11 12:17:26] [DEBUG] player: Set 251575820475804 device 244357356563886 ... [2017-12-11 12:17:26] [DEBUG] mpd: Listener callback called with event type 8. [2017-12-11 12:17:26] [DEBUG] mpd: Notify clients waiting for idle results: 8 [2017-12-11 12:17:26] [ LOG] raop: No response from 'Pioneer VSX-1130 AE41D0' (127.0.0.1) to OPTIONS request [2017-12-11 12:17:26] [DEBUG] player: Callback from AirPlay to device_activate_cb [2017-12-11 12:17:26] [DEBUG] main: Command has 0 pending events [2017-12-11 12:17:26] [ LOG] dacp: Speakers de/activation failed! [2017-12-11 12:17:26] [DEBUG] dacp: DACP request: /ctrl-int/1/getspeakers?session-id=1059908915 [2017-12-11 12:17:26] [DEBUG] httpd: Gzipping response

couteau commented 6 years ago

My guess is the problem is that the ip address for the pioneer is resolving to 127.0.0.1 (i.e., localhost) -- it should resolve to a real ip address somewhere on your local network. Seems most likely to be a problem with the Pioneer's compliance with the Zeroconf/MDNS protocol or with Avahi rather than with forked-daapd.

On Mon, Dec 11, 2017 at 9:56 PM, jshep321 notifications@github.com wrote:

Hi, My pioneer receiver works fine with airplay from itunes, but not 24.2. Do the log snippets below point to a remedy? The likely problem here: [2017-12-11 12:17:26] [ LOG] raop: No response from 'Pioneer VSX-1130 AE41D0' (127.0.0.1) to OPTIONS request Full service log (and play attempt at the end): mdns: Avahi Browser: NEW service '745E1CAE41D0@Pioneer VSX-1130 AE41D0' type '_raop._tcp' proto 0 [2017-12-11 12:17:05] [DEBUG] mdns: Avahi Resolver: resolved service '745E1CAE41D0@Pioneer VSX-1130 AE41D0' type '_raop._tcp' proto 0, host Pioneer-VSX-11 30-AE41D0.local [2017-12-11 12:17:05] [DEBUG] mdns: Avahi Record Browser (Pioneer-VSX-1130-AE41D0.local, proto 0): NEW record 127.0.0.1 for service type '_raop._tcp' [2017-12-11 12:17:05] [DEBUG] raop: Event for AirPlay device Pioneer VSX-1130 AE41D0 (port 5000, id 745e1cae41d0) [2017-12-11 12:17:05] [ INFO] raop: AirPlay 745E1CAE41D0@Pioneer VSX-1130 AE41D0: no pw field in TXT record, assuming no password protection [2017-12-11 12:17:05] [ INFO] raop: Adding AirPlay device 745E1CAE41D0@Pioneer VSX-1130 AE41D0: password: 0, encrypt: 0, metadata: 1, type Other, address 127.0.0.1:5000 [2017-12-11 12:17:05] [DEBUG] db: Running query 'SELECT s.selected, s.volume FROM speakers s WHERE s.id = 127947556930000;' [2017-12-11 12:17:05] [DEBUG] dacp: DACP request: /ctrl-int/1/getspeakers? session-id=1059908915

[2017-12-11 12:17:26] [DEBUG] mpd: Listener callback called with event type 8. [2017-12-11 12:17:26] [DEBUG] mpd: Notify clients waiting for idle results: 8 [2017-12-11 12:17:26] [ LOG] raop: No response from 'Pioneer VSX-1130 AE41D0' (127.0.0.1) to OPTIONS request [2017-12-11 12:17:26] [DEBUG] player: Callback from AirPlay to device_activate_cb [2017-12-11 12:17:26] [DEBUG] main: Command has 0 pending events [2017-12-11 12:17:26] [ LOG] dacp: Speakers de/activation failed! [2017-12-11 12:17:26] [DEBUG] dacp: DACP request: /ctrl-int/1/getspeakers? session-id=1059908915 [2017-12-11 12:17:26] [DEBUG] httpd: Gzipping response

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/ejurgensen/forked-daapd/issues/458, or mute the thread https://github.com/notifications/unsubscribe-auth/ABhx0GABp54je7fooJKQArAgHWdHUc3-ks5s_etAgaJpZM4Q-WMt .

ejurgensen commented 6 years ago

Yes, I agree with couteau, it is a strange address for the device to announce. I wonder how iTunes is getting the correct address. Maybe the device makes multiple announcements? Could you test with either 25.0 or even better, with a build from the master branch? I have made some mdns changes since 24.2 that may or may not help.

jshep321 commented 6 years ago

Hi, Silly question: is it feasible to upgrade to 25.0 and then roll back to 24.2? I installed from the raspbian repo and I suspect my upgrades would forever break after a manual update.

ejurgensen commented 6 years ago

You can roll back, but you would need to delete the database first. However, if you are on Raspbian, you can upgrade to 25.0 by using the build I distribute and then you shouldn't need to roll back. See the instructions here: https://www.raspberrypi.org/forums/viewtopic.php?t=49928

ejurgensen commented 6 years ago

By database, I mean /var/cache/forked-daapd/songs3.db and cache.db. They will be recreated by forked-daapd on startup. If you delete the databases, you will have to re-pair remotes.

jshep321 commented 6 years ago

Hi,

Yep -- 25.0 fixed the following: Pioneer, new apple TV, and Amazon Fire Stick (using "Airbuddy" app as airplay client).

Also verified on old airport express, shairport-sync and rogue amoeba's "airplay speakers" apps.

The docs about the remote pairing needs to be updated since the remote file requirements no longer need the name. That was a confusing bit... :)

ejurgensen commented 6 years ago

That’s good to hear. What docs are you referring to? They should be updated.

jshep321 commented 6 years ago

You are correct--they are updated. I was looking at an old version.