Arch Linux

jchillerup

Member

From: Denmark

Registered: 2011-08-10

Posts: 19

"Audio device stuck" from MPlayer using pulseaudio-raop2

Hi

I installed pulseaudio-raop2 from AUR with all of its dependencies. Used paprefs to enable Airport streaming and issued `pulseaudio -k` to restart PulseAudio. I have an Airport Express in my flat that was detected immediately, but when I try streaming my audio to it (using pasystray and pavucontrol), the player chokes. Tried with both YouTube (using flashplugin) and MPlayer; flashplugin just stops playing while MPlayer complains: "Audio device got stuck!"

I've tried VLC too, which looks like it's playing but no sound comes out of my speakers

Tried to start PulseAudio in verbose and non-daemonized mode, but even after adding autospawn=no to both /etc/pulse/client.conf and  ~/.config/pulse/client.conf and killing it using `pulseaudio -k` it still restarts.

Thanks in advance!

jchillerup

Member

From: Denmark

Registered: 2011-08-10

Posts: 19

Re: "Audio device stuck" from MPlayer using pulseaudio-raop2

So I dug a bit more, and it looks like the problem is somehow related to the IP addresses that Avahi reports downstream. Specifically, the Airport Express has a link-local IP (in the 169.254.0.0/16 range), whereas my workstation and indeed the Airport Express has an IP under 10.0.0.0/16.

I've tried to tweak the Avahi settings, but so far with no success.

jchillerup

Member

From: Denmark

Registered: 2011-08-10

Posts: 19

Re: "Audio device stuck" from MPlayer using pulseaudio-raop2

I started pulseaudio in the foreground (with -vvv) and looked at the logs. At first it couldn't connect to the IP given by Avahi, because I hadn't routed the link-local addresses given (169.154.0.0/16).

sudo route add -net 169.254.0.0 netmask 255.255.0.0 dev wlp3s0 metric 99

OK, so now I can actually ping the Airport! But, alas:

D: [pulseaudio] raop-client.c: RAOP: SETUP
D: [pulseaudio] raop-client.c: Connected to 169.254.153.32 on port 6000 (SOCK_DGRAM)
D: [pulseaudio] raop-client.c: Connected to 169.254.153.32 on port 6001 (SOCK_DGRAM)
D: [pulseaudio] raop-client.c: Connected to 169.254.153.32 on port 6002 (SOCK_DGRAM)
D: [pulseaudio] raop-client.c: Connection established (UDP;control_port=6001;timing_port=6002)
D: [pulseaudio] raop-sink.c: State change recieved, informing IO thread...
D: [pulseaudio] rtsp_client.c: Sending command: RECORD
I: [pulseaudio] module-stream-restore.c: Synced.
W: [pulseaudio] rtsp_client.c: Unexpected/Unhandled response: RTSP/1.0 500 Internal Server Error
W: [pulseaudio] rtsp_client.c: Unexpected/Unhandled response: Server: AirTunes/105.1
W: [pulseaudio] rtsp_client.c: Unexpected/Unhandled response: CSeq: 3
W: [pulseaudio] rtsp_client.c: Unexpected/Unhandled response: 

Kind of looks like an incompatibility problem to me? It could also be that the Airport doesn't bind properly to the link-local address I talk to it through?