---
title: "Cue Point Scheduler Processor"
slug: "cue-point-scheduler-processor"
updated: 2024-11-26T22:03:07Z
published: 2024-11-26T22:03:07Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.tritondigital.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Cue Point Scheduler Processor

The **Cue Point Scheduler Processor** is used for RAS systems that do not provide **End Break** metadata events. For example, the RAS for a talk radio station that has ad breaks but no other metadata. We use the duration of the ad break or literal value to determine when to send an End Break metadata event.

This processor is distinguished from the other processors by the fact that it doesn't change the cuepoint, but depending on a condition generates a new cuepoint instead.

When the processor receives a message, it cancels an active schedule and creates a new one only if the message corresponds to the trigger. Thus, overlapping breaks will send only one end break at the end.

| **Param Name** | **Mandatory** | **Description** | **Possible Value** |
| --- | --- | --- | --- |
| Trigger Key | Yes | Name of the RAS message field. E.g., `category`. | Not null. |
| Trigger Value | Yes | Value the RAS message field contains that triggers the schedule of an end break message. Could be a mask (VB-like syntax). E.g., `b*` or `break`. | Not null. |
| Duration | Yes | A string template for duration value, could be a constant or a referral to a RAS message value. For example `1:35` or `{duration}` | Not null. |
| Duration Format | No | Defines a format of the Duration value; uses the same format as the TimeSpan processor. E.g., `hh:mm:ss` or `s` | Default value is `fff` (milliseconds). |
| Offset | Yes | Offset in milliseconds to add to the scheduled cue point. | Not null. |

### Example of Use

![CuePointSchedulerProc_example](https://cdn.document360.io/7124b381-0a94-401a-abbd-9df9c4ea5dff/Images/Documentation/71233600-6a9e-4d12-add8-63a37a9448db.png)

The above example is interpreted as follows:

- When `ad_type` equals `BREAK` use `cue_time_duration + 250` milliseconds (offset) as **New Cue Point Schedule Time**
- Create a new cue point with the following attributes:
  - `ad_type` = `END_BREAK`
  - `cue_time_duration` = `0`
  - `cue_title` = *copy of Trigger cue point* `cue_title`
- Therefore, in `cue_time_duration + 250 milliseconds` send new cue point to **OutputConnecter**.

> [!NOTE]
> When a scheduled cue point is set, it will be cleared whenever a fresh cue point is received by RAS Adapter (as there is no need for the scheduled cue point).