On Mon, 2014-03-10 at 12:48 +0200, Harri R wrote: > 2014-03-07 12:09 GMT+02:00 Tanu Kaskinen <tanu.kaskinen at linux.intel.com>: > > > > > > > Could you get logs from both machines? > > > > 1) remove module-tunnel-sink(-new) from default.pa if you have it there > > 2) disable autospawning on Raspi and the PC: > > echo autospawn = no > ~/.config/pulse/client.conf > > 2) start pulseaudio on Raspi and the PC with "pulseaudio -vvv" > > 3) Load the tunnel on the PC: > > pactl load-module module-tunnel-sink-new server=192.168.1.225 > > 4) Try to play something: > > paplay /usr/share/sounds/alsa/Front_Center.wav > > 5) Stop pulseaudio on Raspi and the PC with Ctrl-C. > > 6) Save the logs and put them to some pastebin (they're probably too > > large to get through to the mailing list as attachments). > > > > > Ok, here is what I did: > > raspi$ pulseaudio -vvv > > pc$ pulseaudio -vvv > > pc$ pactl load-module module-tunnel-sink-new server=192.168.1.225 > 29 > > - After this there is constant network traffic from PC to raspi. > > pc$ paplay -d tunnel-sink-new.192.168.1.225 > /usr/share/sounds/alsa/Front_Center.wav > > - Network traffic is paused, but after a while there is distorted audio > from raspi. Network traffic is recovered. > > pc$ pavucontrol > > - Network traffic is cut and ended for good. > > pc$ paplay -d tunnel-sink-new.192.168.1.225 > /usr/share/sounds/alsa/Front_Center.wav > Failed to drain stream: Timeout > pc$ > > > Logs can be found from here. I added line of dashes to logs after every > given command. > > Raspi log: > > https://drive.google.com/file/d/0B4vqDczJWwTbekNUVHBJS3N2cWM > > PC log: > > https://drive.google.com/file/d/0B4vqDczJWwTbQXg3azBJWl9kblE > > > These were the latencies of the network: > > Ping from PC In a flooded mode: > > --- 192.168.1.225 ping statistics --- > 3000 packets transmitted, 3000 received, 0% packet loss, time 5259ms > rtt min/avg/max/mdev = 1.375/1.680/18.901/0.556 ms, ipg/ewma 1.753/1.536 ms > > and with 1 sec interval: > > --- 192.168.1.225 ping statistics --- > 3000 packets transmitted, 2994 received, 0% packet loss, time 3004010ms > rtt min/avg/max/mdev = 1.565/2.001/15.767/0.505 ms > > Hopefully this helps... The logs show at least some bugs: 1) When module-tunnel-module-new is loaded, the initial configured latency for it at the raspi end is ~24 seconds, which is way too much. 2) There's a flood of D: [alsa-sink-bcm2835 ALSA] sink.c: Found underrun 58692 bytes ago (6840 bytes ahead in playback buffer) 3) The paplay latency on the pc is 4 seconds (should be 2). Unfortunately I don't have time to properly investigate this any time soon. Maybe later (I have a vacant Raspberry Pi myself, so I could try reproducing the problems). -- Tanu
