Skip to main content

Screens

Screens are the scheduling targets used by events and preview. Each screen receives its own generated playlist and its own display-oriented configuration.

What A Screen Represents​

A screen combines two responsibilities:

  • it acts as the scheduling target for event sequences
  • it defines the display mapping settings used for playback presentation

Operators most often interact with screens through scheduling and preview. Admins usually manage the screen configuration itself.

Key Screen Fields​

Name​

Use a clear name that matches how operators refer to the display in real life.

Examples:

  • North Lobby
  • Facade East
  • Canvas A Left

Target​

The Target links the screen to the broader playback topology.

This relationship matters when validating output routing, preview, and player alignment.

Extensions​

Screens can be associated with extensions.

  • use this when a deployment needs screen-specific custom configuration
  • keep extension usage documented so operators understand which behavior is global and which is screen-specific

Mapping Settings​

The screen mapping section controls how content is positioned and sized.

Typical fields include:

  • resolution: w, h
  • transform: x, y
  • scale: x, y
  • rotation

These settings determine how scheduled content is presented on the actual display surface.

Screen Sidebar Stub screenshot: screen sidebar with general settings, mapping fields, and advanced crossfade visible. Save final image at packages/docs/screenshots/app-screen-sidebar.png.

Advanced Setting: Crossfade​

The Crossfade value controls transition timing at the screen level.

  • crossfade can affect how playback changes are perceived visually
  • crossfade can also matter when validating timing-sensitive schedules in preview

If exact timing matters, test the screen after changing crossfade-related settings.

How Screens Relate To Events​

Events target screens through sequences.

  • one event can contain multiple sequences
  • each sequence can be associated with one or more screens depending on the workflow in use
  • preview is always evaluated for a specific screen

This means screen configuration affects both the operational display result and the scheduling context operators work against every day.

Screen Selector Stub screenshot: screen selector in either calendar or preview showing how operators identify screens during scheduling workflows. Save final image at packages/docs/screenshots/app-screen-selector.png.

Typical Admin Workflow​

  1. Create or open the screen.
  2. Name it clearly.
  3. Assign the correct target.
  4. Apply any required extensions.
  5. Configure mapping values for resolution, transform, scale, and rotation.
  6. Adjust crossfade if needed.
  7. Save the screen.
  8. Validate with preview and, if possible, the live display.

Operational Guidance​

Keep Naming Consistent​

Operators choose screens throughout the schedule and preview workflows.

If screen names are ambiguous, scheduling mistakes become much more likely.

Validate Mapping After Changes​

Any change to resolution, transform, scale, or rotation can affect the visible output.

After editing mapping values:

  • open preview for the affected screen
  • check the live display if available
  • confirm that the screen still matches the intended physical surface

Treat Crossfade As A Playback Behavior Setting​

Crossfade is not just cosmetic. It can influence how transitions feel and may affect tightly timed content changes.

Common Mistakes​

  • scheduling content to the wrong screen because of unclear names
  • changing mapping values without validating the live result
  • applying the wrong target assignment
  • forgetting that crossfade can affect timing perception
  • using screen-specific extensions without documenting their purpose