On Fri Dec 5 11:34:58 2025 +0000, Rémi Bernon wrote:
I think this was meant as a temporary solution but the main issue is that we will need to be able to do the same kind of thing on the mmdevapi side, because the ContainerID is used to match the haptics audio device with its controller. I don't think it's implemented in Wine yet but I know @cmcadams was looking into it, and I'm not very up to date to what we'll need or be able to do there. Yes, whatever we come up with will need to be something that uses information accessible from other places, i.e in `winepulse.drv`. I haven't looked too deeply into these patches, but the information acquired through udev here seems to be fine for that use case.
The MacOS case I did not track down, but I _think_ there might be a way to get the underlying USB device from a USB audio device there as well. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/9687#note_124934