How Alibaba’s OnePlayer Powers Immersive Dual‑Screen Playback for “The Longest Day in Chang’an”

Player Business Framework

Alibaba’s player framework, called OnePlayer, uses a simple yet elegant model that decouples all player functionalities into independent plugins, allowing both the framework and the team structure to be loosely coupled and adaptable to complex playback scenarios.

Player View Model

The view model consists of multiple layers, each containing layout plugins; the player publishes messages that plugins subscribe to, with configuration driven by XML files.

Core Features

Message‑driven, event‑based architecture using publish/subscribe.

Independent plugin structure with no mutual dependencies.

Configurable composition: layers and plugins are assembled like building blocks.

Rich, extensible plugin library; custom plugins can replace defaults.

Multiple player instances can coexist on a single page, isolated from each other.

Technology Empowering Business Development

Open Architecture : Plugins isolate business logic, eliminating explicit dependencies and enabling teams to create personalized players without redundant work.

Standardized Development : Uniform plugin interfaces, lifecycle, and event handling simplify cross‑team collaboration and promote reuse.

Service‑Oriented Playback : Clear separation between playback capabilities and business code facilitates modular deployment and integration with other services.

Cool‑Watch Encyclopedia

The encyclopedia provides contextual tips during playback (e.g., explaining historical time‑keeping), allowing operators to update content via a backend without code changes, and enabling dynamic UI styles that blend with video content.

Sub‑Screen (Mother‑Screen & Child‑Screen)

Sub‑screen splits the display into a main (mother) screen for the primary video and a smaller child screen for auxiliary or interactive content, similar to live‑event side‑bars.

Resources are stored separately, allowing operators to configure and deploy child‑screen content independently, avoiding the limitations of pre‑merged streams.

Dual‑Stream Synchronous Playback

Two playback instances are used—one for each screen—to maintain a clear master‑slave relationship and simplify context management.

Key challenges include cumulative system error, limited precision of player APIs, and device variability. Solutions involve precise anchor timing, error‑compensating seek APIs, adaptive caching, statistical frame‑offset correction, and optimized speed‑change curves.

Synchronization Strategy

Anchor synchronization based on the main video clock (audio, video, or external).

Recursive adjust‑feedback‑correct loop for fine‑grained alignment.

Statistical methods to mitigate device‑specific randomness and network variability.

Through architectural design, engineering optimizations, and algorithmic upgrades, the system achieves accurate multi‑stream synchronization, delivering an immersive viewing experience.