[wdmaudiodev] Re: WaveCyclic input ports show up as "currently unavailable" under Vista RC2
- To: <wdmaudiodev@xxxxxxxxxxxxx>
- Date: Mon, 13 Nov 2006 09:02:11 -0500
Well, I will summarize what I have found:
a) On one PC (the one which I mentioned previously in this thread), all record
sources are marked as "currently unavailable". However, I am able to select
any record source, and, once I do, it is immediately marked as "working".
Closing the reopening the CPL has no effect- all non-selected sources are still
marked as "currently unavailable".
b) On a second PC, I cannot select any record source. All are marked as
"currently unavailable".
c) On said second PC, I cannot select my headphones endpoint, even though it is
marked as working. Why would that be?
d) Is it normal that my AC3 endpoint be shown in the CPL as "working", but that
I am unable to select it?
thanks for any help,
Philip Lukidis
> -----Original Message-----
> From: wdmaudiodev-bounce@xxxxxxxxxxxxx
> [mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx]On Behalf Of Mitchell Rundle
> Sent: Friday, November 10, 2006 5:04 PM
> To: wdmaudiodev@xxxxxxxxxxxxx
> Subject: [wdmaudiodev] Re: WaveCyclic input ports show up as
> "currently
> unavailable" under Vista RC2
>
>
> Once you get a capture endpoint in the "working" state, if
> you close the CPL, then reopen it, do you still have that
> endpoint "working" or are you back to all "unavailable"?
>
> Regards,
> Mitch
>
> -----Original Message-----
> From: wdmaudiodev-bounce@xxxxxxxxxxxxx
> [mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx]
> Sent: Friday, November 10, 2006 6:19 AM
> To: wdmaudiodev@xxxxxxxxxxxxx
> Subject: [wdmaudiodev] Re: WaveCyclic input ports show up as
> "currently unavailable" under Vista RC2
>
> Hello Mitch,
>
> I have the same issue with all my record sources marked as
> "currently unavailable" (and I don't have any peak meters in
> my topology). Concerning the observations already made and
> your reply, in my case KSPROPERTY_PIN_GLOBALCINSTANCES is 0
> when the audio cpl is closed. The count changes to 1 when
> the audio cpl is open, which I assume is normal (if not, what
> could cause this). In addition, I never fail a newstream
> call while interacting with the CPL record sources. All (or
> most) of my record sources are marked as unavailable.
> However, I can select a source, and thereafter it is marked
> as "working". Recording from the selected source works.
> However I'm sure that our users will be worried when they see
> a "currently unavailable" text for our record sources.
>
> Are there any other cases whereby a record source could be
> marked as "currently unavailable"? I myself am using a
> WaveCyclic based audio driver as well. I did not try using a
> sum node, because I would prefer, if possible, to keep OS
> based topology differences to a minimum (and I may be doing
> something else wrong). Do you have any idea what may be the issue?
>
> thanks,
>
> Philip Lukidis
>
> > -----Original Message-----
> > From: wdmaudiodev-bounce@xxxxxxxxxxxxx
> > [mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx]On Behalf Of
> Mitchell Rundle
> > Sent: Wednesday, November 08, 2006 12:29 PM
> > To: WDMAUDIODEV
> > Subject: [wdmaudiodev] Re: WaveCyclic input ports show up as
> > "currently
> > unavailable" under Vista RC2
> >
> >
> > 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/
> >
> > ******************
> >
> > 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:
