H.264 Motion Vector Extractor - Getting Started - Evaluating H.264 Motion Vector Extractor

H.264 Motion Vector Extractor
H.264 Motion Vector Extractor Basics
Getting Started
Evaluating H.264 Motion Vector Extractor Getting the Code Building H.264 Motion Vector Extractor
User Guide
Preparing the buffer Retrieving the motion information Error codes
Examples
File motion vector extraction
Performance
x86 i.MX6 i.MX8
Contact Us

Requesting the Evaluation Binary

RidgeRun can provide you with an evaluation binary of the H.264 Motion Vector Extractor library to help you test it, in order to request an evaluation binary for a specific architecture, please contact us providing the following information:

• Platform (e.g.: i.MX6, i.MX8, Snapdragon, etc...). The more info the better!
• Input resolutions and frame rates
• Use case, if possible (e.g.: drone, car, robot...)
• Latency requirements

Features of the Evaluation

To help you test our H.264 Motion Vector Extractor library, RidgeRun can provide an evaluation version of the library.

The following table summarizes the features available in both the professional and evaluation version of the element.

Table 1. Features provided in the evaluation version

Feature	Professional	Evaluation
H.264 bytestream motion vector extraction	Y	Y
H.264 AVC motion vector extraction	Y	Y
Unlimited Processing Time	Y	N (1)
Source Code	Y	N

(1) The evaluation version will limit the processing to 5 minutes.

Evaluating the library

Dependencies

First, make sure the dependencies are fulfilled:

sudo apt install libgstreamer1.0-dev gstreamer1.0-plugins-base gstreamer1.0-plugins-bad

Eval Binary Structure

The provided H.264 Motion Vector Extractor eval version tarball must have the following structure:

usr/
├── bin
│   └── vectorextractor_example
├── include
│   └── vectorextractor
│       └── rr
│           ├── common
│           │   └── runtimeerror.hpp
│           └── vectorextractor
│               ├── expgolombdecoder.hpp
│               ├── macroblockparser.hpp
│               ├── rbsp.hpp
│               ├── slicedataparser.hpp
│               └── vectorextractor.hpp
└── lib
    └── x86_64-linux-gnu
        ├── libvectorextractor.so
        └── pkgconfig
            └── vectorextractor.pc

Eval Binary Installation

To use the binary provided by RidgeRun, export the location of the evaluation binary libraries in your environment.

export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${PATH_TO_EVALUATION_BINARY}/usr/lib/x86_64-linux-gnu/

where PATH_TO_EVALUATION_BINARY is set as the location in your file system where you have stored the binary provided by RidgeRun.

Eval Binary Testing

Finally, to test if the library is working you can use the included example.

${PATH_TO_EVALUATION_BINARY}/usr/bin/vectorextractor_example <input video>

You can find more information about the example in File motion vector extraction.