alsa(pipewire): capture devices not working in current master

[dheijl]

OS: Linux Debian 13 Trixie
Rust 1.90
application: swyh-rs

When updating Cpal from 0.16.0 to the current Github master I see the following change in behaviour when running my app:

• memory increases from 6 MB to 11 MB
• when closing the app it takes 10 seconds after exiting main before it actually ends instead of ending instantaneously

I didn't change anything in the app, just the Cargo.toml.

Otherwise everything seems to work as axpected.

EDIT: this doesn't happen on Windows (WasApi).

[roderickvd]

Which backend is this on? There indeed is stuff going on with pipewire-alsa. There’s some reports on Discord too that I’ll investigate in a few days.

[roderickvd]

If pipewire-alsa, please try #1033.

[dheijl]

It is stock Debian 13, so pipewire-alsa. I don't use Jack, and Pulse-Audio is all but dead I suppose.

[dheijl]

When using #1033 all the device names have changed breaking the existing app configuration, and audio capture no longer works when selecting the new device names...

[roderickvd]

That’s really weird. #1033 shouldn’t change anything in the way of device enumeration.

[dheijl]

The change in device names was already there in the master branch, but audio capture worked when selecting pipewire with the new name, with #1033 it no longer works.

[roderickvd]

OK, probably need to adjust target_avail_min to one period instead of two on capture devices.

[dheijl]

I think I'll just fork cpal 0.16.0 and cherrypick from the commits.

[roderickvd]

As you wish, though if you’d want to try then that’d be helpful in tracking this bug down.

[dheijl]

There have been so many commits lately that it's difficult to know where to start looking...

[roderickvd]

There’s only one occurrence of set_avail_min: that’s the place.