reply #9, https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/d42bfa56b7c94afa113048529d430c811c8ba651 is required, since the mic will be muted after switch profile, and it is in the upstream 1.0 branch, which the ubuntu noble based on.
reply #10, The developer tries to add the UCM support for pulseaudio to pipewire once in 2023, however, it introduces a lot of side effect and regression, which impacts the 1.0 stable release, therefore, the upstream maintainer revert it. The https://gitlab.freedesktop.org/pipewire/pipewire/-/merge_requests/1800 is the final version being merged after 1.0 is branch out, and being merged into 1.2 and 1.4 branch to complete the UCM support. To noble, the alsa-ucm-conf will keep updating for supporting the new hardware, so that the pipewire needs to enhance its capability to handle the latest ucm config, the philosophy is supporting the usefulness [1]. I agree that the impact is huge and the risk is high, is it possible to leverage phased update to control the impact? We can keeps it zero until it is passed on all machine in the certification pool. [1] https://documentation.ubuntu.com/sru/en/latest/explanation/principles/#maintain- usefulness -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2122556 Title: 3.5mm microphone recognized but can’t be used as audio input To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2122556/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
