This method allow setting up the object from the currently configured format on the
device. This is useful for M2M element where input data decides the format that will
be set on capture side.

https://bugzilla.gnome.org/show_bug.cgi?id=720568

https://bugzilla.gnome.org/show_bug.cgi?id=720568

Julien Isorce authored Dec 31, 2013 and Nicolas Dufresne committed Jan 10, 2014

https://bugzilla.gnome.org/show_bug.cgi?id=720568

https://bugzilla.gnome.org/show_bug.cgi?id=720568

The number of plane, and the stride does not represent a capability change. Same caps
can have different stride from the default GstVideoInfo and the number of planes will
never change for 1 format.

https://bugzilla.gnome.org/show_bug.cgi?id=720568

Now that we have a stride array, we should extrapolate only when
eeded (non multi-planar buffer).

https://bugzilla.gnome.org/show_bug.cgi?id=720568

https://bugzilla.gnome.org/show_bug.cgi?id=720568

It makes the gst_v4l2_object_set_format() slightly simplier and will make that
logic reusable. Note that gst_v4l2_object_has_mplane() will always return the
same value for one device. There is no need to check against the caps as this
has already been done by _open.

https://bugzilla.gnome.org/show_bug.cgi?id=720568

https://bugzilla.gnome.org/show_bug.cgi?id=720568

VIDIOC_REQBUFS allocates buffer, it has no place inside set_config. Also, some driver do
no allow multiple calls to this ioctl.

https://bugzilla.gnome.org/show_bug.cgi?id=720568

We set the dimensions just in case but don't validate them
afterwards. For some codecs the dimensions are *not* in the
bitstream, IIRC VC1 in ASF mode for example.

https://bugzilla.gnome.org/show_bug.cgi?id=720568

Most M2M have undefined behaviour initially when VIDIOC_G_FMT is called.

https://bugzilla.gnome.org/show_bug.cgi?id=720568

https://bugzilla.gnome.org/show_bug.cgi?id=720568

This will duplicated the FD from another object and copy over the probed result.

https://bugzilla.gnome.org/show_bug.cgi?id=720568

This is to allow adding a second io-mode property on M2M device like decoder so
input and output can be controlled separatly.

https://bugzilla.gnome.org/show_bug.cgi?id=720568

Nicolas Dufresne authored Jun 04, 2013 and Nicolas Dufresne committed Jan 10, 2014

This way we can activate deactivate those quirks all at once at one
place.

https://bugzilla.gnome.org/show_bug.cgi?id=720568

Nicolas Dufresne authored Jun 04, 2013 and Nicolas Dufresne committed Jan 10, 2014

V4L2_PIX_FMT_H264 is documentated as byte-stream (with start code). The ensure proper
negotiation with element like h264parse.

https://bugzilla.gnome.org/show_bug.cgi?id=720568

This is need to correctly expose capabilities on specialized devices
like decoders and encoders.

https://bugzilla.gnome.org/show_bug.cgi?id=720568

The need for rewriting apparently is obsolete 0.10 leftover.
We now have caps for subtitles when we create the headers,
so we always write the correct data in the first place.

Coverity CID 1151680

This avoids issues with writing dummy data first, then having
to come back and write correct data later. Doing so prevents
the muxed stream from being actually streamable.

https://bugzilla.gnome.org/show_bug.cgi?id=712134

Otherwise MAC_OS_X_VERSION_MIN_REQUIRED might not be defined

Mov spec says it uses a pascal style string, while isomedia uses
a null terminated one. Store the current atoms flavor into the HDLR
to be able to generate the correct output.

https://bugzilla.gnome.org/show_bug.cgi?id=705982

This reverts commit b3aa8755.

We are already using the running-time because they were placed on the
buffers with gst_collect_pads_clip_running_time(). Arguably it would be
better to not modify the incomming buffers but collectpads seems to want
to use absolute timestamps from the buffers for finding the best buffer
(this can be changed with a custom compare function..).

https://bugzilla.gnome.org/show_bug.cgi?id=721245

remove list of decoders, which are already handled by the list of elements.

https://bugzilla.gnome.org/show_bug.cgi?id=719938

https://bugzilla.gnome.org/show_bug.cgi?id=720995

Use the new method to get the media type of a transport.

This way one failure won't shadow the other test and also if one fails we get
better disgnostics through the test-name.

We do have adtl and cue parse as part of toc handling alreday. The fmt code is a left over from <0.10 times.

Always print a warning with the tag and if possible do a memdump.

We can get maker, model and capture date from this chunk.
Fixes #636143

This chunk is avi specific, no need to expose this as public api.