search

Shaka Player SDK Integration Document

This guide is for integrating the MediaMelon Player SDK for the javascript based ShakaPlayer.

Step 1: Add the MediaMelonPlayer SDK

Step 2: Register and Initialize the MediaMelon Player SDK

Step 3: Errors and Warnings (Important)

Step 4: Report Additional Metadata Fields

Step 5: Update Asset Information:

hashtag
Step 1: Add the MediaMelonPlayer SDK

CDN URL:

<script type="text/javascript" src="https://sdk.mediamelon.com/SDK_RELEASES/Javascript/shaka/2.1.1/mmsmartstreaming_shakaplayer.min.js"></script>

NPM:

npm i [email protected]

import {SHAKAPlayerMMSSIntgr} from 'mediamelon-js-shaka-sdk'

hashtag
Step 2: Register and Initialize the MediaMelon Player SDK

circle-info

<customer_id> is your MediaMelon-assigned Customer ID. If you do not know your Customer ID, contact MediaMelon at [email protected]arrow-up-right

After the player instance has been created, create a new Plugin object, register, report player Info, and then initialize the plugin as shown below:

<body>
  <video id="video" controls autoplay></video>
  <script>
      const video = document.getElementById('video');
      const player = new shaka.Player(video);

      var contentMetadata = {
        "assetName": "ASSET_NAME",
        "assetId": "ASSET_ID",
        "videoId": "VIDEO_ID",
        "contentType": "CONTENT_TYPE",
        "genre": "GENRE",
        "drmProtection": "DRM_PROTECTION",
        "episodeNumber": "EPISODE_NUMBER",
        "season": "SEASON",
        "seriesTitle": "SERIES_TITLE",
        "customTags": {
          "key1": "VALUE_STRING1",
          "key2": "VALUE_STRING2"
        }
      };

      var mmShakaPlugin = new SHAKAPlayerMMSSIntgr();
      mmShakaPlugin.registerMMSmartStreaming("PLAYER_NAME", "CUSTOMER_ID", "SUBSCRIBER_ID", "DOMAIN_NAME", "SUBSCRIBER_TYPE", "SUBSCRIBER_TAG", <hashSubscriberId>);
      mmShakaPlugin.reportPlayerInfo("PLAYER_BRAND", "PLAYER_MODEL", "PLAYER_VERSION");
      mmShakaPlugin.reportBasePlayerInfo("BASE_PLAYER_NAME", "BASE_PLAYER_VERSION");
            
      mmShakaPlugin.reportSubPropertyId("SUB_PROPERTY_ID");       
      mmShakaPlugin.reportAppInfo("APP_NAME", "APP_VERSION");
      mmShakaPlugin.reportDeviceId("DEVICE_ID");
      
      const streamURL = 'https://bitdash-a.akamaihd.net/content/sintel/hls/playlist.m3u8';
      var isLive = false;
      
      mmShakaPlugin.reportViewSessionId("VIEW_SESSION_ID");
      mmShakaPlugin.initialize(player, video, streamURL, contentMetadata, isLive);

      player.load(streamURL);
  </script>
</body>

hashtag
Step 3: Errors and Warnings (Important):

The SDK provides two ways to report errors: automatic error capture and manual error reporting via API.

⚙️ Default Behavior (Auto Error Capture):

By default, the SDK automatically listens to and captures player errors that occur after the stream has loaded. SDK will classify the errors based on severity.

circle-info

⚠️ Note: Errors that occur before or during stream loading are not captured automatically by the SDK, as they fall outside the player’s event lifecycle. Use the error and warning APIs below to manually report such issues.

🚫 Disabling Auto Error Capture:

If you prefer to handle error reporting manually, you can disable this automatic behavior by calling:

circle-info

⚠️ When disabled, the SDK will not listen for any player-generated errors. You will be responsible for reporting all errors & warnings manually using the APIs described below.

🛠️ Manual Error Reporting APIs:

Use these APIs to custom report errors and warnings to the SDK—especially for errors that occur before or during stream loading, or when auto-capture is disabled.

🔴 Report Fatal Error:

All errors reported via reportError are treated as fatal.

🟠 Report Warning (Non-Fatal):

All warnings reported via reportWarning are treated as non-fatal and will be tracked accordingly.

hashtag
Step 4: Report Additional Metadata Fields:

hashtag
Step 4.1: Experiment Name:

Reports a custom experiment label (e.g., for A/B testing or feature segmentation). This label helps categorize playback sessions under specific experiments for analytics and comparison.

hashtag
Step 4.2: CDN:

Report the name or identifier of the Content Delivery Network (CDN) used for streaming. This helps track performance and quality across different CDNs.

hashtag
Step 4.3: Custom Metadata:

Use this method to report any additional metadata that doesn’t fall under predefined fields. This allows flexibility to send custom business-specific or platform-specific information to the SDK. This is the same as customTags in the contentMetadata object.

hashtag
Step 4.4: Stream Information:

Report key stream attributes that describe the encoding and delivery method.

hashtag
Step 4.5: Player resolution:

Report the width and height of the player window (in pixels). This is useful to understand playback size and user experience across different screen sizes or platforms.

hashtag
Step 4.6: Report Stream Fallback Event

Report fallback event in case the primary manifest URL fails and falls back on the secondary manifest.

hashtag
Step 5: Update Asset Information:

If Asset Information needs to be updated dynamically during the live session without re-initiating the player, then the updateAssetInfo API can be used to update the new AssetInfo

circle-info

Note

  • This API must be called for updating asset info for the live streams only

  • This API must be called after the Player has started the playback of the live stream

  • New Asset Info Object will override the previous values. Hence, set all the fields that are required every time calling this API, including all Custom Tags.

PreviousCustom SDK Integration DocumentNextBitmovin SDK Integration Guide

Last updated