Skip to main content

Streams Generator

The Streams Generator action captures snapshots from all camera streams defined in a branch configuration, updating thumbnails in bulk. It's the system-level utility for ensuring all camera previews are current.


Overview

Managing camera thumbnails across many locations requires automation. This action:

  • Iterates through all configured camera channels
  • Generates correct RTSP URLs based on NVR settings
  • Captures and uploads snapshots in bulk
  • Updates database records for dashboard thumbnails

It's essentially the "batch" version of the single-camera Snapshot Stream action.


What It Does

1. Reads Branch Configuration

The action retrieves the current branch's NVR (Network Video Recorder) settings:

  • NVR IP address
  • NVR brand/type
  • Authentication credentials
  • Channel range to process

2. Iterates Through Channels

For a typical configuration, the action loops through channels 1-16 (expandable to 60+ for larger NVRs):

  • Channel 1 → Attempt capture
  • Channel 2 → Attempt capture
  • ... and so on

Not all channels may have cameras connected—the action gracefully handles empty channels.

3. Generates RTSP URLs

Based on the NVR type, the action constructs the correct RTSP URL format:

NVR BrandURL Pattern
Hikvisionrtsp://user:pass@ip:554/Streaming/Channels/X01
Univiewrtsp://user:pass@ip:554/media/videoX
Dahuartsp://user:pass@ip:554/cam/realmonitor?channel=X

4. Captures and Uploads

For each successful connection:

  • Captures a single frame
  • Uploads to cloud storage
  • Records the new URL

5. Bulk Updates Database

After processing all channels, the database is updated so the RIME Studio dashboard displays current thumbnails for all cameras.


Configuration

The action reads configuration from the Branch record rather than direct parameters:

Branch SettingRequiredDescription
NVR IPYesIP address of the Network Video Recorder
NVR TypeYesBrand: Hikvision, Uniview, or Dahua
NVR UsernameYesAuthentication username
NVR PasswordYesAuthentication password

Channel Range

By default, the action attempts channels 1-16. For NVRs with more channels, this can be extended.


Understanding Results

ResultMeaningDetails
processing_completeBatch completedCheck counts for success/failure breakdown
configuration_errorNVR settings missingVerify branch has NVR details configured

Result Details

The action reports:

  • Total channels attempted
  • Successful captures
  • Failed captures (may indicate missing cameras or connection issues)

Common Use Cases

System Initialization

  • When: After configuring a new branch
  • Purpose: Populate all camera thumbnails immediately
  • Benefit: Dashboard shows actual camera views from day one

Scheduled Refresh

  • When: Daily at 3 AM (or other low-activity time)
  • Purpose: Keep all thumbnails current
  • Benefit: Dashboard always shows recent views

Post-Maintenance Recovery

  • When: After NVR maintenance or power outage
  • Purpose: Verify all cameras are online
  • Benefit: Quick identification of cameras that didn't recover

Multi-Branch Deployment

  • When: Rolling out to many locations
  • Purpose: Standardize thumbnail capture across all branches
  • Benefit: Consistent dashboard experience

Troubleshooting

Configuration Error

  1. Check Branch Settings: Verify NVR IP, type, username, and password are configured.

  2. Correct NVR Type: Wrong type means wrong URL format. Verify the exact brand.

  3. IP Accessibility: Ensure the NVR IP is reachable from the ResEngine server.

All Channels Failed

  1. Network Path: Verify network connectivity between ResEngine and NVR.

  2. Firewall: RTSP typically uses port 554. Ensure this is open.

  3. Credentials: Test credentials by accessing NVR directly.

  4. NVR Status: Confirm NVR is powered on and functioning.

Many Channels Failed

  1. Expected Behavior: Not all channels may have cameras. Failed channels might simply be empty.

  2. Partial Deployment: If only some cameras are installed, failures on unused channels are normal.

  3. Individual Camera Issues: Check physical camera connections and power.

Slow Processing

  1. Network Bandwidth: Batch snapshots use network resources. Off-peak timing helps.

  2. NVR Load: Multiple concurrent connections may slow the NVR. Stagger multi-branch runs.

  3. Timeout Settings: Very slow cameras may timeout before capture completes.


Best Practices

  1. Schedule Off-Peak: Run during low-activity hours (overnight) to minimize network impact.

  2. Verify NVR Settings First: Test single-camera snapshot before running batch to confirm credentials work.

  3. Document Channel Mapping: Maintain records of which channel numbers correspond to which physical cameras.

  4. Stagger Multi-Branch: If running across many branches, stagger start times to avoid network congestion.

  5. Monitor Results: Review success/failure reports to identify problematic cameras.


Supported NVR Brands

Hikvision

  • Most common NVR brand
  • Channels typically 1-16 or 1-32
  • Supports main stream and sub-stream

Uniview (UNV)

  • Professional-grade NVRs
  • Similar channel structure to Hikvision
  • Different URL format

Dahua

  • Popular alternative brand
  • Uses realmonitor protocol
  • Channel-based access similar to others

ActionScopeBest For
Streams GeneratorAll channels in branchInitial setup, batch refresh
Stream Snapshot to RDBAll configured streamsSimilar batch capability
Snapshot StreamSingle cameraSpecific camera capture

  • Snapshot Stream: Single-camera version for specific captures
  • Stream Snapshot to RDB: Similar batch capability with different triggering
  • Object Detection: Uses the same camera streams for analysis