Okay, no luck yet with AirPlay.
I've installed the trial versions of Airfoi and TuneBlade. Both programs cannot see the RaspyFi as Airplay receiver. I've tried opening ports 80, 443 and 554; these are apparently used for Airplay. But without any luck.
AirDroid app can't find the Pi either. Twonky Beam app did find the RaspyFi once, but failed to connect. After that it does not recognize the Pi anymore.

How do I enable/switch to Airplay on the Pi?

Pffew, running RaspyFi is not easy..

Yesterday I tried to connect to a shared folder on my laptop. After rebooting the Pi I was unable to connect to MPD. The Pi was still connected to the network and I could access it through SSH, but MPD was unable to connect and also the webinterface was inaccesible.
Finally, by restarting the MPD service a few times I got it working again. Restarting and debugging with the commands in the MPD Troubleshoot Wiki (http://mpd.wikia.com/wiki/Musi…..oubleshoot) does not always work. With the netstat-command however I was able to find out that the deamon was trying to run multiple instances.

This did the trick:
Stopping the server: sudo /var/run/mpd stop
Starting: sudo /var/run/mpd start

Still I cannot get Airplay working. My phone (Twonky Beam app) recognizes the Pi once, when I connect the audio is terribly slow and distorted with cracks and pops. After I stop playing, it doesn't recognize the Pi untill I reboot it. On my laptop TuneBlade and AirFoil don't see the Pi as a receiver.

I think this has something to do with the network. On my laptop, I can only access the Pi's webinterface by typing its full address, 192.168.1.149. Also I cannot access the Pi via \\Raspyfi to copy new webradio's. The other way around, the Pi cannot connect to the shared folder on my laptop.
With my smarthphone I can connect to the shared folder on my laptop and the Pi using ES File Explorer. Also, some other apps do find the Rapsyfi Airplay (but playback is very crappy).

Any ideas?

@admin

1 – Yes, but I didn't know that. Luckily it works now.
2 – See 1. Also solved that.
3 – I know. Bonjour is already installed. I discovered the problem is with my Symantec Endpoit Protection, this blocks traffic. When disabled, I can connect with the Pi via Tuneblade. However I am still figuring out how to add the exceptions in SEP to allow the Pi without having to disable my firewall alltogether.
4 – In that case MPD was not updating because there was nothing to update, no NAS or external hdd connected. It was the connection with my phone. No problem however, was only to illustrate that my phone could see the Pi as Airplay device it but my laptop couldn't.
5 – Sorry if I came over as a crybaby. Stuff just didn't work the way I expected and I couldn't find an answer since a lot of things are specific for the Pi. In the end, that's what a forum is for, right?

Anyways, in the meantime I've stumbled upon a real problem I think.
Short story: shutdown the Pi, connected my external hdd (Samsung G2 portable, 640 Gb, formatted in FAT32, filled with 103 Gb of music in flac and mp3 format) and rebooted. It started updating the DB but got stuck after a few minutes. I let it run for a few more hours while I was at the university. When I got home, MPD crashed and I could not restart it via the SSH. Rebooted the Pi, it had lost its DB and started updating. Again got stuck on the same folder. Deleted that folder, started updating again, it got stuck on the next folder. Removed the folder right before the one it gets stuck on, still keeps stalling on the same point. This is at about 45 Gb. Both webGUI and command "mpc" in SSH say the database is still updating, however no files are added.
I checked, the disk does not contain any zip/rar-files or videos (this makes xmbc crash sometimes I read). I cannot find how to view MPD's update log via SSH. How do I do that?

Haha, no problem. I also made asked some questions before doing proper research so I wouldn't blame you

About the bug, too bad. Any idea which tag type(s) cause it to stall? I already thought it had to do something with bad files or similar. I assumed it scans folder by folder in alphabetic order so I expected that removing the folder it got stuck on would do the trick. Apparantly not, unfortunately. I'm looking forward to the new release then! I guess it's not something one can easily change manually in the config?