Timeshifting

The Timeshifting page selects which content types start and stop timeshift recording.

Timeshifting is driven by playlist content types. This means the configuration depends on how the station marks tracks, jingles, promos, spots and other items in the library and Clock Formats.

Before changing this page, understand the station's delayed-broadcast workflow. The correct settings depend on where the delayed segment begins, where it should end, and which playlist items mark those points reliably.

Start Timeshift Recording

The upper section selects content types that start timeshift recording.

The default source-code configuration starts on Track. This matches a common workflow where music or program content marks the start of a delayed segment.

Select only content types that really indicate the start of the material that should be timeshifted. If the wrong type starts recording, the timeshift may begin too early or during station imaging.

Use a start content type that appears predictably in the relevant Clock Format. If the first item of the segment is sometimes a track and sometimes a live source, promo or special item, review whether the content type plan is stable enough for automatic timeshifting.

Stop Timeshift Recording

The lower section selects content types that stop timeshift recording when those items are used as fill-out items.

The default source-code configuration stops on Jingle, Promo and Spot.

Stop behavior is commonly connected to fill-out items, because these items mark a point where the delayed workflow can be closed or handed back.

Choose stop content types that really mark the end of the delayed segment. If a stop type also appears inside the delayed content, the recording may close too early.

Content-Type Discipline

Timeshifting depends on correct content types in playlists and Clock Formats. Review these settings before special programming.

If a Clock Format changes content types around a live or delayed segment, timeshift recording may start or stop at a different moment than expected.

Do not use a broad content type such as Miscellaneous for timeshift markers unless the station has a strict rule for what that type means. A broad type can accidentally start or stop timeshifting for unrelated one-off items.

Timeshifting is a good reason to keep Clock Formats tidy. If programmers use content types casually, delayed recording behavior becomes less predictable.

Practical Examples

Example decisions:

• A music-program delay may start on Track and stop when a fill-out Jingle or Promo is reached.
• A commercial-safe workflow may stop on Spot if spots mark the end of the delayed material.
• A special-event workflow may need a dedicated content-type convention or a carefully reviewed Clock Format.

The right setup is the one that matches the playlist structure the station actually uses, not a generic default.

Operational Checks

After changing Timeshifting settings:

1. Use a test playlist with the same content types as the real show.
2. Check where recording starts.
3. Check where recording stops.
4. Check fill-out behavior.
5. Confirm the expected recording is available afterward.
6. Repeat the test with a playlist that includes commercials, promos and jingles near the boundaries.

See Timeshift for operational advice.

Common Pitfalls

• Using a content type as a marker while also using it inside the delayed segment.
• Forgetting that Clock Format changes can alter timeshift behavior.
• Testing only with a simple playlist and then using the setting with a more complex real show.
• Letting imported or dropped files keep the wrong content type.