Benjamin Gaignard authored Dec 18, 2013 and Nicolas Dufresne committed Feb 25, 2014

For each videoCdevice probe it input/output capabilities
if it match with video decoder requirement register a new element.

Signed-off-by: Benjamin Gaignard <benjamin.gaignard@linaro.org>

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

Decoders or other devices that expose a minimum buffers required produce
an first output. We use this information to calculate latency.

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

Implement an element that can driver V4L2 M2M decoder device.

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

This fixes an issue with gst-rtsp-server where no sps and pps are
sent for the first intra frame, because the payloader starts working
already when receiving DESCRIBE but there is no transports so it tries
to send sps and pps, but that fails with a FLUSHING flow. But the time
for last sent sps and pps would still be set, so when PLAY arrives and
the first intra frame is to be sent there is no sps and pps sent due to
that time since last sps pps is less than spspps_interval.

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

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

In the case where we have no suitable candidate we post a warning and plug a
fake-element. Do the same when non of the candidate work.

This is more consistent and plugin the fakesink as a fallback is probably
helpful for running unit tests without requiring hardware src/sink elements.

Fixes #722981

... at least if one tries hard enough using extra-controls property.

The code fails to compile without currently, see
https://bugzilla.gnome.org/show_bug.cgi?id=723446

It's better to disable it instead of failing compilation
until this is fixed properly.

Add log handlers for jack that write to the gst debug log. This avoids spamming
the console when e.g. using autoaudiosink, having the jack elements installed,
but not running jack.

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

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

We correctly indicate the field ordering on interlaced buffers, but fail to
flag them as containing interlaced video, which we need to do here because
we signal interlace-mode=mixed in our caps. This means that downstream
elements (like vaapipostproc from gstreamer-vaapi) don't recognise these
buffers as in need of deinterlacing.

Fix this by setting the interlaced flag on all interlaced buffers.

Signed-off-by: Simon Farnsworth <simon.farnsworth@onelan.co.uk>

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

Adds two extra checks:

- Sampling frequency on header can't be 15.
- Frame size should be at least 9 or 7, depending
  on whether CRC protection is present.

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

We need at least 6 bytes to pass over to _get_frame_len()
but we were just checking for a minimum of 2 bytes for the
syncword.

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

previously autovideosrc did not have a sync property and v4l2src has none either.

This makes the actual elements super simple. We're using the ELEMENT_FLAG to
configure source/sink and a string for the Audio/Video type.

Add support for a new property: tls-database. If the property is set,
the certificate database will be given to the rtsp connection if TLS
protocol is being used. If the server certificate can't be verified with
the default database, this additional database will be used.

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

The function to generate the pretty names is basically the same. Use one and add
a parameter.

Add fake audio/video sinks. Previously running the test might be flaky due to
the use of real elements (hardware in use), which we don't want to test here.
Add two more tests that check that the fakes are chosen.

Commit 46fd12ae introduced connection
recovery. But when server does not specify content-size,
souphttpsrc tries to reconnect even after regular end of stream.
Http server replies  with SOUP_STATUS_REQUESTED_RANGE_NOT_SATISFIABLE
but souphttpsrc still emits error instead of EOS.

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



Signed-off-by: Branislav Katreniak <bkatreniak@nuvotechnologies.com>

Use a shared helper for both tests. It turns out that the valgrind variant is
fine (maybe due to picking up pulsesink though).

Remove the obsolete version check and use the ignore macro for the disabled test.

It turns out that the change in gtk-doc-1.20 which wraps the |[]| content in
CDATA break xi:inlcude examples. As in a whole jhbuild checkout these where
the only 4, we're fixing them instead.

This fixes doc warnings.

Don't use docbook unless needed. Also stip other docbook tags in the the files we fix.

The "goto unlock" is wrong as in this code path we haven't take the lock yet.
Fixes #724619

Previous versions did not consider our chunk allocator and allocated
memory by themselves, which caused crashes and broken behaviour.

newer gtkdoc is more sensitive to mismatched docbook tags.
This fixes the build in master.

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

recv_rtp_sink: allow proxying of the allocation query.
send_rtp_sink: allow proxying of caps and allocation. This allows us to
query caps downstream as well as get an allocator from downstream.
send_rtp_src: allow proxy of caps, this makes the caps query do
upstream.

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

Check the charset from (C)*** tags and set the charset
to convert from MAC encoding if suitable.

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

We want to notice ourselves that we're EOS. Otherwise we will
always cancel requests in the very end and confuse the server...
and also make it impossible to use persistent connections.

It's set as property by the application, we should not just reset
properties when going back to READY.

Don't wait for that until the element is disposed.

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

souphttpsrc: Add "compress" property to enable/disable automatic gzip/deflate content encoding handling