IREX Changelog

Release 4.40

IREX 4.40 Changelog

New Features

4.40.0

  1. The user menu now includes a Collaboration section that contains the Resource Groups page. Resource groups can be created on that page, and one or more user groups can be granted access to them. The User Groups page also has a "Resource Groups" tab to grant that access. On the Cameras, Events, and Plans pages, and in Alarm Monitor filter settings, video sources can now be filtered by resource group.
  2. The "Cameras and places" filter now has an "Addresses" tab for searching cameras by address. The separate Locations filter was removed, and the "Locations" tab was removed from the Settings page. On the Logbook page, the additional filters still include a "Locations" tab, so earlier logbook entries for actions on locations can still be searched.
  3. The platform can now grant user groups access to layouts. Access is configured when a layout is created, and on the "Layouts" tab of the User Groups and Resource Groups pages. Access to existing layouts was automatically granted to the user groups that the layout creator belongs to.
  4. The platform can now capture "Overtaking" traffic violations. The "Wrong way" violation type was renamed to "Opposite lane". To capture these violations on a road object, the "Opposite lane / Overtaking" control is turned on and violation control rules are set.
  5. The platform can now play back the archive stored on cameras connected through ONVIF devices. This is enabled with the "Enable access to the archive on the camera" option in the forms for creating and editing an ONVIF device. The "Add cameras" form for an ONVIF device also has the "Use only for viewing archive on the camera" option. Cameras created this way are disabled, but they retain access to the archive on the camera. In the player, the video source is switched using the "Server" and "Camera archive" values of the "Video source" option on the toolbar. On the "Cameras" tab of the Settings page, the "Connection protocol" filter now includes the "Camera archive enabled" and "Camera archive disabled" values.
  6. Case ID is now required to open the Logbook page and for every search on that page. The entered value is stored in the "Search in logbook" entry.
  7. Alarm Monitor filter settings were expanded. Multiple separate filters can now be added to a single monitor. Each filter is created with its own name and set of criteria. Filter criteria can be checked with the "Preview" option before the filter is applied, to see which alarms will appear on the monitor and at what rate.
  8. A Traffic violations category was added to Alarm Monitor filter settings. Filters in this category send alarms for captured traffic violations to the monitor separately from other video analytics events.
  9. On the "Alarm Monitors" tab of the Settings page, a side panel with detailed monitor information was added. The panel opens when a monitor is selected in the list.
  10. On the "Cameras" tab of the Settings page and on the Cameras page, the "Video quality issues" camera status was renamed to "Video issues". Hovering over the "Video issues" status icon shows the issue type, for example, "Scene too bright" or "Low frame rate". The Status filter now also supports search by issue type.
  11. In the ObjectTrack module, the settings for different tracked objects were redesigned. The "View" and "Object type" parameters, with the "People", "Pedestrians", "Vehicles", and "Abandoned items" options, were replaced with the "Object tracking types" block. In that block, the "People", "Vehicles", and "Abandoned items" object types are turned on separately, each with its own settings. For the "People" object type, one of the following tracking modes can be selected: "People tracking", "People tracking (top view)", "Safety gear detection", "Pedestrian tracking", and "Perimeter human detection". The "Perimeter human detection" mode was added to capture people at a secured site, including during unusual movement such as crawling or rolling.
  12. In the forms for creating and editing a person list, the minimum value of the "Similarity" scale was raised from 45% to 55%.

Technical Improvements

4.40.0

  1. The platform now supports H.265 video streams. Playback is available in the latest version of Google Chrome. The graphics card must support H.265 decoding.
  2. For traffic violations, the full video frame before a line crossing is now taken at a distance of three license-plate widths from that line. Previously the frame was taken at a distance calculated from the vehicle width. Using license-plate width avoids cases where the distance for a large vehicle was too great and the vehicle was not in the frame.
  3. In the CarTrack Pro module, video processing on the CPU is now faster.
  4. In API requests that search logbook entries, the parameters for traffic-violation priority, biometric terminal ID and name, and the date and time of event and violation searches were given unique names.
  5. On the Cameras page, in "Show Cards" mode, the camera-card layout was improved. The camera name and status icon were moved into the card header. For cameras with the "Disabled" and "Signal lost" statuses, separate default system images now appear in place of the video frame.
  6. Video analytics modules that run on GPU can now process several video streams on one graphics card, with the card's resources split between the streams.
  7. The internal structure of the UI components for filters, the player, and the Sigur and Netping device integration pages was refactored.
  8. Unit tests now run faster and more reliably.
  9. In the Apache Superset integration, technical parameters that are not used in reports were removed from the datasets, such as table-row identifiers and source table names.
  10. In the FaceTrack Pro module, CPU usage was reduced when matching detected faces against person lists.

Resolved Issues

4.40.0

  1. On the Logbook page, the "Search domain" parameter is no longer shown in "Search for events" entries created by an event search in the player, on the Route page, or in Alarm Monitor filter settings.
  2. On the Logbook page, in "Search in logbook" entries created by a search on the "Biometric terminal ID" and "Biometric terminal name" parameters, those parameters now show correctly instead of "Channel ID" and "Channel".
  3. On the Logbook page, in "Search in logbook" entries created by a search on the "Violation time" parameter, that parameter now shows correctly instead of "Event time", and the "Event types" parameter with the "Search for traffic violation" value is no longer shown.
  4. On the Logbook page, in "Video analysis start" and "Video analysis interrupted" entries, the "Case ID" parameter now appears.
  5. On the Logbook page, in "Search for traffic violation" entries, the "Violation ID" parameter now appears. On the "Violations" tab of the additional filters, the "Violation ID" parameter was added.
  6. On the Logbook page, in "Search in logbook" entries created by a search on the "Human silhouette photo loaded" parameter, that parameter now shows correctly instead of "Search domain".
  7. On the Logbook page, "Search for events" entries created by a silhouette search on the "Additional Events" tab of the Events page now appear.
  8. In the Logbook CSV report, the "Details" column no longer shows technical parameters that are not in the entry detail card on the Logbook page.
  9. In the Logbook CSV report, the "Details" column for a "Vehicle updated" entry now shows the "Photo or pattern: yes" parameter.
  10. In the CarTrack Pro module, a "Motion in region" event no longer ends early when a vehicle license plate is briefly obscured.
  11. In the CarTrack Pro module, the "Traffic Objects" tab is no longer available in the "Track vehicle" and "Recognize plate" modes.
  12. The TamperTrack module now works more reliably when it is the only detector turned on for a camera and only the "View obstructed" option is enabled.
  13. When a request removes a user group’s access to all resources of a selected type, the platform now checks that the user has rights to manage those resources.
  14. On the User Groups page, access to biometric terminals and Sigur devices is now granted when access is given to all video sources at once.
  15. In the FaceTrack Pro module, with the "Run on GPU" option turned on, "Match" events are now generated.
  16. The camera name is now displayed identically on the Camera settings page and the Video Analytics settings page, and the list in the option for switching between those pages has a fixed width. On the Video Analytics settings page, in the options menu, a separator was added between camera actions and the "Export Camera settings" and "Import Camera settings" options.
  17. In the Alarm Monitor "Work schedule" window, the spacing between the day or date name and the time intervals, and between the intervals themselves, was reduced.
  18. The FaceTrack Pro module now works more reliably.
  19. In the player, the archive recording timeline no longer disappears after a camera configuration change.