Jaroslav Kysela

Which hardware are you using?

There is no forced rate or resamling specificed in the configuration file for this hw - https://github.com/alsa-project/alsa-ucm-conf/blob/master/ucm2/USB-Audio/Realtek/ALC4080-HiFi.conf . We had some issues in the USB driver (rate lock when the...

I see 44100Hz in both outputs. You can filter the output only for the problematic card - use `aplay -l` to list cards and devices eventually `cat /proc/asound/cards` will work.

It's weird, but it looks like an issue somewhere else (maybe the USB card does some hidden resampling?). The alsa-lib/ucm does not hardcode the rate for this device. The procfs...

If the 44100Hz is in procfs then the user space already sets to this rate and the driver should issue the USB rate command to the hardware with this settings....

@geoffreybennett This bug is for ALC4080. For configurations using split macros, the default rate is hardcoded to 48kHz in the alsa-lib direct plugins. It would be better to create a...

I don't think that it's the right way to update this configuration. I assume that @plbossart and @mchehab tested the previous configs. It would be probably good to gather output...

Also, do not forget that there are probably multiple hardware variants which are sharing the similar configuration file, so removing devices and/or modifying the configuration unconditionally without asking the original...

As I already wrote, I would like probably to see the step-by-step configuration changes e.g. what are minimal configuration changes to make Speaker device work on your hardware?

You can test the UCM profile using two tools: 1) `alsaucm -c hw:0 dump text` where 0 is the card number to test the UCM syntax errors and values passed...