View Source Membrane.Element.WithOutputPads behaviour (Membrane Core v0.10.2)
Module defining behaviour for source and filter elements.
When used declares behaviour implementation, provides default callback definitions and imports macros.
For more information on implementing elements, see Membrane.Element.Base.
Link to this section Summary
Callbacks
Callback called when buffers should be emitted by a source, filter or endpoint.
Functions
Macro that defines output pad for the element.
Link to this section Callbacks
@callback handle_demand( pad :: Membrane.Pad.ref_t(), size :: non_neg_integer(), unit :: Membrane.Buffer.Metric.unit_t(), context :: Membrane.Element.CallbackContext.Demand.t(), state :: Membrane.Element.state_t() ) :: Membrane.Element.Base.callback_return_t()
Callback called when buffers should be emitted by a source, filter or endpoint.
It is called only for output pads in the pull mode, as in their case demand is triggered by the input pad of the subsequent element.
In sources and endpoint, appropriate amount of data should be sent here.
In filters, this callback should usually return :demand action with
size sufficient for supplying incoming demand. This will result in calling
Membrane.Filter.handle_process_list/4, which is to supply
the demand.
If a source or an endpoint is unable to produce enough buffers, or a filter
underestimated returned demand, the :redemand action should be used (see
Membrane.Element.Action.redemand_t/0).
Link to this section Functions
Macro that defines output pad for the element.
Allows to use one_of/1 and range/2 functions from Membrane.Caps.Matcher
without module prefix.
It automatically generates documentation from the given definition and adds compile-time caps specs validation.
The type Membrane.Pad.output_spec_t/0 describes how the definition of pads should look.