Bluetooth audio behavior depends on supported profiles and codecs, not merely on the presence of a wireless connection. A profile defines an intended use and the procedures that compatible devices follow to provide it.
How the pieces connect
Classic playback and hands-free communication can use different arrangements, and newer audio capabilities require compatibility across the host, operating system, and accessory. An application beginning microphone capture can alter which path is used. The resulting format or endpoint change reflects the negotiated communication mode rather than a simple on-or-off property of the radio.
An everyday example
A headset used for music can behave differently when a meeting application also activates its microphone. The combination of playback and capture requirements changes the work the wireless link must perform. A product's advertised Bluetooth version alone does not specify every profile, codec, or simultaneous-use arrangement that its operating system will select.
Reading the information in context
Codec compatibility is an intersection of capabilities along the path. A format listed by an accessory may not be used by every host. Consult current manufacturer documentation for the exact combination instead of assuming that a newer version label guarantees all features. This library neither pairs devices nor records nearby radios; it explains the terminology used to describe their connections.
Audio
Note these before you change anything
Useful facts to have to hand while reading about bluetooth audio profiles.
- The default playback and recording devices
- Sample rate and bit depth in the device properties
- Enabled enhancements or spatial sound
- Driver name and version, and whether it is a built-in class driver or a vendor one
Audio: Playback (output); recording runs the other way
- Applicationplays a stream
- Audio enginemixes and resamples
- Audio driverbuilt-in class or vendor
- Codec or DACconverts digital to analogue
- Speakers or headphonesanalogue or USB
