OptionaladaptationConfigures the adaptation logic.
OptionaladvertisingAllows you to define which ads you want to display and when you want to display them. In order to play ads on your website, you need to specify an ad config.
OptionalanalyticsBundled Bitmovin Analytics Configuration used to specify metadata and other related info.
Can also be used to completely disable Analytics by setting this to false
in case the Analytics module is loaded, but Analytics is not desired.
OptionalbufferConfigures various buffer settings.
OptionalcastGoogle Cast configuration.
Use remotecontrol with GoogleCastRemoteControlConfig instead.
OptionaleventsA list of callback functions for events. Events can also be dynamically added and removed through on and off.
Example:
events: {
[PlayerEvent.SourceLoaded]: data => {
console.log('version: ' + player.getVersion() + ', SourceLoaded Event data: ', data);
},
[PlayerEvent.Play]: data => {
// do awesome stuff
},
[PlayerEvent.Error]: data => {
console.error('An error occurred:', data);
}
}
OptionalhlsHLS specific configuration options.
Mandatory. A personal key can be found in the bitmovin portal and should be specified here. Do not forget to enter all your domains (subdomains are included) in your account.
OptionallicensingLicensing configuration.
OptionalliveProvide parameters specific to live streams.
For better flexibility it is also possible to define a LiveConfig at source level.
OptionallocationThis can be used to specify custom paths to bitmovinplayer-core.min.js, and bitmovinplayer-core.min.css instead of having all files in the same folder.
OptionallogsCan be use to fine tune logging of the player.
OptionalnetworkNetwork configuration.
OptionalplaybackPlayback config settings.
OptionalremotecontrolRemote control configuration (e.g. Chromecast)
OptionalstorageAllows configuration of the player's access to the Web Storage API.
OptionalstyleUX/UI config settings.
OptionaltweaksTweaks. Use these values only if you know what you are doing.
OptionaluiUI configuration that is passed to the Bitmovin Player UI if the UI module is loaded. Can also be used to disable the UI in case the UI module is loaded but the UI is not desired.
The entry point to the player configuration is the PlayerConfig interface, which is passed into the constructor of the player. There are several ways to do this:
<source>tag:Example configuration:
Example source: