I want to know because my driver is receiving a lot of IOCTLs with the node IDs from the SysAudio "Virtual Audio Device" and not the Filter Node IDs. So in order to handle these IOCTLs correctly I want to be able to decode what the correct Filter node IDs are. Pete -----Original Message----- There is no programmatic way of finding the SysaudioNodeId-->FilterNodeId. And I am really curious about why you need to know this?=20 From the filter point of view, all the node properties that it gets are numbered with FilterNodeId.=20 SysaudioNodeId is just a virtualization for the clients (DSOUND, MIXERAPI (wdmaud)).=20 -----Original Message----- From: Peter Stokes [<mailto:pstokes@xxxxxxxxxxxx]=20> Sent: Wednesday, October 30, 2002 3:43 AM To: wdmaudiodev@xxxxxxxxxxxxx Subject: [wdmaudiodev] Virtual Audio Devices I understand from the Windows DDK documentation that SysAudio builds filter graphs from the available KSCATEGORY_AUDIO filter factories into a "Virtual Audio Device", which is registered as a KSCATEGORY_AUDIO_DEVICE. My question is that each individual KSCATEGORY_AUDIO filter factory contains various nodes, each of which has a node ID consisting of a numeric index based from zero. When all the necessary filter factories are linked to produce the "Virtual Audio Device" it is clearly necessary to re-index many of the nodes' IDs because it is not sensible to have multiple nodes with the same ID. I have observed this behaviour using KsStudio. However, I have not been able to deduce the logic used in this re-indexing process. I would also like to know how I can obtain the mappings between the node ID given to a node in the "Virtual Audio Device" and the corresponding nodes' ID in it's own filter factory. I hope that the above makes sense. I would be very grateful for any assistance with this matter. Thanks Pete ****************** 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/> ****************** 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/
