[wdmaudiodev] Re: WaveCyclic input ports show up as "currently unavailable" under Vista RC2

  • From: Stephan Kappertz <stephan@xxxxxxxxxx>
  • To: wdmaudiodev@xxxxxxxxxxxxx
  • Date: Wed, 08 Nov 2006 19:08:23 +0100

I checked the driver with KSStudio and KSPROPERTY_PIN_GLOBALCINSTANCES CurrentCount is 0 and PossibleCount is 1 for the recording pin.


NewStream gets called and succeeds. After that, SetNotificationFreq is called and immediately afterwards the stream gets destroyed!?!

Any idea what else might cause the unavailable state?

And what could cause the different behavior when replacing the MUX by a SUM node?

Thanks,
Stephan


Mitchell Rundle wrote:
Yes, MUXes are definitely supported in Vista.  When the endpoints are 
"unavailable" it indicates that either:
1) the CurrentCount of KSPROPERTY_PIN_GLOBALCINSTANCES on the host pin factory 
is non-zero, or
2) the system was unable to instantiate the host pin

To see if (1) is the problem, run ksstudio and look at the values under "Instance 
Data" for the host pin factory.
To see if (2) is the problem, put a breakpoint in your drivers NewStream 
implementation and see if it gets hit.

Regards,
Mitch Rundle
Microsoft

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 Stephan Kappertz
Sent: Wednesday, November 08, 2006 9:02 AM
To: WDMAUDIODEV
Subject: [wdmaudiodev] WaveCyclic input ports show up as "currently 
unavailable" under Vista RC2

Hi All,

we have a WaveCyclic driver that uses a node of type KSNODETYPE_MUX in
its topology to express the fact that the user can select one of three
possible input sources for the ADC (but not more than one). Under XP
this topology causes sndvol32 to show all input sources with selector
check boxes. That's what we want.

Now when running the same driver under Vista RC2, all three inputs show
up as "Currently unavailable". It is not possible to select an input and
apps don't see any input source.

The KSPROPERTY_MUX_SOURCES property is queried by Vista with
KSPROPERTY_TYPE_GET and the driver returns the default active source
with STATUS_SUCCESS. Vista never calls the property handler with
KSPROPERTY_TYPE_SET.

When changing the mux node to KSNODETYPE_SUM, all three inputs show up
as available and each one is selectable in any audio application.

Now the question is: is KSNODETYPE_MUX supposed to work under Vista? And
if not, how are we supposed to replace it for a device that has this
hardware design?

Thanks,
Stephan
******************

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: