Re: [PATCH v2 0/2] MR5734: mf: Implement audio capture device enumeration in MFEnumDeviceSources().

[Paul Gofman (＠gofman)]

On Mon May 27 20:51:49 2024 +0000, Nikolay Sivov wrote:
> It's unlikely those device strings need to be constructed in client
> library here, I'd expect those id to come from setupapi
> (DEVPKEY_Device_InstanceId?), if they are not present in mmdevice
> property store already. If application really depends on those
> attributes we could add them here as a temporary solution, but if it
> doesn't, I'd rather prefer a fixme. Device symlink is required for video
> sources I think, but for mmdevapi you'd use an endpoint id.
> I didn't find a straightforward way to get it from mmdevapi. No, I don't know that anything (that is, the only app I came through) is using that link (although I think it is possible to create mmdevapi device using that path with, e. g., ActivateAudioInterfaceAsync). I will look a bit more and if no obvious way I will remove this field for now.

-- 
https://gitlab.winehq.org/wine/wine/-/merge_requests/5734#note_71444