Posts: 12
Joined: Jul 2012
Reputation:
0
matli
Junior Member
Posts: 12
Since I upgraded my XBMC to Frodo (at least RC2 and RC3), my XBMC computers (Ubuntu Linux) does not show up as Airplay devices on my OS X 10.8.2 computers.That is, they are not available for selection in Sound Preferences.
They do however show up in iTunes, and appears to work well from there. They also show up on my iOS devices (both iOS 5 and iOS 6).
The problem with this is that I can't play audio from other applications than iTunes on my computer.
I can also see the devices in Bonjour Browser, and the entries there looks fairly similar to a Shairport-device which does show up in the device list.
Any ideas?
Posts: 16,946
Joined: Feb 2011
Reputation:
256
turn off and on xbmc and reboot network devices. At some point it will appear and work in the osx audio output selector.
AppleTV4/iPhone/iPod/iPad: HowTo find debug logs and everything else which the devs like so much:
click here
HowTo setup NFS for Kodi:
NFS (wiki)
HowTo configure avahi (zeroconf):
Avahi_Zeroconf (wiki)
READ THE IOS FAQ!:
iOS FAQ (wiki)
Posts: 16,946
Joined: Feb 2011
Reputation:
256
Well nothing more that i can tell you. Its a problem of osx picking up the announcment and i'm aware of it - but have no clue what i could do to improve it (since it is the os which needs to pickup the announcment). As said i diddled with it at some point and it just showed up - as of then it always worked.
AppleTV4/iPhone/iPod/iPad: HowTo find debug logs and everything else which the devs like so much:
click here
HowTo setup NFS for Kodi:
NFS (wiki)
HowTo configure avahi (zeroconf):
Avahi_Zeroconf (wiki)
READ THE IOS FAQ!:
iOS FAQ (wiki)
Posts: 12
Joined: Jul 2012
Reputation:
0
matli
Junior Member
Posts: 12
I did some experimenting with Shairport (which is quite simple, since it's more or less just a perl script). I found out that if I announce the AirTunes service as MAC-address@systemname (e.g. "5403A52322@Livingroom"), it does not show up as an audio device. However, if I replace the MAC address with any other number (it's enough to change just one digit), everything works fine.
Xbmc does currently announce itself as MAC-address@systemname in just that way which doesn't work. If I had a working development environment set up for xbmc, which I unfortunately don't have, I would try changing that to something different. (Shairport by default simply uses some hash made up from the system name.)
Maybe this could be some clue? I don't know if there is some reason for having chosen the MAC address as the identifier, or if there is some reason for OSX to hide the device if that is the case. But it seems like that is what's happening here anyway.
Posts: 19,982
Joined: May 2009
Reputation:
451
nickr
Retired Team-Kodi Member
Posts: 19,982
put a ticket in trac, you cannot expect developers to trawl the forums looking for patches.
If I have helped you or increased your knowledge, click the 'thumbs up' button to give thanks :) (People with less than 20 posts won't see the "thumbs up" button.)
Posts: 922
Joined: Jul 2008
Reputation:
6
hopefully this will make it in .. i too have noticed AirPlay being finicky .. was working before and now all of a sudden its not there anymore and i even rebooted my iphone, ipad and xbmc box
Posts: 16,946
Joined: Feb 2011
Reputation:
256
2013-01-09, 18:21
(This post was last modified: 2013-01-09, 18:22 by Memphiz.)
Guys i feel more then uncomfortable to change something basic like that. I tried to mimic the AppleTV2 as close as possible when it comes to all the announcement stuff. And it has a reason that the mac is used for roap announcement as you already figured. (there are more - which i don't remember anymore).
If this is the problem i would like to know why the AppleTV2 shows up in osx then? It uses the "AppleTV2,1" string. I know it is hard - but this whole airplay stuff is reverseengineering and i will not implement something like that - even if you tell me everything is working. Once we release a version with this changed 100s of users will test it and i bet hell will break loose when this change means regressions to other users.
Though appreciate you work and findings - but i need a better explenation for why this will fix the problem and why it won't cause regression with one of the various other airplay apps.
What i can think of in theory is that apples mountain lion checks the announcement in something like this.
if "AppleTV2,1" is announced AND announced MacAddress matches one of Apples Ranges AND the airplayclient really owns this macadress (arp request maybe?)
Only then show it up as a target
end
To prove this you would need to spoof an appletv2,1 macadress in the announcment AND on the ethernet card.
At least for frodo we will not do any quickshots in regard to this. I know airplay is buggy for some people but its to risky to just change it because of it works better with the change for somebody.
AppleTV4/iPhone/iPod/iPad: HowTo find debug logs and everything else which the devs like so much:
click here
HowTo setup NFS for Kodi:
NFS (wiki)
HowTo configure avahi (zeroconf):
Avahi_Zeroconf (wiki)
READ THE IOS FAQ!:
iOS FAQ (wiki)
Posts: 12
Joined: Jul 2012
Reputation:
0
matli
Junior Member
Posts: 12
I see, and fully respect, your concerns.
At least for me, it significantly lowers the WAF of xbmc if we are unable to stream Spotify from our laptops. But it is of course hard to estimate how many user this regression affects since we don't fully see the logic behind.
I tried your suggestion of spoofing an AppleTV2 MAC address in the announcement and on the ethernet card with no luck, so it seems that there is something else happening. However, I don't have access to any ATV2, so I am not fully certain that the chosen MAC address (58:55:CA:0E:C6:72) is a real ATV2. Neither have I any possibility to have a look at a real ATV2 announcement to see if xbmc is missing something.
Wouldn't it be possible to let users change the identification string by using advancedsettings.xml? Or is even that a too large change at this time?
Posts: 16,946
Joined: Feb 2011
Reputation:
256
2013-01-10, 11:38
(This post was last modified: 2013-01-10, 11:39 by Memphiz.)
Its hard to push advancedsettings through the team review at this moment i'm afraid. Well i have the original announcements and even if i copy it 1:1 i don't get the same behaviour as with the original atv2 - seems apple does something special hidden somewhere in ML.
BTW - this is not a regression. Its like it was since AirPlay was added to XBMC. (though i know that its a problem of course).
AppleTV4/iPhone/iPod/iPad: HowTo find debug logs and everything else which the devs like so much:
click here
HowTo setup NFS for Kodi:
NFS (wiki)
HowTo configure avahi (zeroconf):
Avahi_Zeroconf (wiki)
READ THE IOS FAQ!:
iOS FAQ (wiki)