Dualsense Haptic Feedback broken with UCM profiles

Dualsense Haptic Feedback broken with UCM profiles

[GitHub issues - opened]

alsa-project/alsa-ucm-conf issue #828 was opened from Flippy1801:

The current UCM profiles for the Sony DualSense controller (DualSense-PS5.conf and DualSense-PS5-HiFi.conf) use SplitPCM to expose the Headphone and Speaker profiles. It completely breaks vibration in PC games running through Proton/Wine that support it.

The official Sony SDK and Windows API (WASAPI) translated through Wine require raw, exclusive access to the 4-channel audio interface (Analog Surround 4.0) to send low-level haptic data to the controller's actuators.

Because the current UCM config splits this device, PulseAudio/PipeWire no longer exposes the raw 4-channel interface to Wine. The games cannot find the haptic audio output, and advanced vibration features are completely lost.

Steps to Reproduce:
1. Connect a Dualsense controller via USB.
2. Open pavucontrol. Set the controller profile to Direct DualSense Wireless Controller.
3. Launch a game with native Dualsense support via Steam/Heroic/Lutris.
4. Result: No haptic feedback is sent to the controller.

Workaround:
If users manually delete or rename /usr/share/alsa/ucm2/USB-Audio/Sony/DualSense-PS5.conf and DualSense-PS5-HiFi.conf, PipeWire falls back to exposing the controller as an Analog Surround 4.0 Output.
Once the UCM profiles are disabled, Wine successfully routes the 4-channel haptic signal to the gamepad, and Haptics work perfectly.

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