Custom Player C++ SDK
Comprehensive Integration Guide for the C++-based MediaMelon Custom Player SDK
Step 2: Register and Initialise the MediaMelon Player SDK
Step 3: Report Custom, Network & Presentation Information
Step 4: Report Player State & Actions
Step 5: Report Advertisement Analytics
Step 1: MediaMelon SDK Files
Add and import the required MediaMelon SDK header files provided in the release notes
Step 2: Register and Initialise the MediaMelon Player SDK
<customer_id> as your MediaMelon-assigned Customer ID. If you do not know your Customer ID contact MediaMelon at support@mediamelon.com
Register the MediaMelon SDK and report the player information and device information as shown below:
Step 3: Report Custom, Network & Presentation Information
This information should be reported before the video starts playing.
Custom Metadata:
Reports custom metadata, in the form of a key-value pair, to analytics.
Network Type:
Reports the communication network type to analytics.
Enum values and their description for the MMConnectionInfo
are as below;
Presentation Information:
Reports the available representations of the video that the player can present.
Step 4: Report Player State & Actions
Playback Initiation:
Reports that user initiated the playback session. This should be called at different instants depending on the mode of operation of player. In Auto Play Mode, should be the called when payer is fed with the manifest URL for playback In non-Auto Play Mode, should be called when the user presses the play button on the player.
Player State:
Reports the current player state to analytics.
Enum values and their description for the MMPlayerState
are as below;
Note: When the player enters the STOPPED state the current video session is terminated. Re-entering the PLAYING state will result in a new session being logged for the video. The most common reason for this occurring is when a video plays to the end and then the user seeks back to a point earlier in the video.
Playback Position:
Reports current playback position in media to analytics. This should be reported every two seconds if possible. Reported playback position should be in milliseconds.
Seek Complete:
Reports that a seek event is complete, with the new playback starting position in milliseconds. This is the point from which playback will start after the seek.
Buffering:
Reports the start and completion of the buffering.
Error:
Reports an error encountered during the playback. Playback position should be in milliseconds.
Chunk Request:
Reports the encoded chunk bitrate when the current playing chunk bitrate is different from the previous chunk bitrate.
Download Rate:
Reports current download rate (rate at which chunk is downloaded) to analytics. This should be reported for every chunk download (if possible). If this value is not available on every chunk download, then last updated value with player should be reported every 2 seconds. Reported download rate should be in bits per second.
Frame Loss:
Reports cumulative frame loss count to analytics. This is Cumulative count of frames lost in playback session.
Step 5: Report Advertisement Analytics
Ad Info:
Reports advertisement-related information before or at the time of ad start.
MMAdInfo
properties and their respective data types are mentioned below:
Ad State:
Reports advertisement playback state.
Enum values and their description for the MMAdState
are as below;
Ad Playback Time:
Reports current advertisement playback position. This should be reported every two seconds if possible. Reported playback position should be in milliseconds.
Ad Error:
Reports error encountered during the advertisement playback. Playback position should be in milliseconds.
Ad Buffering:
Reports the start and completion of the advertisement buffering.
Last updated