H.264 Motion Vector Extractor - Performance - x86

🚧 Documentation is under development

The H.264 Motion Vector Extractor guide is currently under active development. Some sections may be incomplete or change without notice.

Questions? Contact RidgeRun or email to support@ridgerun.com.

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

This section contains the performance metrics for the library running on the x86 platform.

Intel Core i7-8750H @ 2.20 Ghz, 16 GB RAM

Resolution	CPU %	Memory (MBs)	FPS	Latency (ms)
1920x1080
3840x2160

H.264 Motion Vector Extractor vs FFmpeg

The following tests were performed with an unusual 3840x2560 resolution and are only intended to show a relative comparison between RidgeRun's solution and FFmpeg for the purpose of extracting motion vectors. For performance metrics please refer to the previous table.

Graph of latency per frame for both the FFmpeg and RidgeRun's implementation of a motion vector extractor.

Graph of CPU usage for both the FFmpeg and RidgeRun's implementation of a motion vector extractor, along with a baseline GStreamer application.

Graph of memory usage for both the FFmpeg and RidgeRun's implementation of a motion vector extractor, along with a baseline GStreamer application.