Nodes and Connections

The filter provides a description of its topology nodes in the form of an array of node descriptors (PCNODE_DESCRIPTOR structures). Each descriptor in the array describes a single node and contains a GUID that specifies the node type (for example, KSNODETYPE_REVERB). For a list of the standard node types that are defined for audio devices, see Audio Topology Nodes.

The filter identifies each of its nodes by the node's index in the descriptor array. For example, when sending a node-specific property request to a filter or to a particular pin on a filter, a client includes the node ID (the array index) in the request in order to identify the target node.

The filter provides a description of its internal connections in the form of an array of connection descriptors (PCCONNECTION_DESCRIPTOR structures). Each descriptor describes one of the filter's internal connections. A descriptor can either describe a connection between a pin and a node or a connection between two nodes.

The nodes and connections that the filter exposes together define the filter's internal topology. The topology is a map of the audio device's internal layout and should accurately reflect the organization of the hardware that it represents. The Microsoft Windows Multimedia mixer API, for example, translates the filter's internal connections into mixer lines and its nodes into controls on the mixer lines (see Kernel Streaming Topology to Audio Mixer API Translation). Any inaccuracies in the filter's internal topology are reflected in the mixer-line representation and may cause errors or unexpected behavior in an application that uses the mixer API.

Send comments about this topic to Microsoft