alsa-project/alsa-ucm-conf issue #104 was opened from craftyguy:

I'm using a ucm2 config that is not yet upstream (see [1]), and 1e6297b650114cb2e043be4c677118f971e31eb7 has caused devices to get renamed; they are now prefixed with `_ucm0001.`:

alsaucm json output from 1.2.4:

``` ... "Verbs": { "HiFi": { "Comment": "Default", "Devices": { "Handset": { "Comment": "Handset", "ConflictingDevices": [ "Speaker", "Headphones" ], "Values": { "CaptureCTL": "hw:L5", "PlaybackCTL": "hw:L5", "PlaybackChannels": "2", "PlaybackPCM": "hw:L5,0", "PlaybackPriority": "100", "PlaybackSwitch": "name='Speaker Switch'", "PlaybackVolume": "name='Speaker Volume'" } }, ... ```

alsaucm json output from 1.2.5:

``` ... "Verbs": { "HiFi": { "Comment": "Default", "Devices": { "Handset": { "Comment": "Handset", "ConflictingDevices": [ "Speaker", "Headphones" ], "Values": { "CaptureCTL": "_ucm0001.hw:L5", "PlaybackCTL": "_ucm0001.hw:L5", "PlaybackChannels": "2", "PlaybackPCM": "_ucm0001.hw:L5,0", "PlaybackPriority": "100", "PlaybackSwitch": "name='Speaker Switch'", "PlaybackVolume": "name='Speaker Volume'" } }, ... ```

This breaks things [like pulseaudio config](https://source.puri.sm/Librem5/librem5-base/-/blob/pureos/byzantium/default/...) that expects specific device names. Was this renaming intentional?

cc @agx

1. https://source.puri.sm/Librem5/librem5-base/-/tree/pureos/byzantium/default/...

Issue URL : https://github.com/alsa-project/alsa-ucm-conf/issues/104 Repository URL: https://github.com/alsa-project/alsa-ucm-conf