pulseaudio + zeroconf. zeroconf info only updated *once*

[jnelson]

pulseaudio's zeroconf module appears to correctly identify other audio sources that are available, but only when it is loaded. it should set up a thread or other process or time or /something/ to periodically (or via the avahi API) poll for added and removed devices. Otherwise, one must typically kill and restart the pulseaudio server (easy, but painful) or unload and reload the zeroconf discover module (hard, but not very painful).

[coling]

This is how it works currently. It will wait for callbacks from avahi and take appropriate action. I'm not 100% sure how the avahi side of things works, but the chances are that restarting/reloading the module triggers a rescan or similar.

For me they always show up, although it's not immediate - there is some delay.

Anyway, just wanted to point out that the summary is totally wrong, but perhaps there is something that can be done to make it work in a more responsive way.

Will need Lennart to comment on that, but he wont reply for a few weeks.

[lennart]

Sounds as if mcast is broken on your machine or so (firewall?), because this is exactly how it should work.

Anyway, closing since this is already implemented in PA.

[jnelson]

That is the not the behavior I was seeing - I was able to use avahi-browse to observe the changes in real time, which pulseaudio did /not/ reflect.

However, without being able to replicate it today in a brief test, I'll assume that it was a problem with older versions or something.