Does 3dEYE Stream Continuously or Only When a Camera Event Is Detected?

3dEYE uses continuous cloud recording, meaning the camera streams video to the 3dEYE cloud at all times. The video is then recorded and stored according to the customer’s configured retention and streaming settings.

Recording is not triggered by motion events, analytics, or camera‑generated alarms. Instead, events and analytics act as markers that help users quickly locate, search, and analyze relevant portions of the continuous video timeline.

How continuous recording works

With 3dEYE, the typical video flow is:

Camera → Continuous video stream → 3dEYE Cloud → Continuous recording and storage

Once video is being recorded in the cloud, any camera event or analytics detection can be associated with the corresponding point in the recording. This allows users to jump directly to important moments without relying on event‑triggered recording. For example:

If a camera detects:

• Motion

• Line crossing

• Intrusion

• Any supported analytics event

…the event is simply used to identify the relevant timestamp in the already‑recorded video.

Why continuous recording is important

Systems that rely only on event‑triggered recording can miss critical footage. For example:

• A camera may fail to detect an incident.

• An event may be generated too late.

• The incident may not meet the camera’s configured detection criteria.

If recording only occurs when an event is triggered, undetected incidents may have no recorded video.

With 3dEYE’s continuous recording architecture:

• Video is always being recorded.

• Even if no event is generated, the footage is still available (within the retention period).

• Users can review incidents that were not detected by the camera or analytics system.

Events and analytics are used to find the video

In 3dEYE, events and analytics do not determine whether video is recorded. Instead, they help users locate and analyze relevant portions of the continuous recording.

For example:

1. The camera continuously streams video to 3dEYE.

2. The video is continuously recorded in the cloud.

3. A camera event or 3dEYE analytics event is generated.

4. The event is associated with the relevant point in the recorded video.

5. The user can navigate to the event and review the surrounding footage.

This approach separates video recording from event detection.

Pre-event context

When navigating between events in the 3dEYE Video Portal, playback begins approximately two seconds before the event timestamp. This provides additional context immediately before the detected event and helps users see what was happening leading up to the event.

Continuous recording vs. event-only recording

3dEYE is designed around continuous cloud video recording rather than event-triggered recording. The camera continuously streams video to the 3dEYE cloud, and the video is recorded according to the customer’s configured retention and streaming settings. Camera events and cloud analytics can then be used to locate, search, and analyze specific portions of that recording.

This ensures complete coverage, reliable playback, and accurate event‑to‑video association.