Media Domain
This domain allows detailed inspection of media elements
Methods
Events
Types
Methods
Events
Media.playerErrorsRaised #
Send a list of any errors that need to be delivered.
parameters
- playerId
-
PlayerId
- errors
-
array[ PlayerError ]
Media.playerEventsAdded #
Send events as a list, allowing them to be batched on the browser for less congestion. If batched, events must ALWAYS be in chronological order.
parameters
- playerId
-
PlayerId
- events
-
array[ PlayerEvent ]
Media.playerMessagesLogged #
Send a list of any messages that need to be delivered.
parameters
- playerId
-
PlayerId
- messages
-
array[ PlayerMessage ]
Media.playerPropertiesChanged #
This can be called multiple times, and can be used to set / override / remove player properties. A null propValue indicates removal.
parameters
- playerId
-
PlayerId
- properties
-
array[ PlayerProperty ]
Types
Media.PlayerError #
Corresponds to kMediaError
Type: object
properties
- errorType
-
string
- code
-
integer
Code is the numeric enum entry for a specific set of error codes, such as PipelineStatusCodes in media/base/pipeline_status.h
- stack
-
array[ PlayerErrorSourceLocation ]
A trace of where this error was caused / where it passed through.
- cause
-
array[ PlayerError ]
Errors potentially have a root cause error, ie, a DecoderError might be caused by an WindowsError
- data
-
object
Extra data attached to an error, such as an HRESULT, Video Codec, etc.
Media.PlayerErrorSourceLocation #
Represents logged source line numbers reported in an error. NOTE: file and line are from chromium c++ implementation code, not js.
Type: object
properties
- file
-
string
- line
-
integer
Media.PlayerEvent #
Corresponds to kMediaEventTriggered
Type: object
properties
- timestamp
-
Timestamp
- value
-
string
Media.PlayerMessage #
Have one type per entry in MediaLogRecord::Type Corresponds to kMessage
Type: object
properties
- level
-
string
Keep in sync with MediaLogMessageLevel We are currently keeping the message level 'error' separate from the PlayerError type because right now they represent different things, this one being a DVLOG(ERROR) style log message that gets printed based on what log level is selected in the UI, and the other is a representation of a media::PipelineStatus object. Soon however we're going to be moving away from using PipelineStatus for errors and introducing a new error type which should hopefully let us integrate the error log level into the PlayerError type.
Allowed Values:error
,warning
,info
,debug
- message
-
string
Media.PlayerProperty #
Corresponds to kMediaPropertyChange
Type: object
properties
- name
-
string
- value
-
string