Telegram not detected on PipeWire about soundux

[D3SOX]

Are you in a call on Telegram Desktop and refreshed after the call has started?

[Curve]

I can't switch audio backend to PulseAudio, it instanly reverts back to Pipewire. In console it says:
Detected PipeWire-Pulse, please use the native pipewire backend

This is by design.
The pipewire backend will also pick up all applications that run through pipewire pulse.

The same thing is happening to me

[Goosegit11]

Are you in a call on Telegram Desktop and refreshed after the call has started?

I was recording voice message, still no devices

[Curve]

Are you in a call on Telegram Desktop and refreshed after the call has started?

I was recording voice message, still no devices

Have you tried it with other applications?
Maybe Telegram is the culprit here.

All applications I've tried got picked up fine

[Goosegit11]

well, yeah, discord works... but it's strange that telegram voice messages don't

[Curve]

well, yeah, discord works... but it's strange that telegram voice messages don't

Well now we know that telegram specifically is causing the issue and can investigate that.
It's probably caused by telegram not always pulling audio, this might already be resolved in the next update

[Goosegit11]

sorry for incovenience and misunderstanding. hope that issue will be solved in the next updates!

afaik Telegram uses OpenAL for audio

[D3SOX]

afaik Telegram uses OpenAL for audio

Can you try this workaround from our FAQ?

[Curve]

afaik Telegram uses OpenAL for audio

Can you try this workaround from our FAQ?

That should only apply to pulse audio, not pipewire

[D3SOX]

Could be that pipewire-pulse has this also implemented

[Curve]

Could be that pipewire-pulse has this also implemented

PipeWire doesn't have facilities to restrict link creation, so highly unlikely

Edit: Also said setting prevents changing of the sink, which is not what happens when using the PipeWire backend