Membrane Core v0.2.2 Membrane.Element.Base.Sink behaviour View Source

Module defining behaviour for sinks - elements consuming data.

Behaviours for filters are specified, besides this place, in modules Membrane.Element.Base.Mixin.CommonBehaviour, and Membrane.Element.Base.Mixin.SinkBehaviour.

Sink elements can define only input pads. Job of a usual sink is to receive some data on such pad and consume it (write to a soundcard, send through TCP etc.). If the pad works in pull mode, which is the most common case, then element is also responsible for requesting demands when it is able and willing to consume data (for more details, see Membrane.Element.Action.demand_t/0). Sinks, like all elements, can of course have multiple pads if needed to provide more complex solutions.

Link to this section Summary

Callbacks

Callback that is called when buffer should be written by the sink. In contrast to handle_write_list/4, it is passed only a single buffer

Callback that is called when buffer should be written by the sink

Link to this section Callbacks

Callback that is called when buffer should be written by the sink. In contrast to handle_write_list/4, it is passed only a single buffer.

Called by default implementation of handle_write_list/4.

Callback that is called when buffer should be written by the sink.

For pads in pull mode it is called when buffers have been demanded (by returning :demand action from any callback).

For pads in push mode it is invoked when buffers arrive.