The value is a GUID, which is the data type for a container ID.Īn audio driver supports KSPROPERTY_JACK_CONTAINERID, if and only if, it can reliably obtain the correct container ID through some other means For example, from a Bluetooth enumerator. The new property is KSPROPERTY_JACK_CONTAINERID and it's been added to the existing KSPROPSETID_Jack property set. In this case, your audio driver can support a new container ID property for endpoints. But regardless, you can develop your audio driver to provide support for such a scenario.

This scenario involving a Bluetooth I2S design that uses its own Bluetooth enumerator is rare. In certain cases, the logic used by the endpoint builder is not sufficient to handle Bluetooth I2S designs where the container ID of an audio endpoint exposed by the audio driver is determined by another enumerator - the Bluetooth enumerator. The audio endpoint builder uses an enumeration algorithm to determine the container IDs of audio endpoints, and then stores these IDs as properties in the MMDEVAPI endpoint property store.

The Audio Endpoint Container ID topic discusses the reliable methods available for obtaining the container ID of an audio endpoint associated with a Bluetooth audio device.