videoWatchdog: A C++ repository from antoinehng

#VideoWatchdog

VideoWatchdog is a software developed for screen monitoring and video processing using an IntensityPro acquisition card. The main idea is to connect a STB as video input and analyze its data, creating events for state changes and implementing other forms of data acquisition to automate the testing process.

The project was written in C++ and is divided in the following components:

Main thread: implemented in ./IntensityAcquisition.cpp, this file is responsible for generating real time video output using the data acquired from IntensityPro and presenting it on desktop.
blackmagic/: This folder contains files used for communicating with IntensityPro drivers and acquiring video and audio, it also contains a SDK for developing software for Blackmagic products.
recognition/: This folder contains some files specialized in image processing, and implement template matching and level monitoring for OpenCV material objects (cv::Mat).
ServerInstance/: This folder has source code related to the REST Server implementation and declaration of routes used.
watchdog/: Implementation of an watchdog that monitors all video output and reports events.

You can find installation instructions here: Installation instructions.

##Video Watchdog

###Options:

-no-video : video display is not shown, server will be executed normally
-res X Y  : set resolution of window
-720p : set resolution of input to 720p instead of 1080i

##REST API

The server exposes an REST API on page 8080 with the following routes:

Route	Function	Method	Arguments
/status	Get status of STB	POST	{"timeAnalysis":1000}
/image	Get image in binary format	GET	None
/imageb64	Get image in base 64	GET	None
/getScreenEvent	Search for events in video input	POST	{"eventType": ["LIVE", "FREEZE", "BLACK"],"timeAnalysis":600000, "timeEvent":5000,"count":true}
/checkForImage	Check if an image is being shown in the screen	POST	{"imageURL":"http://image.to.search/img.png","returnImage":true}
/text	Executes an OCR text recognition on the current STB output and returns the text being shown	GET	None

The complete list of routes can be found in the Wiki: REST Server

Two other routes were created to control the watchdog, the first one is /watchdog that accepts two arguments via POST.

To start looking for events of at least 1.5s and of types: BLACK, FREEZE, LIVE and FREEZE_NO_AUDIO:

{"start":true, "tevent":1500, "eventType":["BLACK","FREEZE","LIVE","FREEZE_NO_AUDIO"]}

And then you can stop the watchdog sending another POST message to the same route (this will return the list of observed events):

{"stop":true}

There is also an second route that allows you to view wich elements were observed while the watchdog is still running: You can do a get request on /report, both this request and a command to stop the watchdog have the same output format:

{
  "incidents": [
    {
      "duration_ms": 1900,
      "event": "Freeze",
      "isIncidentFinished": true,
      "videoName": "http://10.0.1.19/logvideo_0_live_g3p.avi",
      "when": "17.11.2015 15:02:50"
    },
    {
      "duration_ms": 9900,
      "event": "Freeze",
      "isIncidentFinished": false,
      "videoName": "http://10.0.1.19/logvideo_575_live_ij6.avi",
      "when": "17.11.2015 16:38:54"
    }
  ],
  "message": "Watchdog is running",
  "startTime": "17.11.2015 15:02:49"
}

Wiki

You can find more information about the project at: videoWatchdog Wiki

antoinehng/videoWatchdog

Wiki