By mixer, I assume you mean the mixer API and not Kmixer (Kmixer doesn't need to know anything about the topology of downstream filters). The mixer API gets the topology of the whole graph through Sysaudio. Sysaudio exposes the audio graph as a few unconnected "virtual" filters. E.g. The "wave" render graph is virtualized as a single filter with all the nodes of all the real filters in the graph. The inter-filter pin-to-pin connections are hidden in this view, which simplifies things for the clients (e.g. Windows APIs). So if the mixer API needs to set a volume control, it does so through a "virtualized" pin handle on the Sysaudio filter. Sysaudio routes the call appropriately. Out of curiosity, what are you trying to accomplish (big-picture-wise)? Thanks. Mitch Rundle Microsoft Corporation This posting confers no rights and contains no guarantees. -----Original Message----- From: Art Edwards [mailto:snowdog0@xxxxxxxxxxxx]=20 Sent: Wednesday, September 25, 2002 10:00 AM To: wdmaudiodev@xxxxxxxxxxxxx Subject: [wdmaudiodev] Re: Enumeration of Nodes on Instantiated Pins Yes, I forgot to mention that I can get the count of pin instances from the=20 filter. Hmmm, as I suspected... So, how does the mixer send property requests to the volume control=20 pin-nodes on a wave out filter ? At 12:43 PM 9/25/2002 , you wrote: >It depends on what you mean by "enumerate". You can infer the count of >pin instances, but you cannot get handles to them (which is what you=20 >need for sending property IOCTLs) unless you instantiated them yourself >(e.g. via KsCreatePin). > >Mitch Rundle >Microsoft Corporation > >This posting confers no rights and contains no guarantees. > >-----Original Message----- >From: Art Edwards [mailto:snowdog0@xxxxxxxxxxxx]=3D20 >Sent: Wednesday, September 25, 2002 5:45 AM >To: wdmaudiodev@xxxxxxxxxxxxx >Subject: [wdmaudiodev] Enumeration of Nodes on Instantiated Pins > > > >Does anyone know if an application can >enumerate pin instances on a filter ? > >If so, did I miss it when I searched the >DDK help and the WDMAudioDev archives ? >Or, is it top-secret ? > >I am trying to send IOCTL_KS_PROPERTY >requests to volume nodes associated with >a pin instance (i.e. so called >pin-nodes) on a filter. I have been >successful sending such requests to >nodes that are global to the filter. >(i.e. so called filter-nodes). > > >Art Edwards > >Art's <http://members.localnet.com/~snowdog0/Resume>resume. >Art's <http://www.soniqboom.net>band (a.k.a. Soniq Boom). > >****************** > >WDMAUDIODEV addresses: >Post message: mailto:wdmaudiodev@xxxxxxxxxxxxx >Subscribe: =3D >mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=3D3Dsubscribe >Unsubscribe:=20 >mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=3D3Dunsubscribe >Moderator: mailto:wdmaudiodev-moderators@xxxxxxxxxxxxx > >URL to WDMAUDIODEV page: >http://www.wdmaudiodev.de/ > >****************** > >WDMAUDIODEV addresses: >Post message: mailto:wdmaudiodev@xxxxxxxxxxxxx >Subscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=3Dsubscribe >Unsubscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=3Dunsubscribe >Moderator: mailto:wdmaudiodev-moderators@xxxxxxxxxxxxx > >URL to WDMAUDIODEV page: >http://www.wdmaudiodev.de/ Art Edwards Art's <http://members.localnet.com/~snowdog0/Resume>resume. Art's <http://www.soniqboom.net>band (a.k.a. Soniq Boom). ****************** WDMAUDIODEV addresses: Post message: mailto:wdmaudiodev@xxxxxxxxxxxxx Subscribe: = mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=3Dsubscribe Unsubscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=3Dunsubscribe Moderator: mailto:wdmaudiodev-moderators@xxxxxxxxxxxxx URL to WDMAUDIODEV page: http://www.wdmaudiodev.de/ ****************** 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.de/