Tag: Metadata

Categories
Knowledge Support Support Illustra exacqVision Server Categories Products

Performance Issues Caused by Disabling Metadata while Camera is Connected

Description

Disabling AI metadata within a camera while connected to the exacqVision Server application could lead to camera performance issues.

Product

Any IP Camera providing AI classification metadata.

While this was specifically seen and tested using Illustra devices it can be expected to occur with any camera providing metadata such as AI Object Classification.

Steps to Reproduce

  1. Connect a camera providing AI Object Classification or LPR metadata to the exacqVision Server.
  2. While the device is connected and streaming, enter the camera web browser interface.
  3. Within the camera settings disable the metadata stream. For Illustra Pro Gen4 and Flex Gen4 cameras, this is done by unchecking the ‘Enable AI Object Classification‘ box on the AI Object Classification tab.

Expected Results

Users probably expect no visible change and for the camera to cease streaming metadata.

Actual Results

The camera may become sluggish to respond to commands or provides reduced video performance.

The exacqVision Server logs show repeated entries stating:

Network error 103 in metadata stream

Error code 103 is defined by the exacqVision plugin. The value ‘103’ could change when upgrading or downgrading the exacqVision Server software. The value is calculated as the last libcurl error + 2.

Solution

  1. Navigate to the Add IP Cameras page in the exacqVision Client software.
  2. In the IP Camera List, locate the camera.
  3. Uncheck the box in the Enabled column.
  4. Wait a few seconds, then check the Enabled box to re-enable the connection.
  5. In some cases this may not resolve the issue and the camera will need to be rebooted.

<br>

Categories
User Guides Documentation exacqVision Client exacqVision Server Categories Products

Maximum Days to Keep Bounding Box Metadata Explained

Description

Despite adhering to Analytic Metadata Best Practices, users could encounter storage or performance issues. Symptoms, such as software performance issues or operating system drives that fill up, may be encountered as a result.

More devices than ever today are implementing advanced analytics to detect and classify objects within camera views or audio. Many of these analytic functions continue to emit classification data at a high rate, whether or not anything is occurring. Consider a camera configured with vehicle detection. A camera directed at a street or parking lot is likely to continue to emit metadata about each vehicle each second regardless of the fact that they may be parked, doing nothing of considerable interest to the viewer. As a result, the database receiving this metadata can grow to large size very quickly.

Product

  • exacqVision Server 23.09 or higher
  • exacqVision Client 23.09 or higher

Both Server and Client versions must be version 23.09 or higher to take advantage of this feature.

<br>

Solution

Maximum Days to Keep Bounding Box Metadata

Located at the bottom of the Event Linking page, just above the buttons to add and delete new event linkages, this control allows administrators to enter the maximum number of days, up to 365, to retain the bounding box data for object classification analytics.

This provides a method, beyond following metadata best practices, to aid in controlling the size of the database to improve forensic metadata search performance and limit its size. Data that reaches this threshold will be eliminated from the database.

IMPORTANT: If your drive was previously filled to capacity due to the database size, delete the eventpi.db file from the exacqVision Server directory, then restart the exacqVision Server service.

NOTE: While this constrains the size of the database, once removed these metadata points may not be used in forensic searches.

<br>

Categories
Configuration Knowledge Support Support exacqVision Client exacqVision Server Categories Products

Analytic Metadata Best Practices

With Artificial Intelligence being used more often users may notice a spike in the analytic metadata being processed and stored.  Here are our recommendations to manage this increase.

Update exacqVision Server/Client Software

  • Ensure you are running the latest version of both exacqVision Server and Client software.  
  • Search “updating” in the exacqVision Client User Manual, available Here for information on updating.

Adjust Camera Settings

  • Access Analytics from the camera’s configuration GUI page
  • Only those analytic types required by the customer should be enabled
  • The goal is to keep this setting as minimal as possible, while still achieving the customers goals.

Reduce DB retention period

  • Reduce ‘Maximum Days to Keep Bounding Box Metadata’ available in exacqVision Server/Client 23.09 and higher. See: Maximum Days to Keep Bounding Box Metadata Explained
  • Reduce the ‘Maximum Days to Keep Logged Events’
  • These settings decide when older items should be removed or “Purged” from the Database (eventPI), the lower the value, the less storage needed. 
  • It is recommended to set this value as low as possible and adjust based on available storage when data is processing
  • Customer retention requirements must also be considered.

Disable Analytics

  • Each camera is different, but if the user does not have enough storage for 24 hours of analytics, or if analytics are not needed, currently the best option is to disable the analytics completely. 
  • Within the exacqVision Client software, go to Configuration → Server → Configure System → Add IP Cameras → Camera Recording → Analytics Camera → Analytics tab – Uncheck “Record analytic data”

AESW-5987

Categories
Knowledge Support Support exacqVision Server Categories exacqVision Integrations

Samsung Motion Issues

Description 

Samsung cameras have experienced motion recording issues when running exacqVision Server version 22.09 or lower.

Product 

  • exacqVision Server version 22.09 or lower
  • Samsung Cameras

Steps to Reproduce 

  • Configure Samsung camera to record on motion

Expected Results 

  • Video is recorded when motion is present

Actual Results 

  • One or the other of the following states have been observed
  • Video is recorded constantly even when no motion is present
  • No video is recorded i.e. motion is not detected even when present

Solution

It was determined this was a result of metadata timeouts and can be resolved by updating to exacqVision Server 22.12.3.0 or higher.

Categories
Knowledge Support Support Illustra exacqVision Server Categories Products

My Illustra Camera Isn’t Recording Motion

Issue

Illustra cameras may be showing a status of “Motion not Supported” or motion is not being detected.

As part of cyber security compliance Illustra camera firmware is now defaulting to ‘Enhanced’ vs ‘Standard’ security resulting in the camera sending out metadata over HTTPS instead of HTTP. 

Resolution

Select one of the following options:

  • Update the Server version to 22.12.5 or higher.
    Exacq’s ability to accept metadata over HTTPS was enhanced in version 22.12.5. If your SSA does not permit you to update the ExacqVision Server version to 22.12.5 or higher, you will need to choose from the remaining options below.<br><br>
  • Factory default the camera and choose Standard instead of Enhanced security. See Article 14441 on the differences between Standard and Enhanced security modes.
  • Or if the camera is using Enhanced Security, then enable ‘Video over HTTP’ in the camera’s GUI
    • To change this setting, navigate to the Security page in the Illustra camera web interface.
    • Click the ‘Edit’ link beside ‘Video over HTTP’.
    • Place a check mark in the box adjacent to ‘Video over HTTP’.
    • Return to the ‘Add IP Cameras’ page in the ExacqVision Client.
    • Disable then re-enable the camera to pull the new camera settings.

<br>