H.264 Motion Vector Extractor - User Guide - Error codes
 | H.264 Motion Vector Extractor RidgeRun documentation is currently under development. |
| H.264 Motion Vector Extractor | |
|---|---|
 | |
| H.264 Motion Vector Extractor Basics | |
|
|
|
| Getting Started | |
|
|
|
| User Guide | |
|
|
|
| Examples | |
|
|
|
| Performance | |
|
|
|
| Contact Us |
This page provides a basic description of the RuntimeError class and its different error codes.
RuntimeError
Every method in the H.264 Motion Vector Extractor library other than getters and setters will return a rr::vectorextractor::RuntimeError object. This object contains two attributes: an error code and its message.
Error codes
They form part of the Codes enum and are the following:
- EOk: everything is ok. This is the default code when the process finishes without any error.
- WrongApiUsage: signals an invalid use of the library's API.
- NotImplemented: indicates an unimplemented section of the code was reached. This can indicate your stream contains a special feature of the H.264 standard.
- NullParameter: a required parameter was passed as null.
- FileError: there was a problem handling a file.
- MemoryError: allocation or memory management error.
- UnknownError: an unknown error has occurred.
- StillProcessing: more data is required to get valid outputs. This will happen if the input buffer doesn't contain an entire frame.
