HDMI audio state reference
The display-transport, audio endpoint, capability, and stream layers that can meet across an HDMI path.
Audio can travel with display transport
An HDMI connection can carry audio and video as related streams over one display link. The graphics or display path, the audio function, the monitor or receiver capability record, and the host endpoint can each be represented separately. A connector label alone does not describe all of those layers.
Capability records guide representation
Display-side capability data can describe supported audio formats, channels, or related timing and transport properties. The host’s graphics and audio components use those records within their respective contracts. A capability declaration is metadata about what a sink reports, not a guarantee about every application stream.
Endpoint is not the connector
The audio stack can expose a digital audio endpoint associated with a display path. That endpoint is a software object with policy and stream state, while HDMI is a physical and protocol boundary. A monitor, receiver, dock, or adapter can affect which endpoint relationship is represented.
Lifecycle crosses subsystems
Package identity, graphics activation, display detection, audio endpoint publication, and stream negotiation can change at different times. Reading an HDMI audio state requires naming which subsystem owns the observed record.
Reference facts
- Transport
- A display link can carry related video and audio streams
- Capability data
- Sink-reported formats, channels, and transport properties
- Endpoint boundary
- Digital audio endpoint distinct from connector and display object
Questions and answers
Is an HDMI port an audio endpoint?
No. The port is a physical and protocol boundary; the audio stack can expose a separate digital audio endpoint associated with the path.
Does the monitor always provide the audio device?
The represented audio sink can be a monitor, receiver, dock, adapter, or another component in the display path.
Are HDMI audio and graphics drivers one package?
They can have coordinated components, but graphics and audio functions have distinct software contracts and records.