[wdmaudiodev] Re: Problems with wrapping the Microsoft APO (was Multiple APOs in Vista?)
- From: Hakon Strande <hakons@xxxxxxxxxxxxxxxxxxxxx>
- To: <wdmaudiodev@xxxxxxxxxxxxx>
- Date: Mon, 30 Apr 2007 15:22:26 -0700
That requirement was made into a recommendation.
The latest WLP documents should reflect this.
Sincerely,
Hakon Strande | Windows Sound Team PM | (p) 425.705.0637
-----Original Message-----
From: wdmaudiodev-bounce@xxxxxxxxxxxxx
[mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of Jeff Claar
Sent: Monday, April 30, 2007 1:18 PM
To: wdmaudiodev@xxxxxxxxxxxxx
Subject: [wdmaudiodev] Re: Problems with wrapping the Microsoft APO (was
Multiple APOs in Vista?)
Hi Hakon,
Below is a post you made several months ago regarding the requirement of
the reuse of MS system effects in Vista for APOs. In it, you state that
the requirements for reuse go into effect in June 2007. Is that still
the schedule?
Also, is this a requirement for all systems and devices? For example, is
a set of 3rd-party USB speakers required to implement the MS effects, or
is it limited only to Vista Premium systems? If not all devices need to
implement the effects, is there a document somewhere that details which
devices do and do not?
Thanks,
Jeff
-----Original Message-----
From: wdmaudiodev-bounce@xxxxxxxxxxxxx
[mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of Hakon Strande
Sent: Thursday, October 05, 2006 10:05 AM
To: wdmaudiodev@xxxxxxxxxxxxx
Subject: [wdmaudiodev] Re: Problems with wrapping the Microsoft APO (was
Multiple APOs in Vista?)
Michael,
Excellent questions that we can only comment on after talking with the
team that owns the Vista Home Theater effects. Some of those team
members are on this mailing list but some are not and the key program
manager is on vacation currently.
I wanted you to know that we will get back to you on the problem you are
pointing out with regards to future mandatory re-use of these effects
for Logo and the difficulties for IHVs in doing so.
At this time it is not required until systems/devices shipping after
June 2007 with grandfathering in effect for submissions made prior to
June 2007.
Sincerely,
Hakon Strande
PM Integrated, Internal, External, and Wireless Audio Devices
MediaTech/DMD/Windows Client/Microsoft
-----Original Message-----
From: wdmaudiodev-bounce@xxxxxxxxxxxxx
[mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of Michael R.
Preston
Sent: Thursday, October 05, 2006 9:51 AM
To: wdmaudiodev@xxxxxxxxxxxxx
Subject: [wdmaudiodev] Re: Problems with wrapping the Microsoft APO (was
Multiple APOs in Vista?)
Hakon,
Thanks for the official response. I don't have a problem with IHVs
having to do their own GUI for their own effects using their own
property store GUIDs. What I do have a problem with is two things:
1. Not being able to reuse the Room Correction wizard without having to
reuse the whole Microsoft APO property page GUI.
2. Not being able to replace the Microsoft speaker configuration GUI
with the IHVs custom Bass Management/Speaker Phantoming GUI.
Is either of these possible? The other features provided by the
Microsoft APO have much simpler GUIs - sometimes just a simple on/off
switch. Those should be quite easy to replicate in the IHVs GUI.
However, the Room Correction wizard is quite complicated, as it is a
complicated feature. Forcing IHVs to either use the entirety of the
Microsoft APO/GUI package or replace all the functionality with their
own (including Room Correction) is really putting the IHVs in a bad
position. It makes their decisions on doing their own custom effects
much more complicated.
In light of all this, does this mean that Microsoft is going to relax
its requirement about having IHVs replace all the built-in
functionality? If the audio infrastructure in Vista has been
defeatured, it makes sense for the IHV requirements to reflect this.
Mike
wdmaudiodev-bounce@xxxxxxxxxxxxx wrote:
> You guys are pointing at one area where your disappointment truly
echoes
> our own. The lack of UI extensibility is regrettably true, one of the
> victims of feature cut-back. The documentation will be corrected to
> reflect reality better.
>
> While we sure had larger plans for this part of the audio
infrastructure
> in Vista we got only half-way there this time around. Bottom line is
> that if you want your own UI for your own FXs you have to create it
and
> map it to your own property store.
>
> Sincerely,
>
> Hakon Strande
> PM Integrated, Internal, External, and Wireless Audio Devices
> MediaTech/DMD/Windows Client/Microsoft
>
> -----Original Message-----
> From: wdmaudiodev-bounce@xxxxxxxxxxxxx
> [mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of Jeff Claar
> Sent: Wednesday, October 04, 2006 3:51 PM
> To: wdmaudiodev@xxxxxxxxxxxxx
> Subject: [wdmaudiodev] Re: Problems with wrapping the Microsoft APO
(was
> Multiple APOs in Vista?)
>
> Thanks for the updates. In a separate email thread I got some
> clarification from Hakon Strande.
>
> He said that multiple APOs per device should be allowed. However,
there
> can only be one LFX and one GFX APO per endpoint.
>
> This is in conflict with what's on page 10 of the same document, where
> it describes how to install multiple APOs on the same endpoint. (Using
> FX\0, FX\1, FX\2, etc.) Hakon said that this was never the intention,
> and will not be supported.
>
> I also agree about the frustrations with the Enhancements page. This
is
> true if you add features as well -- there seems to be no way to add
any
> additional features without writing a separate app. But if you do
that,
> you can only get read-only access to the endpoint property store, and
> there is no way to get a pointer to the FX store.
>
> Jeff
>
> -----Original Message-----
> From: wdmaudiodev-bounce@xxxxxxxxxxxxx
> [mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of Michael R.
> Preston
> Sent: Wednesday, October 04, 2006 2:56 PM
> To: wdmaudiodev@xxxxxxxxxxxxx
> Subject: [wdmaudiodev] Re: Problems with wrapping the Microsoft APO
(was
> Multiple APOs in Vista?)
>
> No, that's not correct. The LFX, GFX, and GUI are all registered
under
> the same FX subkey, but with different property IDs (a property ID is
a
> combination of a GUID and an integer index value). It's not clear
from
> the SysFX document what purpose multiple APOs for the same endpoint
> would be. Elsewhere in the same document (on page 4) the following is
> stated:
>
> "Each Plug and Play hardware ID can be associated with only one GFX
and
> one LFX sAPO."
>
> I don't think this is referring to multiple endpoints within the same
> Hardware ID, since each of them would get installed as "FX\0" for each
> endpoint. Sounds like we need some clarification here...
>
> Mike
>
> Tim Roberts wrote:
>
>>Michael R. Preston wrote:
>>
>>
>>
>>> The more I've looked into wrapping the Microsoft APO, the more
>>>difficult I find it. Sure, Microsoft gives you examples on how to do
>>>it, but the manner in which it's supported is extremely limiting for
>>>the IHVs. I'm not sure about the multiple FX key issue from the APO
>>>standpoint, ...
>>
>>
>>
>>My interpretation of the "multiple FX key" thing in the document is
>
> that
>
>>you can have one subkey for the LFX, one subkey for the GFX, and one
>>subkey for the configuration UI.
>>
>
>
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| Mike Preston | Home/Office: (360)756-1655 |
| E-mail: mike@xxxxxxxxxxxxxxxxxxx | Cell: (360)303-9331 |
|~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
| The man who follows the crowd will usually get no |
| further than the crowd. The man who walks alone is |
| likely to find himself in places no one has ever been. |
| -- Alan Ashley-Pitt |
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
******************
WDMAUDIODEV addresses:
Post message: mailto:wdmaudiodev@xxxxxxxxxxxxx
Subscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=subscribe
Unsubscribe:
mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=unsubscribe
Moderator: mailto:wdmaudiodev-moderators@xxxxxxxxxxxxx
URL to WDMAUDIODEV page:
http://www.wdmaudiodev.com/
******************
WDMAUDIODEV addresses:
Post message: mailto:wdmaudiodev@xxxxxxxxxxxxx
Subscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=subscribe
Unsubscribe:
mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=unsubscribe
Moderator: mailto:wdmaudiodev-moderators@xxxxxxxxxxxxx
URL to WDMAUDIODEV page:
http://www.wdmaudiodev.com/
******************
WDMAUDIODEV addresses:
Post message: mailto:wdmaudiodev@xxxxxxxxxxxxx
Subscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=subscribe
Unsubscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=unsubscribe
Moderator: mailto:wdmaudiodev-moderators@xxxxxxxxxxxxx
URL to WDMAUDIODEV page:
http://www.wdmaudiodev.com/
******************
WDMAUDIODEV addresses:
Post message: mailto:wdmaudiodev@xxxxxxxxxxxxx
Subscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=subscribe
Unsubscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=unsubscribe
Moderator: mailto:wdmaudiodev-moderators@xxxxxxxxxxxxx
URL to WDMAUDIODEV page:
http://www.wdmaudiodev.com/
Other related posts:
