Exporting video with Video Analytics meta data is very useful in the process of optimization of Video Content Analytics performance. One could configure VA, record particular scene and then replay this scene over and over again using different VA configurations.
Moreover the video could be exported and replayed multiple times with different VA configuration settings.
The choice of the tool depends on the way the camera and recording are managed.
Camera that is managed by non Bosch Video Management System (also no VRM recording), or is not recording - Configuration Manager. Configuration Manager is now the best tool for configuring VCA/IVA and some of the other items that required ActiveX.
VRM recorded video - VRM eXport Wizard
Camera that is managed by Bosch Video Management System - VRM eXport Wizard
Note: Forensic search makes possible to search the meta data of the recorded video and select the relevant export stamp. Forensic search is part of BVMS OC and BVMS Viewer
Export of VRM recorded video using VRM eXport Wizard
VRM eXport Wizard description:
is a tool that records or transcodes VRM recorded video.
eXport Wizard is part of VRM installation package
For more details how to use the tool, please read:
version 2.10 > Document attached
Export process with VRM eXport Wizard
VA task should be configured and enabled for the Camera, thus meta data is created and included in the video stream
Alarm Recording should be enabled
Use VRM eXport Wizard to connect to VRM
chose the camera and the time span to be exported. There is no option to replay or search for alarms with this tool, you should know the time span you need to export.
choose location for the export
Note: The exported video created as directory, called export_date_time. It includes the following files and directories.
Record of a video from a Bosch camera
Tools to use in replacement of Internet Explorer and MPEG-ActiveX:
For VCA configuration.
For missing time and date.
Set up the Time Stamping in Configuration Manager or go to Playback where you can see the time and date.
For Instant Recording Button.
If you need Video and Metadata recorded, then Configuration Manager has record option in the VCA/Main Operation tab.
You can record your video and use the Task, Metadata Generation or Meta Inspection tab to analyze the video.
By selecting "show Timeline"
And selecting the video from the Dropdown.
You can also find the file at C:\Users\Public\Documents\Bosch\VIDOS\Recordings. If you want to look at it with Bosch Export player.
There is also an option to record using the Video Security App.
But the will only record video (not Metadata).
The exported / recorded videos can be imported in BVMS OC 10.01. There it is possible to edit the VA Task settings for this particular export and to search the video for alarms. In that way is possible to apply different VA settings to the same video export, compare the results and find the optimal VA settings for the particular scene.
... View more
In order to start to analyze and optimize Video Analytics settings for particular customer set up, we need initial information and export of example video.
This article describes the absolute minimum information we need in order to start analyzing and optimizing Video Analytics performance.
Video Analytics (VA) task performance optimization
Please provide the following details:
Symptom specific Information
Describe the expected result from the VA task.
It is important to get detailed information of the results VA should provide.
Define what is the customer’s priority:
High sensitivity - miss as few true alarms as possible, but increases the likelihood of more false alarms!
High precision – have less false alarms, but accept the risk to miss true alarm!
Using VA is always based on balancing between sensitivity and precision. It is not always possible to get high sensitivity and high precision at the same time.
Provide an export of recorded video that should contain:
for basic understanding of meta data, please read the latest Software Manual Video Content Analytics
for instructions about doing a video export with meta data, please read the article: How to export video including meta data (Export video including Video Analytics meta data).
Couple of examples of false alarms (in case false alarms are the issue)
Provide the number of false alarms per time span (per day, per week, etc.)
What would be acceptable as a number of false alarms per time span
Couple of examples of situation that should have caused alarm, but VA did not generate the alarm as expected.
In this case please provide the time stamp of the event and short description
Screenshot from the Camera Calibration Verification page - only in case calibration is needed for the particular VA functionality
access the Calibration Verification page of the camera (via the Configuration Manager or Web Interface)
provide screenshot from the verification of each parameter used for camera calibration
Note: For more information on Camera Calibration and Calibration Verification, please check:
How To calibrate camera for Video Analytics?
... View more
Related Products: Configuration Manager 7.00 and above.
This article shows how to use recorded video in Configuration Manager in order to calibrate a camera and to configure a task.
Camera Calibration using Recorded Video
It is possible to calibrate camera using already recorded video in Configuration Manager 7.0. This feature is independent of the camera firmware version.
Configure a Video Analytics Task using Recorded Video
It is possible to configure a Video Analytics Task, using already recorded video in Configuration Manger 7.00 and above. This includes initial Task configuration, verification and then further performance analysis over the time and fine-tuning of the task parameters.
Note: There are multiple video analytics how-to videos in the following lists:
Calibration playlist: https://www.youtube.com/playlist?list=PLz97rFi-OzLfI2F4sP-ocX3BhX0rtJvgt
Video Analytic how-to playlist: https://www.youtube.com/playlist?list=PLz97rFi-OzLdPrzs-SR-g1oo4RkV9mvf5
... View more
In order to quickly offer a technical solution or to provide a professional advice for the next analysis steps, the technical support specialists need to get some general and basic information.
Ticket content should always be in English and provided in a well summarized and structured way in order to be able to provide a quick and appropriate feedback.
Not following the guideline will impact the processing time of the ticket.
Related Products: BVMS Operator Client
This article describes the initial steps one can take for troubleshooting BVMS display issues (during live view or playback). It also summarizes what initial information and logs are needed for support in order to start the issue investigation.
How to retrieve the Hardware ID for BVMS and check the Software Maintenance Agreement (SMA) status?
BVMS stand alone or appliance
Detailed problem description
Check and eventually update the version of your Graphic Card driver.
During BVMS system tests there were documented cases of display issues related with out of date Graphic card divers. ❗ It is important that the Graphic Card driver of the client is up to date. Find the supported version of the Graphic Card driver in the corresponding to your BVMS version Release Notes (https://downloadstore.boschsecurity.com), in the section Hardware drivers.
Symptom specific Information
Is the issue camera type / FW dependent?
Are all the devices in the system affected?
Is the issue existent for all BVMS Operator Clients in the system?
Is the issue existent for hardware decoders, for camera Web Interface or other display Clients?
Is the recording, the playback or are both affected?
BVMS ConfigCollector logs keeping the following conditions:
From the machine that shows the issue
VSDK logging – please follow the steps from the article:
How to collect Video SDK log files
VRM logs (in case VRM runs on the same machine like the BVMS MS, then BVMS ConfigCollector logs from the server)
for VRM version 3.82 and onwards use VRM Monitor. The following articles will help you out:
How to access VRM monitor from BVMS Configuration Client?
How to collect VRM logs with VRM Monitor (v3.82/ v3.83)?
Screenshot of the Dashboard of the VRM
for VRM version till 3.81 - contact support to receive BVIP Log collector tool and use it to collect VRM logs
Movie showing the display artefacts can be helpful
... View more
What is the difference between RAID 5, RAID 5 plus a Hot Spare and RAID 6?
The RAID combines two or more physical drives into a logical unit presented as a single hard drive to the operating system. There are currently six basic RAID levels: RAID 0, RAID 1, RAID 0+1, RAID 1+0, RAID 3, RAID 4, RAID 5 and RAID 6.
The scope of this article is to provide basic information for the levels RAID 5 and RAID 6 and to compare them from point of view of performance and security.
Hot spare is a drive that acts as a stand by drive in RAID 1, RAID 5 or RAID 6 volume. It is fully functional drive that contains no data and is not used during normal operation. If a drive from the volume fails, the controller reconstructs the data from the failed drive to the hot spare drive.
A RAID 5 array is designed to protect against the failure of a single disk within the array. Because of the way that RAID 5 works, the total capacity of one disk is lost to overhead. If, for example, a RAID 5 array contained five 10TB disks, then the array’s usable capacity would be 40TB. Requires a minimum of three disk drives. Data is striped across multiple drives with distributed parity. Offers fault tolerance by using parity information to reconstruct data in the event of a single drive failure. Good performance for both read and write operations. Capacity utilization is high since only one drive's worth of space is used for parity. However, RAID 5 does not protect against multiple drive failures. If a second drive fails before the first failed drive is replaced and rebuilt, data loss will occur.
A RAID 5 (with Hot Spare disk) array can be configured to treat one of the disks as a hot spare. Then one of the disks is reserved as a replacement in the event that a disk fails. For the above example with five 10TB disks, this would decrease the example array’s usable capacity to 30TB. Similar to RAID 5 but includes an additional drive designated as a hot spare. The hot spare remains inactive until one of the drives in the RAID array fails. When a drive fails, the hot spare automatically takes its place, rebuilding the data without manual intervention. Provides improved fault tolerance by reducing the risk of data loss during drive rebuilds. However, it still has the same limitations as RAID 5 when it comes to protecting against multiple drive failures.
A RAID 6 array is designed to protect against two simultaneous disk failures. However, the price for this extra protection is that two disks' worth of capacity is lost to overhead. As such, a RAID 6 array made up of five 10TB disks would have a usable capacity of 30TB because 20 TB is lost to overhead. Requires a minimum of four disk drives. Data is striped across multiple drives with double distributed parity. Offers increased fault tolerance by using two sets of parity information to tolerate the simultaneous failure of up to two drives. Can withstand multiple drive failures without data loss. However, RAID 6 typically has lower write performance compared to RAID 5 due to the additional parity calculations required. It also has a higher capacity overhead compared to RAID 5 since it uses two drives' worth of space for parity.
The performance during Normal Operation is measured in IOPS (Input/output operations per second) and as a sum for all the disks (excluding the Hot Spares and decreased for writing parity data) in the array. As a rule of the thumb, the higher the overhead associated with writing parity data (in the above example RAID 5 with Hot Spare causes the same overhead like RAID 6) the lower the IOPS.
The reason for implementing RAID arrays is to secure the data. The level of protection does not directly correlate with the overhead. From the above example both RAID 5 with Hot Spare and RAID 6 have same capacity, but offer different level of protection. In case of failure of RAID 5 array with Hot Spare, the Hot Spare is activated and the rebuild process start immediately.
The system can recover from a single disk failure and during the recovery, process is vulnerable to second disk failure.
Therefore, RAID 5 and RAID 5 with Hot Spare disk offer the same level of protection – single disk failure.
In contrast, if a disk fails at RAID 6 array, the recovery will start only after the faulty disk is replaced manually. However, if during the recovery process second disk fails, the RAID 6 array will stay functional.
In summary, RAID 5 provides basic fault tolerance with good performance, but it cannot protect against multiple drive failures. RAID 5 with a hot spare improves fault tolerance by automatically replacing failed drives, but it still has the same limitation regarding multiple drive failures. RAID 6 offers a higher level of fault tolerance by using double parity, allowing for the simultaneous failure of up to two drives without data loss. However, it has higher write overhead and requires more drives for implementation compared to RAID 5.
... View more