The player configuration is the main data object of the SDK; this object is used for configuring all plugins and for creating and obtaining the media provider media entries that will play on the device.

Media Entry - PKMediaEntry

The PKMediaEntry contains information regarding the media that will be played. With this information, the Kaltura Mobile Video Player
prepares the source that will play the media, decides which type of player is required to play the media, and more.

Methods for Creating the PKMediaEntry

The PKMediaEntry can be created using one of the following methods:

  1. Manually - Instantiate a new PKMediaEntry instance and fill the fields.


Basic Setup without provider

  1. Using a MockMediaProvider - Create a PKMediaEntry from a JSON input file or JsonObject.

  2. Using a remote media provider - Use one of the provided MediaEntryProvider implementations:

    For OVP environments, use “KalturaOvpMediaProvider”.


OVP media provider

For OTT environments, use "PhoenixMediaProvider".


Phoenix media provider

To use this method, you'll need to do the following:

a) Create an instance of one of the above mentioned providers.

b) Set the mandatory parameters needed for fetching data, such as media id, SessionProvider, etc.

c) Once your provider object is ready, activate its “load” method and pass a completion callback. If successful, the PKMediaEntry object will be provided in the response.

Once you have a PKMediaEntry ready, you can build the player configuration and plugins, and continue to prepare the Kaltura Mobile Video Player for play.

About the PKMediaEntry


  • Building the PKMediaEntry manually is more relevant for customers which do not use Kaltura BE to store their content.

  • Once content is stored in Kaltura’s BE you can use our Media Providers to fetch the PKMediaEntry

The PKMediaEntry holds information gathered from the OVP/Phoenix media providers. This information is used by the player and plugins like manifest url, DRM data, media duration and the type of the media.

This object usually will be created using one of the media providers in case Kaltura’s BE is used for hosting your media files.

Additional information includes:

  • String id - correlates to the media/entry id
  • String name - media name
  • long duration - the media duration in ms.
  • MediaEntryType mediaType - indicates the type to be played (VOD, Live or Unknown)
  • List sources - list of source objects
  • boolean isVRMediaType - property to flag if this is VR/360 media
  • List externalSubtitleList - it is optional to add external subtitles to the media

The PKMediaEntry can be created with builder style instantiation, chain setters as follows:

PKMediaEntry mediaEntry = new PKMediaEntry().setId(entry.getId())

To learn more, see PKMediaEntry.


The PKMediaEntry object contains a list of “PKMediaSources”. All sources relate to the same media, but have different formats / qualities / flavors. The player determines which of the sources will actually be played.

To learn more, see PKMediaSource

Manual creation of media source

PKMediaSource can be created with builder-like coding, by chaining setters:

PKMediaSource pkMediaSource = new PKMediaSource().setId(sourceId)

  • In OTT environments:
    Each source represents one MediaFile (Media or AssetInfo contains list of MediaFile items. Each file represents a different format. HD, SD Download…)
    Each file can point to a different video, like Trailer MediaFile and HD media file.
    When playing on OTT environments, specific “format” (MediaFile), should be configured.

  • In OVP environments:
    PKMediaSource items are created according to several criteria:

    • Supported video format: url [.mp4], mpdash [.mpd], applehttp [.m3u8]
    • Flavors: defines the quality of the video.
    • Bit rate

A single “Entry” can have many media sources. The player determines which source to use according to the device’s capability, connection quality, and other parameters, such as which of the sources is best for the current play.

If the media is DRM-restricted, such as Widevine, the DRM information will be needed for playing.


PKDrmParams represents a single DRM license info object. PKDrmParams contains the licenseUri that will be needed for the play. The PKMediaSource contains a list of “PKDrmParams” items. The player will select the source and the relevant DRM data according to device type, connectivity, supported formats, etc.

Example for creating MediaEntry with DRM configuration without media provider

   private PKMediaEntry createMediaEntry() {
        //Create media entry.
        PKMediaEntry mediaEntry = new PKMediaEntry();

        //Set id for the entry.
        //Set media entry type. It could be Live,Vod or Unknown.
        //In this sample we use Vod.

        //Create list that contains at least 1 media source.
        //Each media entry can contain a couple of different media sources.
        //All of them represent the same content, the difference is in it format.
        //For example same entry can contain PKMediaSource with dash and another
        // PKMediaSource can be with hls. The player will decide by itself which source is
        // preferred for playback.
        List<PKMediaSource> mediaSources = createMediaSourcesDRM();

        //Set media sources to the entry.

        return mediaEntry;
    private List<PKMediaSource> createMediaSourcesDRM() {

        //Create new PKMediaSource instance.
        PKMediaSource mediaSource = new PKMediaSource();
        //Set the id.


        // Add DRM data if required
        if (DRM_LICENSE_URL != null) {
                    new PKDrmParams(DRM_LICENSE_URL, PKDrmParams.Scheme.WidevineCENC)

        //Set the format of the source. In our case it will be hls in case of mpd/wvm formats you have to to call mediaSource.setDrmData method as well

        return Collections.singletonList(mediaSource);


Basic Setup