UVAP
  • Key Features
  • Feature Demos
  • Installation
  • Developer Guide
  • Operation Guide
  • Tutorials
  • Help

›Microservice Configuration

Developer Guide

  • Architecture
  • Data Model
  • Microservices

    • Multi-Graph Runner
    • Tracker
    • Pass Detector
    • Reidentifier
    • Feature Vector Clustering
    • Detection Filter
    • Video Capture

    Microservice Configuration

    • Microservice Superconfiguration
    • Configuring Multi-Graph Runner
    • Configuring Tracker
    • Configuring Pass Detector
    • Configuring Reidentifier
    • Configuring Feature Vector Clustering
    • Configuring Detection Filter
    • Configuring Video Capture

    Tools

    • Stream Configurator UI Guide
    • Configuring Detection Filter Areas
    • Configuring Passlines
  • Extending UVAP

Configuring Video Capture

This microservice does not require GPU resources.

The Video Capture microservice processes video streams or files and writes the result to its target topic.

Environment Variables

  • VC_PROPERTY_FILE_PATHS: property files path list.

Video Capture reads its configuration from the property files in the above list during startup. See the list of properties below.

Properties

The values of properties with the .file extension are the paths of the .json files, while the values of properties with the .data extension are the .json configurations themselves.

Attention! Setting .data and .file properties are exclusive to each other, meaning setting both ultinous.service.vc.ms.config.data and ultinous.service.vc.ms.config.file results in an error.

ultinous.service.vc.auth.defs.data

Propertyultinous.service.vc.auth.defs.data
DescriptionAuthentication definition data in one-liner JSON format corresponding to the definitions described in Superconfig Authentication Definitions.
RequiredOptional
NoteRequired if ID based authentication is used in ultinous.service.vc.ms.config.*

ultinous.service.vc.auth.defs.file

Propertyultinous.service.vc.auth.defs.file
DescriptionAuthentication definition file path. Content of the file should be in JSON format described described in Superconfig Authentication Definitions.
RequiredOptional
NoteRequired if ID based authentication is used in ultinous.service.vc.ms.config.*

ultinous.service.vc.monitoring.port

Propertyultinous.service.vc.monitoring.port
DescriptionMonitoring server port.
RequiredRequired

ultinous.service.vc.monitoring.threads

Propertyultinous.service.vc.monitoring.threads
DescriptionMonitoring server thread pool size.
RequiredOptional

ultinous.service.vc.ms.config.data

Propertyultinous.service.vc.ms.config.data
DescriptionVideo Capture microservice configuration, and optionally authentication and functional configuration. Content must be in one-liner JSON format described in Superconfig Topic Definitions.
RequiredRequired

ultinous.service.vc.ms.config.file

Propertyultinous.service.vc.ms.config.file
DescriptionVideo Capture microservice configuration, and optionally authentication and functional configuration. Content must be the path to the JSON format configuration file.
RequiredRequired

ultinous.service.vc.config.data

Propertyultinous.service.vc.config.data
DescriptionFunctional configuration.
RequiredOptional
NoteRequired if config_data is not defined in ultinous.service.vc.ms.config.*

ultinous.service.vc.config.file

Propertyultinous.service.vc.config.file
DescriptionFunctional configuration.
RequiredOptional
NoteRequired if config_data is not defined in ultinous.service.vc.ms.config.*

Microservice Configuration

Configuration records are separated into the following three values:

  • VideoCaptureMSConfig specified in Kafka Superconfiguration Proto
  • VideoCaptureConfigRecord specified in Kafka Configuration Proto
  • AuthDef specified in Kafka Superconfiguration Proto

Example of a VideoCaptureMSConfig from Kafka

This configuration provides the details of connecting the microservice to Kafka. The example below can be the contents of a file given as the property value for ultinous.service.vc.ms.config.file.

{
  "targets": [
     {
       "broker_list": "127.0.0.1:6494",
       "name": "local_camera.vc.Packet.upw"
     },
     {
       "broker_list": "127.0.0.1:6494",
       "name": "network_camera.vc.Packet.upw"
     }
  ]
}

In this example, two targets are defined with broker list and topic name, meaning that Video Capture will process two input streams and write the results in these topics.

The config_data field is not given in this example, which means that the configuration for the microservice functionality is given separately, see Example of a VideoCaptureConfigRecord from Kafka.

Example of a VideoCaptureConfigRecord from Kafka

This configuration provides other details of themicroservice, e.g. the input streams. The example below can be the contents of a file given as the property value for ultinous.service.vc.config.file.

{
 "streams": [
   {
     "url":"/dev/video0"
   },
   {
     "url":"rtsp://192.168.0.1/"
   }
 ]
}

In this example, two input video streams are saved: one is from the local camera, and the other is a network stream.

← Configuring Detection FilterStream Configurator UI Guide →
  • Environment Variables
  • Properties
    • ultinous.service.vc.auth.defs.data
    • ultinous.service.vc.auth.defs.file
    • ultinous.service.vc.monitoring.port
    • ultinous.service.vc.monitoring.threads
    • ultinous.service.vc.ms.config.data
    • ultinous.service.vc.ms.config.file
    • ultinous.service.vc.config.data
    • ultinous.service.vc.config.file
  • Microservice Configuration
    • Example of a VideoCaptureMSConfig from Kafka
    • Example of a VideoCaptureConfigRecord from Kafka
Help
UVAP License TermsGlossaryTypographic ConventionsTrademark InformationSupport
Navigation
Key FeaturesFeature DemosInstallationDeveloper GuideTutorialsHelp
Community
GitHubFacebookLinkedInTwitterYouTube
Ultinous
Copyright © 2019-2020 Ultinous