#495: Output to an RAOP sink skips
-----------------------+----------------------------------------------------
Reporter: clconway | Owner: coling
Type: defect | Status: new
Milestone: | Component: module-raop-*
Resolution: | Keywords: module-raop-sink skip
-----------------------+----------------------------------------------------
Changes (by bnb):
* cc: b...@rompatroullie.de (added)
Comment:
Hi all,
i encounter the same problem. Didn't solve it, but here are some details
which might help to track down the issue (i use pulseaudio 0.9.15 from
debian stable):
1. I own 2 airport expresses. The choppy output only occurs at the new 802
.11n-version (firmware version 7.4.2) of the device. My old-generation
version (802.11bg, firmware version 6.3) is not affected.
2. As stated before, the problem doesn't occur with the raop_play client
or itunes as the client.
3. The problem seems not related to the WLAN component or bandwidth, since
i stream across a FastEthernet network (actually i deactivated the
wireless radio on the device) and the used bandwidth is far from
saturated.
4. The advice from peitschie above (to deactivate other pulseaudio-
devices/-sinks) could be explained by a strange pulseaudio-behavior i
observed: If both AEX devices are configured in pulseaudio via separate
"module-raop-sink" lines (manually; "module-raop-discover" not used), but
only the "problematic" AEX is marked as an active sink, a wireshark dump
suggests that the output seems to be nonetheless streamed to _both_ AEX
devices. This seems like a bug to me, but maybe someone knows better...
;-)
5. Unfortunately the issue in 4. does not seem to be the whole story: I
still get choppy output on my problemativ AEX even if i deactivate any
other sink in my pulseaudio-configuration.
6. Although not directly related to the choppy sound, but maybe to the
described problems with auto-discovery of devices: I see a strange
behaviour of my new-generation/problematic AEX concerning Bonjour/Avahi
service announcements. I configured a fixed RFC1918-IP on the device,
which can be used to successfully connect to it. But if i look into the
mdns-announcements, the AEX announces an unrelated APIPA-address, which is
then used by the module-raop-discover. Seems like a bug in the (new
generation-)AEX-firmware.
--
Ticket URL: <http://pulseaudio.org/ticket/495#comment:23>
PulseAudio <http://pulseaudio.org/>
The PulseAudio Sound Server
_______________________________________________
pulseaudio-tickets mailing list
pulseaudio-tickets@mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-tickets
