Giraffe CCTV
  • What is Giraffe?
  • Architecture
  • Giraffe Cloud
    • Getting started
      • Logging in
      • First steps
      • Giraffe terminology
      • Managing your account
    • View and control
      • Live talkdown
      • PTZ presets
      • Quick sounds
      • Custom views
      • Strobes
      • Floodlights
    • Alarm handling
    • Recording
      • Recording configuration
      • Recording playback
      • Exporting footage
    • Schedules
    • Active threat deterrence
      • Arming and disarming
      • Alarm states and configuration
    • System monitoring
      • Overview
      • Graphs
      • Events
      • Error states
    • Notification system
      • Person / vehicle alerts
      • Rate limits
    • Camera setup
      • Artificial intelligence
      • Masking
      • Camera configuration
      • Camera guides
        • Pelco
        • Hanwha
        • Axis
        • Dahua
        • Hikvision
        • Milesight
    • Router integration
      • Peplink
      • Teltonika
      • Advanced
    • Team management
      • Team hierarchy
      • Inviting users
      • Permissions
    • ARC integration
      • Sentinel Native
      • Generic Integration
      • Immix
      • Sentinel - Deprecated
    • Reseller teams
      • Team management
    • Troubleshooting
      • MTU Configuration
    • Advanced
      • Firewall whitelisting
      • White label
    • API
      • RTSP Service
      • HTTP API
  • Mobile App
    • Installing
    • Signing in
    • Live view
    • Recording
    • Updating
    • Privacy policy
  • Edge Controller
    • Edge Controller versions
    • Hardware overview
      • Edge Controller V2
      • Edge Controller V1
        • Status lights
    • Configuration
      • Device definitions
      • Camera power
    • Battery Calibration
    • Mobile routers
      • Router guides
        • Teltonika
          • Unblocking WebUI access
        • Peplink
    • Victron integration
    • SMTP Alarm Receiver
    • PIR sensors
      • Luminite Genesis PIR integration
      • Wired PIR sensors
    • Power consumption
    • Boot / shutdown procedure
    • GPS
    • EFOY integration
    • Advanced
      • Internal queue system
      • Self healing
      • Recording storage
  • Hub Controller
    • Overview
    • Installation
    • Troubleshooting
  • Mobile Security Unit
    • Overview
    • MSU Generations
    • Battery
  • Network Node
    • Overview
  • Mini Tower
    • Overview
    • Transporting the tower
    • Deployment steps
    • On site setup checklist
    • Pack away steps
    • Battery management
    • Solar performance
    • Maintenance
    • Branding
    • Troubleshooting
    • Safety
  • Battery Box
    • Overview
  • Giraffe Battteries
    • Charging
    • Safety
  • Solar Frame
    • Page 1
  • Terms and conditions
Powered by GitBook
On this page
  • Retention time
  • Purging recordings
  1. Giraffe Cloud
  2. Recording

Recording configuration

PreviousRecordingNextRecording playback

Last updated 1 year ago

Recording must first be enabled on a camera. The recording settings are found on the camera settings page under the Recording tab.

  • Recording can be enabled or disabled with the toggle. When recording is disabled, no new recordings will be saved. Existing footage will not be immediately after recording is disabled, but will be removed subject to the normal retention regime. You can access the recordings again by reenabling recording.

  • The motion sensitivity slider has no effect since motion detection is not currently used.

Retention time

The retention time setting lets you reduce the length of time for which you keep recordings for a particular camera. It is set to auto by default which means it will store the recordings for as long as possible.

If you set a specific number of days, the behaviour will vary. Imagine a scenario where we have a 1TB storage drive, and each camera uses 10GB per day. This means we have the ability to store 100 days worth of footage.

If you have four cameras, with every camera set to auto, each camera will record for approximately 25 days. The oldest recording in the database (from any camera) will be deleted first, followed by the second oldest and so on.

If one of cameras has a retention time of 7 days set, the footage from this camera will always be deleted when it becomes 7 days old, irrespective of how much space is available in the database.

This means that there will be space for another 18 days of footage that will be equally shared between the other cameras. The remaining 3 cameras will now recording for approximately 31 days each.

However, if one of the cameras has it's recording duration set to 50 days, this will have no effect in the above example. The 50 day threshold will never be exceeded, and the recording cleanup process will still round-robin delete all the oldest recordings once the hard drive fills up irrespective of individual camera duration settings.

With the above in mind, if you want to increase the retention time of a particular camera more than the others, the correct way to do it is to reduce the retention time to the mimimum you can accept for the other cameras on the same Edge Controller.

This will have the effect of freeing up as much space as possible for the camera you want to have a longer recording duration.

Purging recordings

Recordings can be mass deleted from the Edge Controller using the purge recordings button. This will wipe the database clean and format the hard drive.