Anyways if you're using a Dualsense controller and games are routing haptics to the speaker instead of the haptic motors, you can drop the following into ~/.config/wireplumber/wireplumber.conf.d/60-dualsense.conf:monitor.alsa.rules = [

[iczero@mice.tel]

Anyways if you're using a Dualsense controller and games are routing haptics to the speaker instead of the haptic motors, you can drop the following into ~/.config/wireplumber/wireplumber.conf.d/60-dualsense.conf:

monitor.alsa.rules = [
  {
    matches = [
      {
        node.name = "alsa_output.usb-Sony_Interactive_Entertainment_Wireless_Controller-00.pro-output-0"
      }
    ]
    actions = {
      update-props = {
        audio.position = ["FL", "FR", "RL", "RR"]
      }
    }
  }
]

Then set the Dualsense audio sink to use the "Pro Audio" profile in the KDE audio devices controller (or something else). systemctl --user restart wireplumber and you should have haptics working. The default profile for the Dualsense does some funny things and generally doesn't work, not sure where it lives or how to fix it.

RE: https://mice.tel/notes/an1cg9loaeyf00ag

[iczero@mice.tel]

First two channels correspond to standard stereo audio (FL and FR). "Default" mapping creates an "Internal Mono Speaker" virtual sink which is the only sink exposed to applications, which maps to the second channel (FR). This is only accurate when no headphones are connected to the headphone port on the controller; both FL and FR are routed as stereo to the headphones when they are connected. RL and RR always correspond to the left and right HD haptic motors, respectively. (You can play music on it for fun, they sound like subwoofers.) However, since the mono sink is the only sink exposed to applications, games that expect to send 4-channel {audio + haptic} data to the controller end up getting downmixed and behaving incredibly weirdly. Even the Pro Audio profile assumes the output device is 2 channels and as such invokes downmixing anyways unless the stream.dont-remix = true property is set on the node. Unfortunately patchbays like Helvum additionally only show the game as outputting two-channel audio because downmixing is automatic and happens before port assignment; this leads to further confusion.