<div dir="ltr"><div>Thanks</div><div><br></div><div>It works as expected with version `0.3.70-2` from experimental.</div><div><br></div><div>Cheers,</div><div>Landry<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Le mar. 2 mai 2023 à 15:41, Alban Browaeys <<a href="mailto:alban.browaeys@gmail.com">alban.browaeys@gmail.com</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Likely an upstream issue.<br>
<br>
I see the headset mic has an IPv6 address:<br>
address = [2a01:e0a:8db:8861:dead:beef:0:f0f8]<br>
while advertised as IPv4.<br>
<br>
pipewire now filter IPv6 zeroconf advertisment in its zeroconf-discover<br>
module to avoid showing duplicate entries (one for IPv4 the other for<br>
IPv6) in the client UI this might be related.<br>
The fact that no IPv4 service is advertised (well it is but with an<br>
IPv6 address) might explain why the pipewire zeroconf discover module<br>
hide your headless mic.<br>
You could try older pipewire debs (<a href="http://snapshot.debian.org" rel="noreferrer" target="_blank">snapshot.debian.org</a>) as this IPv6<br>
hide was introduced recently or simply open a bug in the upstream bug<br>
tracker. This was introduced due to<br>
<a href="https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2031" rel="noreferrer" target="_blank">https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2031</a><br>
<br>
The change was made on the publishing side ie the server is the one<br>
were you should downgrade pipewire. The version that introduced this<br>
behaviour is 0.6.32 so downgtrading to 0.6.31 will do. see<br>
<a href="https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2861" rel="noreferrer" target="_blank">https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2861</a><br>
<br>
The fact that an IPv6 address is published in an IPv4 entry might be<br>
another upstream pipewire bug namely inhte zeroconf-publish module.<br>
Though before reporting to upstream you should try at least pipewire<br>
0.3.70 from debian experimental (and maybe even upstream code).<br>
<br>
Mind that for me 0.3.70 module-zeroconf-discover module might crash on<br>
startup but this is another issue that I am investigating. Might not<br>
crash for you (the crash depends on the server box adverstising which<br>
will be different for your setup). upstream git code is also affected.<br>
This is <a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035280" rel="noreferrer" target="_blank">https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035280</a> not<br>
yet reported upstream (as I have a hard time to reproduce properly with<br>
my git master build).<br>
<br>
<br>
Cheers,<br>
Alban<br>
<br>
<br>
On Tue, 21 Feb 2023 14:45:03 +0100 Landry MINOZA<br>
<<a href="mailto:landry.minoza@gmail.com" target="_blank">landry.minoza@gmail.com</a>> wrote:<br>
> Package: libpipewire-0.3-modules<br>
> Version: 0.3.65-2<br>
> Severity: normal<br>
> <br>
> Dear Maintainer,<br>
> <br>
> Trying to use remote devices with pipewire, I don't see some devices<br>
> (specificaly a headset mic in my case).<br>
> Reproduce on 2 sid clients.<br>
> <br>
> I load zeroconf module:<br>
> <br>
> pactl load-module module-zeroconf-discover<br>
> <br>
> When listing available devices:<br>
> Audio<br>
> ├─ Devices:<br>
> │ 42. Audio interne [alsa]<br>
> │<br>
> ├─ Sinks:<br>
> │ * 45. Audio interne Stéréo analogique [vol: 0.40]<br>
> │ 62. Starship/Matisse HD Audio Controller Stéréo analogique on<br>
landry@demetra [vol: 1.00]<br>
> │ 64. [G533 Wireless Headset Dongle] [vol: 1.00]<br>
> │<br>
> ├─ Sink endpoints:<br>
> │<br>
> ├─ Sources:<br>
> │ * 46. Audio interne Stéréo analogique [vol: 1.00 MUTED]<br>
> │ 60. Starship/Matisse HD Audio Controller Stéréo analogique on<br>
landry@demetra [vol: 1.00]<br>
> │<br>
> ├─ Source endpoints:<br>
> │<br>
> └─ Streams:<br>
> <br>
> The headset mic (source [G333 Wireless Headset Dongle] is exposed by<br>
> avahi:<br>
> <br>
> ❯ avahi-browse --resolve _pulse-source._tcp -t<br>
> + wlan0 IPv4 landry@demetra: [G533 Wireless Headset Dongle] Mono<br>
PulseAudio Sound Source local<br>
> + wlan0 IPv4 landry@demetra: Starship/Matisse HD Audio Controller<br>
St__r__o a PulseAudio Sound Source local<br>
> = wlan0 IPv4 landry@demetra: [G533 Wireless Headset Dongle] Mono<br>
PulseAudio Sound Source local<br>
> hostname = [demetra.local]<br>
> address = [2a01:e0a:8db:8861:dead:beef:0:f0f8]<br>
> port = [4713]<br>
> txt = ["description=[G533 Wireless Headset Dongle] Mono"<br>
"subtype=hardware" "channel_map=mono" "format=s16le" "channels=1"<br>
"rate=48000" "device=alsa_input.usb-Logitech_G533_Gaming_Headset-<br>
00.mono-fallback" "cookie=0x4a6f9a3a" "fqdn=demetra" "uname=Linux<br>
x86_64 6.1.0-5-amd64" "user-name=landry" "server-version=PipeWire<br>
0.3.65"]<br>
> = wlan0 IPv4 landry@demetra: Starship/Matisse HD Audio Controller<br>
St__r__o a PulseAudio Sound Source local<br>
> hostname = [demetra.local]<br>
> address = [10.0.0.144]<br>
> port = [4713]<br>
> txt = ["description=Starship/Matisse HD Audio Controller<br>
St\195\169r\195\169o analogique" "subtype=hardware" "channel_map=front-<br>
left,front-right" "format=s32le" "channels=2" "rate=48000"<br>
"device=alsa_input.pci-0000_0a_00.4.analog-stereo" "cookie=0x4a6f9a3a"<br>
"fqdn=demetra" "uname=Linux x86_64 6.1.0-5-amd64" "user-name=landry"<br>
"server-version=PipeWire 0.3.65"]<br>
> <br>
> On the remote host, this source is visible and usable:<br>
> Audio<br>
> ├─ Devices:<br>
> │ 44. GM204 High Definition Audio Controller [alsa]<br>
> │ 46. [G533 Wireless Headset Dongle] [alsa]<br>
> │ 47. Starship/Matisse HD Audio Controller [alsa]<br>
> │ 122. Fairphone 4 5G [bluez5]<br>
> │<br>
> ├─ Sinks:<br>
<br>
</blockquote></div><br clear="all"><br><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature">Landry MINOZA<br><a href="mailto:landry.minoza@gmail.com" target="_blank">landry.minoza@gmail.com</a></div>