GitLab

Remember to free the ftyp data after writing it to a file.

Fixes #660969

... as well as related items, such as seeking and position reporting.

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

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

Refactor bitrate check test to accomodate multiple tests
for bitrate

AAC in mov format puts an ESDS atom inside of a WAVE atom in
STSD atom, we need to update the bitrate on this ESDS. This patch
fixes it.

When rewriting bitrates, also update the btrt atom under stsd

Adds tests to make sure qtmux/mp4mux sets average bitrate
correctly

Calculate and use average bitrate for streams when no
bitrate tag was received

If first_ts is 0 there is no need to subtract, so we might
skip some copying to make the buffer metadata writable.

Since matroskademux will attempt to push unaligned buffers,
downstream might have trouble with those, especially if downstream
uses ORC, such as audioconvert.

Ensure we push buffers aligned to the basic type at least for
those raw buffers.

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

Fixes bug #660294.

To avoid confusion, and because we might want a server
sink at some point too.

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

The base class will create the sink pad.

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

... although basertpdepay does not really make it easy/possible to do so
all the way.

A particular window may be selected using the new xid (X-Window
XID, eg a pointer) and xname (window title) properties. If both
are specified, the XID is used in preference, falling back to
xname if not found.

Default (if none of xid and xname are specified, or if no such
window is found) is to capture the root window.

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

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

Fixes bug #659237.

Use slightly adjusted sender interval to determine sender timeout rather than
our own sender side interval (which may have been forced small).

... following a PAUSE/PLAY cycle, particularly applicable when operating
with a short RTCP interval (possibly forced so server-side).

... to at least having it trigger a/v synchronization, possibly without
using provided values which are still not considered sane
(as previously dropped).

... which in particular caters for some more reset following a possible
rtsp PLAY.

... when operating in non slave mode, and reset if detected.
This should avoid some (large) bogus outgoing timestamp due to jumps
in rtp time, as result of PAUSE/PLAY or seek or ...

... at least if not syncing to NPT time:
* either sync using RTCP SR data (as currently)
* only perform the above once using initial RTCP SR packets
* discard RTCP and sync by equating provided stream's clock-base rtptime,
  as provided by jitterbuffer (typically obtained from RTP-Info in RTSP).

... rather than necessarily syncing at each RTCP SR.

... in PLAY response.