Re: [PATCH 1/2] mmdevapi: Add code to enumerate NOTPRESENT devices

[Alexandre Julliard]

Maarten Lankhorst <m.b.lankhorst(a)gmail.com> writes:
> @@ -33,6 +35,13 @@
>
> WINE_DEFAULT_DEBUG_CHANNEL(mmdevapi);
>
> +static const WCHAR software_wine_mmdevapi[] =
> +    { 'S','o','f','t','w','a','r','e','\\','W','i','n','e','\\','m','m','d','e','v','a','p','i',0};

This looks suspicious. Why do you need a Wine-specific config for this?

-- 
Alexandre Julliard
julliard(a)winehq.org

[PATCH 1/2] mmdevapi: Add code to enumerate NOTPRESENT devices

[Maarten Lankhorst]

Hi Alexandre,

Alexandre Julliard schreef:
> Maarten Lankhorst <m.b.lankhorst(a)gmail.com> writes:
> > @@ -33,6 +35,13 @@
> >
> > WINE_DEFAULT_DEBUG_CHANNEL(mmdevapi);
> >
> > +static const WCHAR software_wine_mmdevapi[] =
> > +    { 'S','o','f','t','w','a','r','e','\\','W','i','n','e','\\','m','m','d','e','v','a','p','i',0};
>
> This looks suspicious. Why do you need a Wine-specific config for this
> I need to map a name to a guid. The guid has to be persistent across 
> reboots and across all programs, so I figured this was the easiest way 
> to do it. If it turns out to be necessary, device specific overrides 
> such as channel config could be put there too.

Cheers,
Maarten.ew

[PATCH 1/2] mmdevapi: Add code to enumerate NOTPRESENT devices

[Maarten Lankhorst]

Hi Alexandre,

Alexandre Julliard schreef:
> Maarten Lankhorst <m.b.lankhorst(a)gmail.com> writes:
> > @@ -33,6 +35,13 @@
> >
> > WINE_DEFAULT_DEBUG_CHANNEL(mmdevapi);
> >
> > +static const WCHAR software_wine_mmdevapi[] =
> > +    { 'S','o','f','t','w','a','r','e','\\','W','i','n','e','\\','m','m','d','e','v','a','p','i',0};
>
> This looks suspicious. Why do you need a Wine-specific config for this?

After some more digging I found 
HKLM\Software\Microsoft\Windows\CurrentVersion\MMDevices\Audio\ (Render 
or Capture) \ {GUID} that seems to have subkeys which probably define 
all the windows properties assigned to a device.

The format seems to be:
{GUID},n = VALUE

Since a property key is defined as a GUID with a integer value following 
it, I assume it's just:
PROPERTYKEY = VALUE

Which means that I should probably add the IMMDevice stubs first, then 
implement IPropertyStore, add all property key values from the sdk, then 
use IPropertyStore on device creation to fill in default values.

Cheers,
Maarten.

Cheers,
Maarten.