the buffer is live data and should be discarded in the PAUSED state.
the buffer contains data that should be dropped because it will be clipped against the segment boundaries or because it does not contain data that should be shown to the user.
the buffer marks a data discontinuity in the stream. This typically occurs after a seek or a dropped buffer from a live or network source.
the buffer timestamps might have a discontinuity and this buffer is a good point to resynchronize.
the buffer data is corrupted.
the buffer contains a media specific marker. for video this is typically the end of a frame boundary, for audio this is usually the start of a talkspurt.
the buffer contains header information that is needed to decode the following data.
the buffer has been created to fill a gap in the stream and contains media neutral data (elements can switch to optimized code path that ignores the buffer content).
the buffer can be dropped without breaking the stream, for example to reduce bandwidth.
this unit cannot be decoded independently.
this flag is set when memory of the buffer is added/removed
Elements which write to disk or permanent storage should ensure the data is synced after writing the contents of this buffer. (Since 1.6)
This buffer is important and should not be dropped. This can be used to mark important buffers, e.g. to flag RTP packets carrying keyframes or codec setup data for RTP Forward Error Correction purposes, or to prevent still video frames from being dropped by elements due to QoS. (Since 1.14)
additional media specific flags can be added starting from this flag.