Lines Matching full:frame

10 between processed frames. This means that each frame is decoded independently
30 frame may be the result of several decode requests (for instance, H.264 streams
31 with multiple slices per frame). Decoders that support such formats must also
110          frame buffer resolution for the decoded frames.
119          as per standard semantics; matching frame buffer format.
162          frame buffer resolution of the decoded stream; typically unchanged from
231 For each frame, the client is responsible for submitting at least one request to
236   corresponds to one frame worth of encoded data, but some formats may allow (or
246 If there is a possibility that the decoded frame will require one or more
253 A typical frame would thus be decoded using the following sequence:
267           number of bytes taken by the encoded data frame in the buffer.
272           to produce a fully decoded frame, then
279           must be set to a unique value per frame. This value will be propagated
280           into the decoded frame's buffer and can also be used to use this frame
282           frame, then the timestamps of all the ``OUTPUT`` buffers for a given
283           frame must be identical. If the timestamp changes, then the currently
301           a frame.
329 carrying the ``V4L2_BUF_FLAG_ERROR`` flag. If a decoded reference frame has an
341 A dequeued capture buffer can also be used as the reference frame of another
344 A frame is specified as reference by converting its timestamp into nanoseconds,
347 conversion. The timestamp of a frame can be used to reference it as soon as all
350 A decoded buffer containing a reference frame must not be reused as a decoding
358 1. All the requests for frames affected by the reference frame have been
366 can e.g. close the DMABUF file descriptors of reference frame buffers if it
396    last frame is not available on the ``CAPTURE`` queue. In this case, a
419 last frame is not available on the ``CAPTURE`` queue. In this case, a