1.2.5 now prefixing devices with "_ucm0001." about alsa-ucm-conf

[craftyguy]

If I remove the include added in 1e6297b, device names go back to what they were <1.2.5:

diff --git a/ucm2/ucm.conf b/ucm2/ucm.conf
index a9bdd0d..157742e 100644
--- a/ucm2/ucm.conf
+++ b/ucm2/ucm.conf
@@ -18,7 +18,7 @@ Define.V2ConfD yes    # empty string to disable
 Define.V2Module yes    # non-empty string to enable module name lookups (obsolete)
 Define.V2Name yes      # non-empty string to enable driver & card name lookups (obsolete)
 
-Include.libgen.File "/lib/generic.conf"  # private alsa-lib configuration
+# Include.libgen.File "/lib/generic.conf"  # private alsa-lib configuration
 
 If.driver {
        Condition {

[perexg]

As you can see, the ucm can have a private configuration for the PCM and control ALSA devices. It means that the global alsa-lib configuration is not used in this case. So yes, it's part of the UCM API now.

The private prefix which can be obtained using _alibpref key (https://github.com/alsa-project/alsa-lib/blob/0e4ba2ea8c0402f12a645032a14693eb9b1278e6/include/use-case.h#L261) may be removed by pulseaudio . Note that the number in the prefix may vary.

[agx]

@perexg so just to confirm: pa should just drop the prefix?

[perexg]

@perexg so just to confirm: pa should just drop the prefix?

Yes, but only for the port name string, if this functionality is required. The unmodified device name must be used for the device open call.

[craftyguy]

this is fixed in pulseaudio 18.0