Hello List,
I’ve recently completed work on a Windows ACM driver (audio codec) for a
client and I now need to register some IDs with Microsoft. Specifically, I
need to register 2 new Product IDs and 2 new FormatTag IDs.
I used the Windows Driver Development Kit (DDK) to do the development and in
the template code from which I built my driver, I see the following:
// the manufacturer id (wMid) and product id (wPid) must be filled
// in with your company’s registered identifier’s. for more
// information on these identifier’s and how to get them registered
// contact Microsoft and get the Multimedia Developer Registration Kit:
//
// Microsoft Corporation
// Multimedia Technology Group
// One Microsoft Way
// Redmond, WA 98052-6399
//
// Developer Services Phone: (800) 227-4679 x11771
This seems OK except that I can’t call a US toll-free number from my
European location. Can anyone help me with a number to call and/or email
address?
Also, I need to define 2 new audio file formats - if I use
WAVEFORMATEXTENSIBLE and generate my own GUIDs, how do I let Microsoft know
these data or do I need to care?
Thanks in advance,
Culann.
Hi, Culann.
I’ve always emailed the text portion of the registration forms in the MDRK
to the email alias “mmreg at microsoft dot com”. You could try that. You
don’t need to register product IDs, only manufacturer IDs. The product IDs
are yours to allocate. They used to put all of them into mmreg.h in the
SDK/DDK, but I don’t think that happens anymore.
-Dan
----- Original Message -----
Subject: How to register new Product IDs and/or Audio FormatTag with
Microsoft
From: Culann mac Cabe
> Date: Tue, 05 Apr 2005 10:36:47 +0100
>
> Hello List,
>
> I’ve recently completed work on a Windows ACM driver (audio codec) for a
> client and I now need to register some IDs with Microsoft. Specifically,
> I
> need to register 2 new Product IDs and 2 new FormatTag IDs.
>
> I used the Windows Driver Development Kit (DDK) to do the development and
> in
> the template code from which I built my driver, I see the following:
>
> // the manufacturer id (wMid) and product id (wPid) must be filled
> // in with your company’s registered identifier’s. for more
> // information on these identifier’s and how to get them registered
> // contact Microsoft and get the Multimedia Developer Registration
> Kit:
> //
> // Microsoft Corporation
> // Multimedia Technology Group
> // One Microsoft Way
> // Redmond, WA 98052-6399
> //
> // Developer Services Phone: (800) 227-4679 x11771
>
> This seems OK except that I can’t call a US toll-free number from my
> European location. Can anyone help me with a number to call and/or email
> address?
>
> Also, I need to define 2 new audio file formats - if I use
> WAVEFORMATEXTENSIBLE and generate my own GUIDs, how do I let Microsoft
> know
> these data or do I need to care?
>
> Thanks in advance,
> Culann.
Dan,
Thanks for this. What about defining new audio file FormatTags? The
manufacturer I’m working for already has a FormatTag in mmreg.h of 0x25. We
have modified the basic codec algorithm to create 2 codec variants, which I
need to ID separately. How should I do that? Do I need to retain the
original 0x25 as one of them and generate a new one? Or should I generate 2
new ones altogether using, e.g. GUIDGEN?
Thanks,
Culann
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Daniel E. Germann
Sent: 07 April 2005 13:22
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] How to register new Product IDs and/or Audio FormatTag
with Microsoft
Hi, Culann.
I’ve always emailed the text portion of the registration forms in the MDRK
to the email alias “mmreg at microsoft dot com”. You could try that. You
don’t need to register product IDs, only manufacturer IDs. The product IDs
are yours to allocate. They used to put all of them into mmreg.h in the
SDK/DDK, but I don’t think that happens anymore.
-Dan
----- Original Message -----
Subject: How to register new Product IDs and/or Audio FormatTag with
Microsoft
From: Culann mac Cabe
> Date: Tue, 05 Apr 2005 10:36:47 +0100
>
> Hello List,
>
> I’ve recently completed work on a Windows ACM driver (audio codec) for
> a client and I now need to register some IDs with Microsoft.
> Specifically, I need to register 2 new Product IDs and 2 new FormatTag
> IDs.
>
> I used the Windows Driver Development Kit (DDK) to do the development
> and in the template code from which I built my driver, I see the
> following:
>
> // the manufacturer id (wMid) and product id (wPid) must be filled
> // in with your company’s registered identifier’s. for more
> // information on these identifier’s and how to get them registered
> // contact Microsoft and get the Multimedia Developer Registration
> Kit:
> //
> // Microsoft Corporation
> // Multimedia Technology Group
> // One Microsoft Way
> // Redmond, WA 98052-6399
> //
> // Developer Services Phone: (800) 227-4679 x11771
>
> This seems OK except that I can’t call a US toll-free number from my
> European location. Can anyone help me with a number to call and/or
> email address?
>
> Also, I need to define 2 new audio file formats - if I use
> WAVEFORMATEXTENSIBLE and generate my own GUIDs, how do I let Microsoft
> know these data or do I need to care?
>
> Thanks in advance,
> Culann.
—
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: xxxxx@rocudo.com To unsubscribe
send a blank email to xxxxx@lists.osr.com
Hi, Culann.
I’ve never registered a format tag before, but it seems like there would be
a form you could email to mmreg for that somewhere in the MDRK. Or, just
make one up with all the info in it and sent it along to mmreg.
Or, like you mentioned, you could use GUIDGEN and WAVE_FORMAT_EXTENSIBLE. I
believe that’s the preferred way to handle new multimedia IDs. I know
WAVE_FORMAT_EXTENSIBLE works with the wave audio APIs. I’ve never tried it
with any of the ACM APIs, though.
If your two CODEC variants are different from the original, I would get two
new IDs for them. If one variant is the same as the original, you can just
get one new ID for the new variant. Does that make sense?
-Dan
-----Original Message-----
Subject: RE: How to register new Product IDs and/or Audio FormatTag with
Microsoft
From: Culann mac Cabe
Date: Thu, 07 Apr 2005 16:16:54 +0100
Dan,
Thanks for this. What about defining new audio file FormatTags? The
manufacturer I’m working for already has a FormatTag in mmreg.h of 0x25. We
have modified the basic codec algorithm to create 2 codec variants, which I
need to ID separately. How should I do that? Do I need to retain the
original 0x25 as one of them and generate a new one? Or should I generate 2
new ones altogether using, e.g. GUIDGEN?
Thanks,
Culann
Thanks Dan,
That makes perfect sense and you are the man.
C
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Daniel E. Germann
Sent: 08 April 2005 14:12
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] How to register new Product IDs and/or Audio FormatTag
with Microsoft
Hi, Culann.
I’ve never registered a format tag before, but it seems like there would be
a form you could email to mmreg for that somewhere in the MDRK. Or, just
make one up with all the info in it and sent it along to mmreg.
Or, like you mentioned, you could use GUIDGEN and WAVE_FORMAT_EXTENSIBLE. I
believe that’s the preferred way to handle new multimedia IDs. I know
WAVE_FORMAT_EXTENSIBLE works with the wave audio APIs. I’ve never tried it
with any of the ACM APIs, though.
If your two CODEC variants are different from the original, I would get two
new IDs for them. If one variant is the same as the original, you can just
get one new ID for the new variant. Does that make sense?
-Dan
-----Original Message-----
Subject: RE: How to register new Product IDs and/or Audio FormatTag with
Microsoft
From: Culann mac Cabe
Date: Thu, 07 Apr 2005 16:16:54 +0100
Dan,
Thanks for this. What about defining new audio file FormatTags? The
manufacturer I’m working for already has a FormatTag in mmreg.h of 0x25. We
have modified the basic codec algorithm to create 2 codec variants, which I
need to ID separately. How should I do that? Do I need to retain the
original 0x25 as one of them and generate a new one? Or should I generate 2
new ones altogether using, e.g. GUIDGEN?
Thanks,
Culann
—
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: unknown lmsubst tag argument: ‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com