Using AI Moments in the Clip Editor Using AI Moments in the Clip Editor

Using AI Moments in the Clip Editor

Overview

AI Moments are the key moments the AI detects automatically in your live streams, such as a soundbite, an interview or a conflict story. They are listed in the Timeline tab of the Clip Editor, so you can find the best passages quickly and turn them into clips in one click.

Which moments are detected depends on the moment types configured for your account. See Managing AI Moment Types.

The Clip Editor monitoring a live stream, with the Timeline panel on the right

The Clip Editor monitoring a live stream, with the Timeline panel on the right

Feature usage criteria

User access to the AI Moments feature is conditioned to the following requirements:

  • AI Moments require the new clip editor (v2). AI Moments are not available from the legacy clip editor (v1).
  • The AI Moments feature shall be enabled on your platform tenant - contact your Backlight representative.
  • As a user, you shall be granted a user profile that includes the permission "Access moment types and categories (read)" .

Find the detected moments

  1. In the Clip Editor, open the Timeline tab in the right panel.
  2. Select Moments. The number shows how many moments are listed.

Each moment card shows a thumbnail, the duration in seconds, the timestamp, the moment type (for example Soundbite / Declaration, Conflict / Diplomacy, Crime / Public Safety or Interview / Newsmaker) and a title. A scissors icon creates a clip, and a chevron expands the card.

Moments list: tab, card details, scissors and chevron

Moments list: tab, card details, scissors and chevron

Filter by moment type

Click Moments again to open the Filter types list. Tick or untick whole categories or single types: for example untick Ads (SCTE) to hide breaks and keep News, Current Affairs / Magazine and Talk / Debate. Use Select all or Clear, then click Apply. The list shows only the selected types.

Filter types list

Filter types list

Timeline filter selections are remembered between sessions for each stream. SCTE-generated Moments are also accessed through the Moments filter rather than a separate SCTE filter.⁠

Note: Filtering changes what you see—not what the system detects.

Review a moment

Jump to it. Click a card: the player moves to the start of that moment. Click another card and the player moves again.

Spot overlaps. A white bar on the left of a card means this moment overlaps the one you clicked. For example, a 28-second moment can sit inside a 4 min 04 s moment, so several detected moments can cover the same sequence.

White bars mark moments that overlap

White bars mark moments that overlap

Read the metadata. Click the chevron to expand a card. The fields depend on the moment's category. For example:

  • Soundbite / Declaration: speaker, quote, topic.
  • Crime / Public Safety: incident type, location, summary.
  • Conflict / Diplomacy: event, location, actors, outcome.

Metadata of a soundbite and of a crime story

Metadata of a soundbite and of a crime story

The default metadata are set per moment type or category. See the related articles below.

Create a clip

Click the scissors icon on the card (the tooltip says Create clip).

Create clip on a moment card

Create clip on a moment card

The Clip Editor switches to clipping mode, with the moment selected on the timeline. Check that the content matches the moment's title, then continue as for any clip.

Clipping mode after creating a clip from a moment

Clipping mode after creating a clip from a moment

  • Managing AI Moment Types: create and configure the types of moments the AI detects.
  • Managing AI Moment Categories: group moment types and set their shared settings.⁠

Limitations

Editorial review is required

Detection and generated metadata can be imperfect. Review the source rather than relying solely on a title, label, or score.

Results depend on content and configuration

Detection quality depends on the source, available signals, and how clearly the type is defined. There is no documented guarantee that every relevant passage will be detected. ⁠⁠

Configuration changes are not guaranteed to reprocess history

Do not assume that changing instructions or source scope automatically re-analyzes earlier content. Confirm historical reprocessing behavior for your environment.

Advanced automation is separate

AI Moments detection does not itself imply automatic highlight assembly or automatic clip creation, branding, and publication. Storybot and Moment-triggered workflows are separate capabilities. ⁠⁠

Availability varies by deployment and permissions

Source workflows, configuration controls, and card actions depend on your deployed version and account access.

FAQ

What is the difference between a category and a type?

A category groups related types and provides shared context. A type defines a particular detection target and its metadata.

What is the difference between a Moment and a clip?

A Moment identifies a source segment. A clip is content you create and refine through the editing workflow. Detecting a Moment does not mean it has been published.

Why do I see no Moments in the Timeline panel?

Check:

  • feature availability and your permissions;
  • that you are using Clip Editor V2;
  • the source configuration of the relevant types;
  • that the source is running or has been analyzed;
  • the Timeline’s selected Moment filters.

Why does a type apply to an unexpected source?

Review the type’s source configuration, inherited category scopes, and applicable source tags.

Why does a duplicated type have different sources?

The documented duplication behavior inherits the category’s scope rather than copying the original type’s scope. Review it before use.⁠

Does hiding a type in the Timeline stop its detection?

No. Timeline filtering and source detection configuration serve different purposes. Change the source configuration when you want to change where detection applies.

Can AI Moments automatically create a finished highlight reel?

Not through the detection workflow described here. Automated assembly is a separate capability. ⁠⁠

What should I do when a Moment is incorrect?

Review the source, refine the excerpt in your editing workflow, and check whether the type’s instructions need improvement. Do not assume that correcting one result changes future detection behavior.