rtspconnection: also allow POST before GET

Don't only allow GET and then POST request to setup tunneling over HTTP
but also allow POST and then GET.

Fixes https://bugzilla.gnome.org/show_bug.cgi?id=732459
docs: Assorted documentation and introspection fixes for new 1.4 API

https://bugzilla.gnome.org/show_bug.cgi?id=732595
tests: codec-select: Plug element name memory leak

https://bugzilla.gnome.org/show_bug.cgi?id=732593
mikey: make message and payload mini-objects

Make the MIKEY message and payload objects miniobjects so that they have
a GType and are refcounted.
We can reuse the dispose method to clear our payload objects.
Add some annotations.
Implement a copy function for the MIKEY message.
Fix the unit test.

Fixes https://bugzilla.gnome.org/show_bug.cgi?id=732589
mikey: add more Since markers for new methods
tests: codec-select: fix compilation
videodecoder: parse any source data that is still available.

Fix gst_video_decoder_parse_available() to really parse any pending
source data that is still available in the adapter. This is a memory
optimization to avoid expansion of video packed added to the adapter,
but also a fix to EOS condition when the subclass parse() function
ultimately only needed to call into gvd_have_frame() and no additional
source bytes were consumed, i.e. gvd_add_to_frame() is not called.

This situation can occur when decoding H.264 streams in byte-stream/nal
mode for instance. A decoder always requires the next NAL unit to be
parsed so that to determine picture boundaries. When a new picture is
found, no byte is consumed (i.e. gvd_add_to_frame() is not called)
but gvd_have_frame() is called (i.e. priv->current_frame is gone).

Also make sure to avoid infinite loops caused by incorrect subclass
parse() implementations. This can occur when no byte gets consumed
and no appropriate indication (GST_VIDEO_DECODER_FLOW_NEED_DATA) is
returned.

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

Signed-off-by: Gwenole Beauchesne <gwenole.beauchesne@intel.com>
riff: Print invalid fourcc in error message in hex

Previously this was printed as characters which caused later processing
of the error message to sometimes warn about non-UTF-8 characters.

Fixes https://bugzilla.gnome.org/show_bug.cgi?id=732697
sdp: add gstmikey.h to sdp.h

https://bugzilla.gnome.org/show_bug.cgi?id=732709
po: Update translations
dmabuf: Ensure _get_fd() works even for shared memory

Fixes regression introduced by:

commit b60888fd4bcacd42bb4e27fa938272d6e72c5c32
Author: Michael Olbrich <m.olbrich@pengutronix.de>
Date:   Tue May 20 11:18:56 2014 +0200

    dmabuf: share the mapping with shared copies of the memory

https://bugzilla.gnome.org/show_bug.cgi?id=730441
libvisual: Remove < 0.4 support

And remove the version guards that went along with it

https://bugzilla.gnome.org/show_bug.cgi?id=733046
Update .po files
Release 1.3.91
playsink: Fix filter property getter

The switch-case set was incomplete.

https://bugzilla.gnome.org/show_bug.cgi?id=733012
po: update POTFILES

https://bugzilla.gnome.org/show_bug.cgi?id=733207
xvimagesink: fix property description string

Spotted by Josep Torra.
adder: Handle seqnums
videotestsrc: Learn to seek on READY.
audiodecoder: Are you a nazi ? We sure don't like nazi around here !