> For the complete documentation index, see [llms.txt](https://docs.sonoransoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sonoransoftware.com/store/cctv/playback.md).

# Live View and Historic Playback

Monitor CCTV cameras live and replay recorded incidents later from the archive.

CCTV is built around historic review. Operators do not need to be watching a camera when an incident happens: configured motion detections and bookmarks create recordings that can be opened later from the archive.

<figure><img src="https://954277862-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FA1LA3ay59CDyDKnfXPfc%2Fuploads%2Fgit-blob-0a91ca18ecda481ccbcd577d20719a0eaad3d670%2Fcctv-archive.webp?alt=media" alt="CCTV archive containing motion-detected recordings"><figcaption><p>The archive lists captured incidents for authorized reviewers.</p></figcaption></figure>

## Record an incident

A recording can begin from:

* A configured motion detection
* An operator bookmark
* Another supported, authorized event workflow

Events Core preserves pre-event and post-event context so the replay is not limited to the exact instant that triggered it. Each finalized recording keeps the camera definition and angle from the time of the incident.

## Review historic footage

1. Run /cctv.
2. Open **Archive**.
3. Find the recording by event type, camera, or time.
4. Select the view or play action.
5. Use the playback controls to review the incident.

Reviewers can pause, seek, skip backward or forward, step through the timeline, restart, and change playback speed. Moving or deleting the current camera does not rewrite the viewpoint saved with a completed recording.

<figure><img src="https://954277862-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FA1LA3ay59CDyDKnfXPfc%2Fuploads%2Fgit-blob-9e7c7ecf3c35d77e9806a54e80e91616b4899188%2Fcctv-historical-playback.webp?alt=media" alt="Historic CCTV recordings ready for replay"><figcaption><p>Return later and replay what happened after the scene has cleared.</p></figcaption></figure>

## What is preserved

Events Core records the gameplay state required to recreate the incident, including relevant entities, movement, the environment, event markers, and the camera perspective. This makes later in-game replay possible without continuously streaming a live camera to an operator.

When optional upload, export, or Discord workflows are configured, the archive actions and permissions control who can create or share an additional recording artifact.

## Live view

Live view opens the selected camera immediately. Each camera supports up to eight viewers by default. Zoom is enabled; pan and tilt depend on the camera's configured capabilities.

Live view and historic recording are separate workflows. Watching a feed does not replace motion or bookmark recording, and a recording can be captured without anyone viewing the feed.

## Night vision and overlays

The shipped presentation includes timestamps, the Sonoran Security watermark, and night vision. Thermal viewing is disabled by default.

<figure><img src="https://954277862-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FA1LA3ay59CDyDKnfXPfc%2Fuploads%2Fgit-blob-e9920a6eae551082a2abbefe27d0646a523011a4%2Fcctv-night-vision.webp?alt=media" alt="CCTV camera using night vision"><figcaption><p>Night vision can be toggled for dark locations when enabled in configuration.</p></figcaption></figure>

## Retention and storage

The default recording retention is seven days, with a configured maximum of 90 days. Local recording data is stored under eventsCore/data/recordings; terminal and camera state is stored in eventsCctv/data/cctv.json.

Use the archive's preserve and deletion controls only with the corresponding permissions. Back up evidence data securely before updates or storage changes.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.sonoransoftware.com/store/cctv/playback.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
