Skip to content

Guidelines to Use MediaQueue and MediaControl API#

Media Control and Media Queue API implementation guidelines

What is Remote Control?#

The Remote Control functionality is intended for controlling a single media item at a time. For instance, when a passenger performs actions such as seeking, rewinding, fast-forwarding, or adjusting the volume, these commands are sent through the RemoteControl API. This API acts only as a communication channel, transmitting the passenger’s input from the PED to the seatback monitor.

For example, if a passenger selects ‘Next’ to play the following track in an album, the PED sends a ‘Next’ command to the seatback. Once the seatback receives this event, it is the responsibility of the Interactive application to manage the actual process of loading and playing the next track. The same applies to other operations such as volume adjustments, seeking, rewinding/forwarding, changing soundtracks, or switching subtitles. The PED simply sends the corresponding event, and upon receiving it, the Interactive system on the seatback determines how to handle and execute the requested operation.

What is Media Queue?#

The Media Queue API is used to manage lists of media items—such as tracks in an album, episodes in a TV series, or items in a custom playlist. In scenarios where multiple items are involved, the Media Queue API provides the necessary functionality to perform various playlist-related operations.

A key advantage is that the Interactive application does not need to maintain its own copy of the media list. The Media Queue API ensures that the playlist remains synchronized between the paired PED and the seatback monitor.

Beyond basic list management, the Media Queue API also supports advanced features such as shuffle mode and repeat mode. It keeps track of important information like the currently selected index and offers events such as ‘has next/previous’ and playback-end notifications. These events enable both the PED and the seatback to handle user interactions and playback operations efficiently and consistently.

What is now playing information?#

The Now Playing information is sent from the seatback monitor to the paired PED to provide details about the media currently being played. This message enables the PED to stay updated with the active playback state, including information such as the content type, media URI, elapsed playback time, and the current playback status.

The mechanism used to deliver this Now Playing data is part of the MediaPlayerControl API within the seatback SDK. In addition to updating the PED, this information is also consumed by other software components within the system, allowing them to trigger various events or actions based on the current playback state.

What is player id?#

The IFE system supports multiple remote control instances, and the player ID serves as a unique identifier for each media player. For example, if we want to create separate remote controls for different player types-such as an audio player and a video player-the player ID allows these instances to be distinguished from one another.

On the PED, instances of RemoteMediaControl are provided based on this player ID. The seatback can expose multiple remote control interfaces, each associated with a different player ID. When the PED sends any command to the seatback monitor, the command also includes the corresponding player ID. This allows the seatback to know exactly which player should handle the command. The default player ID is MediaQueuePlayer, which means that when a launch request is sent from the PED to the seatback monitor, it is received with this player ID by default.

Do we need to implement the Remote Control API if we are already using the MediaQueue API on the seatback?#

Yes, both APIs need to be implemented together. The MediaControl API is also required because certain Media Queue operations rely on it. For example, when a ‘play’ action is triggered from the Media Queue (from PED), it results in a launch media request that is handled by the MediaControl API. Similarly, other queue-based actions depend on MediaControl to complete the playback workflow.

When to use which API?#

  • Use the MediaQueue API—whether from the PED or the seatback monitor—whenever you need to load, launch, or play a collection of media items such as an album, a TV series, or a custom playlist

  • Use the MediaControl API when you need to play a single media item, such as a movie or Live TV.

  • Since the MediaQueue API does not support playback operations like seek, rewind, fast-forward, or volume adjustments, the PED must use the MediaControl API to perform those actions. Additionally, it is recommended that the PED invoke the ‘Next’ or ‘Previous’ methods when navigating multiple items. When the seatback receives a next/previous event, the Interactive application will call the corresponding MediaQueue ‘Next’ or ‘Previous’ method if the player ID is MediaQueuePlayer.

Version 1.0