The purpose of this document is to simplify some of the terms, descriptions, and mechanisms of the GStreamer core. It will, initially, serve as a foundation to help model and test the GStreamer implementation in the RDK/HAL system.
This document describe the details of the following,
- Adheres to GObject (Glib 2.0)
- Uses signals and object properties
- Has one specific function (read, decode, ...)
- Has two Pads:
- source (output)
- sink (input)
- GStreamer core views elements as blocks of bytes
- Linked or chained elements create a pipeline that performs a specific task
Is defined by two properties:
- Downstream : src element to sink element
- Upstream: sink element to src element
Actual media data.
A simple buffer consists of:
Information on elements or pipeline.
A message consist of:
Request for a specific stream property related to progress tracking.
These 3 types of elements create a simple GST-Pipeline.
Pipelining is an implementation technique whereby multiple instructions are overlapped in execution; it takes advantage of parallelism that exists among the actions needed to execute an instruction.