[wdmaudiodev] Re: Mixer API under Vista build 5308
- From: "Frank Yerrace" <Frank.Yerrace@xxxxxxxxxxxxx>
- To: <wdmaudiodev@xxxxxxxxxxxxx>
- Date: Wed, 5 Apr 2006 14:00:09 -0700
Yes, we do have some new information. One of us will respond shortly-
within a day or two. Thanks for your patience.
This posting is provided "AS IS" with no warranties, and confers no
rights.
-----Original Message-----
From: wdmaudiodev-bounce@xxxxxxxxxxxxx
[mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of Jeff Pages
Sent: Wednesday, April 05, 2006 1:30 PM
To: wdmaudiodev@xxxxxxxxxxxxx
Subject: [wdmaudiodev] Re: Mixer API under Vista build 5308
Hi Frank,
Any update on this issue?
Jeff
----- Original Message -----
From: "Frank Yerrace" <Frank.Yerrace@xxxxxxxxxxxxx>
To: <wdmaudiodev@xxxxxxxxxxxxx>
Sent: Sunday, March 12, 2006 5:13 AM
Subject: [wdmaudiodev] Re: Mixer API under Vista build 5308
> We very much appreciate that this community is taking a good look at
> Vista and giving specific feedback like this. Thank you.
>
> Please give us a couple weeks to study this issue here to see if we
can
> offer some alternatives for certain classes of applications like this.
> If you hear nothing more within that timeframe, please raise the issue
> again.
>
> Frank Yerrace
> Technical Lead
> Microsoft Corporation
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
>
> -----Original Message-----
> From: wdmaudiodev-bounce@xxxxxxxxxxxxx
> [mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of stephen turner
> Sent: Saturday, March 11, 2006 9:26 AM
> To: wdmaudiodev@xxxxxxxxxxxxx
> Subject: [wdmaudiodev] Re: Mixer API under Vista build 5308
>
> I agree with Jeff and Dan -It looks like this is going to be a huge
> problem for professional applications that still use the mixer API and
> expect full control over the h/w. Is there a way that the audio
> subsystem can be put in a "legacy" mode to make it act like 2000/XP?
> -steve
> ----------------------
> Stephen Turner
> AudioScience, Inc.
>
>
> -------- Original Message --------
>> From: "Daniel E. Germann" <deg@xxxxxxxx>
>> Sent: Saturday, March 11, 2006 7:13 AM
>> To: wdmaudiodev@xxxxxxxxxxxxx
>> Subject: [wdmaudiodev] Re: Mixer API under Vista build 5308
>>
>> We have customers that will have the same problem. Some are
> broadcast, like
>> Jeff's, and others use our products for test and measurement
> applications.
>> Both sets of customers have existing software that expects to access
> the
>> hardware through the mixer APIs. In fact, access to the main audio
> fader is
>> mandatory for the test and measurement app, so they can ensure their
> test
>> stimulus signal is not attenuated. Otherwise, it will look to their
>> software like the response signal has a drop in level.
>>
>> Is there a white paper that talks about these changes that we could
> pass on
>> to our customers, so they have a "heads up"? Most of the public info
> I've
>> seen so far is in the HD Audio or driver realm.
>>
>> Thanks,
>> -Dan
>> --
>> Dan Germann
>> Digital Audio Labs
>>
>>
>> ----- Original Message -----
>> > From: "Jeff Pages" <barefeet@xxxxxxxxxxxxxx>
>> > To: <wdmaudiodev@xxxxxxxxxxxxx>
>> > Sent: Saturday, March 11, 2006 8:31 AM
>> > Subject: [wdmaudiodev] Re: Mixer API under Vista build 5308
>> >
>> >
>> > Thanks Frank. The controls are showing up correctly and are
> functional
>> > under Device Properties as you described.
>> >
>> > My main concern is that our products are targeted at the
> professional
>> > audio market, and many of our customers will be using our cards
with
>> > broadcast automation and mixing desk software that expects to find
> these
>> > controls through the mixer API, and the loss of this functionality
> will
>> > seriously impact on our business.
>> >
>> > Jeff
>>
>> ******************
>>
>> 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/
******************
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:
