Skip to content
Tilecast Edge is in preview. Its software is complete, but it is not qualified on physical hardware yet. Use the stable Linux Player on production screens until a Tilecast release supports your hardware.

Content compatibility

Edge keeps playing the last presentation it could show if a newer one needs a feature it doesn’t have. It reports the reason to Studio instead of showing a partial or blank presentation.

Edge plays images, downloaded video, native Widgets (including Clock, Date, World Clock, and Countdown), Layouts and playlist zones, transitions, direct assignments, schedules, Takeovers, Quick Present, synchronized Display Groups, unrotated Span content, status screens, the Countdown Bar and alert ticker plugins, and Websites, YouTube, and web Widgets through its isolated remote web helper (GPU-backed frames, audio routing, and real YouTube still need hardware testing).

For large videos and items marked for streaming, Edge downloads and verifies the complete file before it plays it. The item starts a little later the first time, and it keeps playing offline afterward.

  • Rotated Span panels. Edge rotates Span content the same way as the AppImage Player, but check rotation on your own wall before you depend on it.

Codecs, hardware video decoding, and multi-panel frame alignment depend on the hardware. Tilecast does not claim that a whole Intel, AMD, or ARM GPU generation can play a particular profile just because another device in that family can. The WPE/GStreamer path also depends on the kernel driver, userspace video driver, firmware, display backend, and the exact media profile.

Before you roll out, test the exact computer image and the exact video profile you plan to deploy. A successful 1080p30 file does not prove 1080p60, HEVC, 10-bit video, or a different driver stack. Use H.264, yuv420p, AAC-LC in MP4 as the conservative prepared format, and check media preparation for how Tilecast normalizes uploads.

See the capability matrix for the full comparison.

Review these in Studio for the screen you plan to migrate:

  • its direct assignment and upcoming schedules;
  • Layout zones and Widgets;
  • synchronization or Span requirements;
  • installed plugins;
  • Website or YouTube content;
  • Display Control and other hardware features.

The migration also checks the screen’s current presentation before it stops the AppImage Player, and refuses to switch if Edge can’t show it.