This article is about best practice when integrating CMS systems with PIXERA.

System Architecture

There are different possible system architectures for this use case.

Basically, it makes no difference where the CMS system is hosted, whether it is hosted on a local server or online, it makes no difference to our setup, which is why the CMS server is always represented here as a cloud, but the actual IT architecture may vary.

1. CMS, Local Server hosting Logic, API Use of PIXERA

2. CMS, PIXERA Control

3. CMS, Custom Software, Local API Use of PIXERA

In most cases, we recommend option 2 or 3, CMS coupled with PIXERA Control. The best example is ISAACPlayer24H Module, which uses a control module as a connector between the web server and PIXERA.

The module handles the logic of building the timeline communication with the web server within Control.
 

Best Practice When Integrating a CMS System

Timeline Structure

When integrating a CMS system, it is strongly recommended to use a single 24-hour timeline rather than alternating between two timelines with crossfades. A continuous 24-hour timeline provides greater stability, simpler logic, and fewer synchronization issues.

When building timelines via API—especially using JSON bulk commands—it is important not to create too many elements at once. Although the JSON bulk build command improves efficiency, creating, for example, 70 layers with 24-hour duration in a single operation should be avoided.

Instead, it is recommended to:

• Build the timeline progressively (e.g., approximately 4 hours ahead).
• Alternatively, place a defined number of future elements on the timeline.
• As a practical guideline, scheduling 20–100 elements ahead of the current Now Pointer has proven effective.

This approach improves performance, reduces system load, and maintains responsiveness.

Managing Handles for Stable Cleanup

During timeline construction, it is recommended to store the handles of created clips and cues together with their corresponding timestamps.

This allows elements positioned behind the Now Pointer to be safely and reliably removed at a later stage, ensuring long-term timeline stability and preventing orphaned objects.

24:00 → 00:00 Transition

When transitioning from 24:00 back to 00:00, a hard cut without fade should be used.

The first container of the new cycle should be positioned so that it starts exactly in the next frame after the final container at 24:00.

This method ensures:

• Seamless looping
• Frame-accurate transitions
• Compatibility with external timecode workflows

The same principle applies when operating with Timecode PIXERA input.

File Download and Content Import

There are two common approaches for content synchronization:

Network Path Integration

A network path can be mounted, and communication with a web server can determine when files are available. Once available, the files can be imported into the PIXERA resource tree.

External Downloader Process

In some workflows (e.g., Isaac integration), a dedicated downloader process is started externally.

Currently, PIXERA does not provide native API commands for downloading content directly from the web. Therefore, downloading must be handled outside the software.

Common API Commands

Batch Clip Creation

string createClipsFromJsonString(string jsonString)

Creates multiple clips in a single JSON-based batch operation.
Batch create/remove clips via API 

Batch Clip Removal

null removeClipsFromJsonString(string jsonString)

Deletes multiple clips using a JSON definition.
Batch create/remove clips via API 

Import Resources from Directory

handle[] addResourcesFromDirectory(string path, bool removeOthers, bool checkRedundancy)

handle[] addResourcesFromDirectoryRemoveAssets(string path, bool removeOthers, bool checkRedundancy)

Used for importing content into the resource tree.

UI Update Blocking (Optional)

null blockUiTimelineUpdates(bool doBlock, int terminationDurationInMs)

Can be used in certain cases to achieve smoother timeline builds by temporarily blocking UI updates.

However, in this specific use case, this method is considered deprecated. When placing clips via JSON API batch commands, the system handles operations more efficiently internally. Therefore, blockUiTimelineUpdates is only recommended when creating clips or layers individually — not when performing batch operations via JSON.
 

PIXERA 26.1  | 2. March 2026 | J.B.