THEOPlayer XCFramework
This guide provides detailed instructions on integrating the MediaMelon Player SDK into a Theo player based iOS Media Player Application
Steps Involved in Integrating the MMTheoPlayerFramework
There are four steps involved in integrating the SmartSight Player SDK
Importing the framework
Providing asset information for the content before starting the player and after creating its instance
Cleaning up the SDK integration session
Disable manifest-fetching by the SDK
1. Import Frameworks
2. Provide asset information
2a) Add the following method to integrate the MediaMelon Player SDK to the class ViewController
<customer_id> is your MediaMelon-assigned Customer ID. If you do not know your Customer ID contact MediaMelon at customer-support@mediamelon.com
Call to setPlayerRegistrationInformation
is mandatory.
2b) Call the method integrateMMSDK after setting up the player
2c) Create and Set the Asset Information
The application may like to set the auxiliary information of the asset so that it can be recorded in Smartsight. This information could be assetId, assetName, videoId (describing the title to which assets belong), custom metadata, etc. Call to addCustomKVP
is optional. However, when a call is made, setting both the custom key and the value is mandatory
2d) Adding Custom parameters.
The app can produce this asset information to the SmartSight Player SDK by utilizing the metadata field of the SourceDescription
used by the Theo player.
3) Cleanup of session
When the view controller used for playback is removed, call the cleanUp method of the SmartSight Player SDK and add the following method in class ViewController
4) Disable Manifest
Disable Manifest Fetch is optional
If your workflow restricts the manifest to be accessible from both the player and the MediaMelon Player SDK simultaneously, then, you can disable the fetch of the manifest via disableManifestsFetch
in method integrateMMSDK()
Last updated