Service: Channel Engine Scheduler - EyevinnOSC/community GitHub Wiki

Channel Engine Scheduler

Channel Engine Scheduler (serviceId eyevinn-channel-scheduler) is a web-based, broadcast-style rundown interface for creating and managing linear TV channel schedules for Eyevinn Channel Engine instances. In Eyevinn Open Source Cloud (OSC) it is a long-running service instance with up to 10 GiB of storage. License: MIT. Source: Channel Engine Scheduler.

What it can do

  • Professional schedule view with real-time status indicators.
  • Automated Channel Engine lifecycle management: create, start, stop and link engines from the interface.
  • Webhook integration for status monitoring.
  • Live stream previews.
  • Intelligent content looping.
  • Searchable VOD library for content discovery.

Creating an instance

You need existing Eyevinn Channel Engine instances or the ability to create new ones (see FAST Channel Engine), and VOD content available as HLS.

  1. Store your OSC personal access token (found in settings under API) as a service secret with create-service-secret (serviceId: "eyevinn-channel-scheduler", for example name osctoken).
  2. Create the instance with create-service-instance using serviceId: "eyevinn-channel-scheduler". The instance name must be alphanumeric and at most 20 characters.
{ "name": "channelscheduler", "OscAccessToken": "{{secrets.osctoken}}" }
  1. Wait with wait-for-service-ready or get-instance-status, then read the URL with describe-service-instance.

OSC CLI example:

% osc create eyevinn-channel-scheduler channelscheduler \
  -o OscAccessToken="{{secrets.osctoken}}"

Instance created:
{
  id: 'demo-channel-scheduler',
  name: 'channelscheduler',
  url: 'https://demo-channel-scheduler.eyevinn-channel-scheduler.auto.prod-se.osaas.io'
}

Options

Option Required Type Meaning
name Yes string Name of the instance. Letters, digits and underscore only; on OSC at most 20 characters.
OscAccessToken Yes string, sensitive Your OSC personal access token, used by the scheduler to launch Channel Engine instances. Store as a service secret and pass as {{secrets.NAME}}. The catalog marks it as system-generatable.

A {{secrets.NAME}} reference must be the whole field value. Overwriting a secret does not restart a running instance.

Using the instance

Open the instance URL in a browser.

Configure Channel Engines. To create an engine for a schedule, use "Create Engine" in the interface; the scheduler deploys and manages the engine.

Add content to the VOD library. In the VOD Library section add content by providing HLS manifest URLs, plus metadata such as title, duration and description.

Create a schedule. Select or create a Channel Engine instance, open the Schedule view and add content blocks with the plus sign on a VOD.

Monitor channel status. The interface shows channel status indicators (running, stopped, error), a live preview of current content and webhook status.

Multiple channels. Create separate schedules per channel, use the dashboard view to monitor all channels and switch between channel views with the navigation menu.

Troubleshooting:

  • Channel not starting: check VOD content accessibility and Channel Engine status.
  • Schedule conflicts: use the conflict detection feature to find overlaps.
  • Webhook failures: verify endpoint availability and authentication.

Limitations

  • Requires active Channel Engine instances to manage.
  • Content must be accessible via HLS.
  • Real-time schedule updates depend on webhook connectivity.

Resources