Version: (using KDE KDE 3.5.0) Installed from: SuSE RPMs Compiler: gcc 4.0.2 OS: Linux Since there is now a lot of detailed information for how to stream (and find) an Apple Airport Express using Rendevous, and the key has been released into the public domain, would it be possible to add support for streaming audio from amaroK to an Airport Express (Airtunes, I think they call it)? This might be a good candidate for a virtual hardware device or a KDE-abstracted arts output device instead, but I'm filing it under amaroK in the hopes that my favorite audio app will become even more useful and I won't need to keep reverting to my iTunes box just to stream audio to my stereo wirelessly. I'm willing to provide what research I have done on this topic, but I'm not really competent enough to write the code to accomplish this.
Are you sure it's been released into public domain? Can you post a link to an announcement from Apple saying so? I don't remember having heard about that...
Dupe of Bug 100513.
*** This bug has been marked as a duplicate of 100513 ***
I don't belive that this is a duplicate of bug 100513. If I understand things correctly, 100513 is about playing music that is stored in remote iTunes like servers. Were as this wish/bug is about playing music from the current machine and hearing it on remote speakers (like the airport express). This would be a very usefull thing and something I miss alot. This page has some info on doing this: http://www.ecs.soton.ac.uk/~sg02r/articles/airport.html iTunes creates a combo box were multiple output devices can be selected, if Amarok could also do something similar with the help of the info above that it would be great.
This is not a dupe of Bug 100513! Information about how AirTunes works in Apple iTunes: http://www.apple.com/airportexpress/airtunes.html
Reopening as requested
There is a HOWTO for this: http://www.jroller.com/nwinkler/entry/amarok_and_the_airport_express Perhaps this could be integrated into Amarok and polished up?
Would be nice with a integrated soultion, without the "tricks" and the known issues.
Voting for this one :) Also there should be a generic option to fast-switch output, like it is doen in iTunes with a combo box.
Oxine supports AirTunes via xine-lib. Maybe it would be easy to support AirTunes when xine is used as backend? Take a look: http://oxine.sourceforge.net/documentation.php """ Apple Airport Express Using the xine-lib audio output plugin for the Apple Airport Express which can be downloaded from the oxine subversion repository by running svn co https://oxine.svn.sourceforge.net/svnroot/oxine/trunk/xine-aex it is possible to output audio on any Apple Airport Express available on the local network. If you have the AVAHI client library installed (see above) oxine will automatically find any available Apple Airport Express and make them available in the settings menu. At the moment it is only possible to output audio via one Apple Airport Express or via the normal sound card."""
This AirPort Express XINE plugin works perfectly in OXINE, to make it work in Amarok we need to pass it a hostname/ip of Airport Express There is no way to enter this information in Amarok/Engines configuration dialog... Anyone? :)
I have added my AirportExpress IP address statically into audio_aex_out.c and it works perfectly. But someone really should teach Amarok to interpretate XINE plugins' additional configuration fields. For AEX output there are 3 configurable options: audio.device.aex_latency audio.device.aex_port audio.device.aex_host with audio.device.aex_host beeing mandatory.
There is a GPL'd library that claims to be able to connect through airtunes. Perhaps this could be used as the base of a plug-in. I would love this feature. http://sourceforge.net/projects/raop-play/
*** This bug has been confirmed by popular vote. ***
might be an idea for a scripting service?
(In reply to comment #10) > Oxine supports AirTunes via xine-lib. > Maybe it would be easy to support AirTunes when xine is used as backend? As a matter of fact, we do recommend to use the Phonon xine backend, so the mentioned plugin just has to be installed if I understand the quoted documentation correctly. As we do not handle sound directly, this is out of our hands anyway.