Jaroslav Kysela

It would be better to contact author of this utility through e-mail. I don't think that he watches this tracker.

`alsactl monitor` = `amixer events` It would probably make sense to send an end-of-output line in stdin mode (like `---END---`) - using a new `amixer` argument. The numid=1 as the...

> Though at least in alsa-utils 1.2.4 it's indocumented (though imho, program help should usually be updated first). Fixed in 68473a41c6fa68f3d8331ef995b25c2c84a0ef92 .

Could you check which `hdmi:X,Y` and `hw:X,Y` devices are probed in PW with alsa-lib 1.2.4 and the recent alsa-lib ? The 'Device or resource busy' errors are probably the culprit,...

``` systemctl --user stop pipewire.socket spa-acp-tool -vvv -c 2 list-ports ``` Replace 2 with the alsa card number (you can obtain it using `aplay -l` for example). Start pipewire again:...

The probe order is reversed: ``` 1.2.7: Managed to open _ucm0001.hw:NVidia,11 Managed to open _ucm0001.hw:NVidia,10 Managed to open _ucm0001.hw:NVidia,9 Managed to open _ucm0001.hw:NVidia,8 Error opening PCM device _ucm0001.hw:NVidia,7: Device or...

Please, show the PA debug output: https://fedoraproject.org/wiki/How_to_debug_PulseAudio_problems

Ok, this hardware consists from four cards: HDA analog - which is not used at all (no codec is connected to the PCI bridge) HDA HDMI USB Front Audio USB...

The TRX40 boards use 2 integrated USB audio chips which leads to this confusion. The USB driver represents this hardware as two ALSA USB cards (Main and Front). Just try...

It's possible to "merge" those two cards into one profile via UCM now. I believe that it may be more understandable for users.