AV Player with Nowtilus SSAI
Integration document for AV Player with Nowtilus SSAI
Step 0: Creating AV Player based media player application
Create a directory for integration by doing the following. Open the terminal, change directory to the home directory, and create a folder sampleintegration
Pull the Sample Application from https://sdk.mediamelon.com/$CustomerID/iOS/AVPlayer_SampleApplication.zip
and unzip it
Step 1: Get the MMGenericFramework Static Framework Library
Download the MMGenericFramework static faremwork
Copy the MMGenericFramework static framework to the AVPlayerWithNowtilusSSAi directory
If you are building for the simulator use the MMGenericFramework.framework in the iphonesimulator-x86 and which building for the device use the MMGenericFramework.framework in the iphoneos-arm64 directory
Step 2: Integrating the MMGeneric Framework with the AV Player Sample Application
There are a few steps involved for integrating the MediaMelon Player SDK using the MediaMelonSmartStreaming Framework:
Add the appropriate MMGenericFramework to the AV Player Sample Application
Add the AVPlayerIntegrationWrapper.swift file from the Wrapper directory
Provide asset information for the content before starting the player and after creating its instance
Cleaning up the SDK Session
Disable manifest fetching by the SDK
Add the MMSSAIAdManagerDelegate callbacks
Initializing SSAIAd Manager
Stop the Ad Manager
All AV Player related code of the sample application can be found in the Swift classViewController.swift
1. Import Frameworks
2. Ad the AVPlayerIntegrationWrapper.swift file
This is the integration layer between the Media Melon Framework and AV Player. This needs to be added to the project. Unless absolutely necessary , this file should not be modified.
3. Provide Asset information
After the instance of the player is create, we should set the asset information and send it to before starting its playback. In ViewController.swift, call function self.configureMMSDKwithURL(
mediaURL: String, vastURL: String, player: AVPlayer)
4. Cleaning up the SDK Session
We need to clean up the SDK session once the playback completes. The SDK internally manages the cleanup for most of the cases. For example - when playback finishes, or some error is notified.
However, in some error cases, like network reachability issues, the error notification is delayed. And before this error notification is available, the user may trigger another session. Therefore, it is advised to clean up the session once the playback finishes.
We recommend cleanup at the following two places.
When the view controller hosting the post roll ad terminates
When the player is restarted
5. Disable manifest fetching by the SDK
If your workflow restricts the manifest to be accessible from both player and the MediaMelon Player SDK simultaneously, then, you can disable the fetch of manifest via disableManifestsFetch()
in method _configureMMSDKwithURL()
Note: Disable Manifest Fetch is Optional
6. Add the MMSSAIManagerDelegate
Add the MMSSAIManagerDelegate the ViewController class in ViewController.swift. This delegate will be used for receiving Ad related events and data. At every Ad event the Delegate will fire the notifyMMSSAIAdEventsWith function. This can be used to display Ad related data, enable or disable Ad skipping etc.
Ad Events Supported
adCueTimelineStart
Fired at the start of an Ad break
adImpression
Fired on Ad Impression
adStarted
Fired on start of Ad Play
adPlaying
Fired every 1s during Ad Playback
adFirstQuartile
Fired when Ad playback reached the 25% mark
adMidPoint
Fired when the Ad playback reaches the 50% mark
adThirdQuartile
Fired when Ad Playback reaches the 75% mark
adCompleted
Fired when Ad Playback reaches 100% mark
adCueTimelineEnd
Fired at the end of an Ad break
adSkipped
Fired when an Ad break is skipped
Sample output
7. Initialize the SSAI Ad Manager
Initialize the SSAI Ad Manager to track the Ads and report Ad related metric. For live stream the last parameter isLive is set to true. There are different ways in which the Ad manager can be initialized
Mode 1: Poll for Vast and Manifest Mode ( Default mode )
Mode 2: Read the Manifest data from player API and retreive the Vast file from X-AD-VAST tag in the #EXT-X-DATERANGE metadata in the manifest file
To enable this mode there are a a few steps required
STEP 1: Enable Meta Data Collector
STEP 2: Sync player time with Manifest based time
STEP 3 Initialise the AD Manager
8. Stop the SSAI Ad Manager
To stop the SSAI Ad Manager call the following API
Step 3: Adding multiple static frameworks including the MMGeneric (Static) Framework
List of AvPlayerIntegrationWrapper methods for SSAI
initialiseSSAIAdManager
Initializes the Nowtilus SSAI Ad Manager
setMetaDataCollector
Configiures the Meta Data collector and then returns meta data valuessyn
syncEpochTime
Syncs the player time with the time provided in the Manifest URL
stopSSAIManager
Stops the running instance of the SSAI Ad Manager
getAdPlaybackTime
Gets the playback time of the current ad playing ( Called during an Ad Break)
getAdDuration
Gets duration of the current Ad ( Called during an Ad Break)
getAdId
Gets the Ad Id value( Called during an Ad Break)
getAdTitle
Gets the Ad Title ( Called during an Ad Break)
getAdIndex
Returns in Index of the current ad playing in an Ad break. ( Called during an Ad Break)
getAdTotalAdsInPod
Gets the toal number of Ads inside an Ad Pod( Called during an Ad Break)
getAdServer
Gets the Ad Server Name ( Called during an Ad Break)
getAdDuration
Gets the duration of the events( Called during an Ad Break)
getAdPosition
Gets the position of the Ads . For live Ads this will return "MID"
Last updated