ReferenceExtensions
mux-data
Options for the Mux Data extension that monitors playback quality
Adds the Mux Data extension to the player. It renders nothing — place it anywhere inside the player, and it follows whatever media the player attaches. See Mux Data for how monitoring works.
Import
Or load it from the CDN:
Anatomy
Options
Any number of metadata-* attributes can label a view without script. metadata and MuxDataSdk are still properties only when you need to pass an object or override attribute values. Set them on the element, typed as the MuxDataExtension class that @videojs/html/extensions/mux-data exports.
Views also report the extension itself as the Mux plugin, so they can be told apart from other Video.js integrations such as videojs-mux.
Player software name
When no player software name is set, views report videojs-<framework>-<engine>, where the framework is html or react and the engine is the one playing the current source:
The framework is always one word, so everything after the second hyphen is the engine. The name updates on the current view when a source change switches engines. Media that doesn’t declare an engine name leaves it out, as in videojs-html. A player software name you set always takes precedence.
The player software version defaults to the Video.js version, and the Mux plugin is reported as @videojs/mux-data at the same version.
Changing MuxDataSdk, beaconCollectionDomain, debug, or disableCookies restarts monitoring, which ends the current view and starts a new one. The rest update the view in place.