baseparse: Don't return more data than asked for in pull_range()
Even when pulling a new 64KB buffer from upstream, don't return
more data than was asked for in the pull_range() method and then
return less later, as that confused subclasses like h264parse.
Add a unit test that when a subclass asks for more data, it always
receives a larger buffer on the next iteration, never less.
570736d...
by
=?utf-8?q?Tim-Philipp_M=C3=BCller?= <email address hidden>
Release 1.16.3
0922975...
by
=?utf-8?q?Tim-Philipp_M=C3=BCller?= <email address hidden>
Update docs
155a4b6...
by
=?utf-8?q?Tim-Philipp_M=C3=BCller?= <email address hidden>
Update translations
c899387...
by
=?utf-8?q?Tim-Philipp_M=C3=BCller?= <email address hidden>
Automatic update of common submodule
From 59cb678 to a825d27
e846ef2...
by
Mathieu Duponchelle <email address hidden>
gstvalue: don't write to const char *
Our various deserializing functions require NULL terminators
to not over consume substrings (eg fields of an array). Instead
of writing a NULL terminator to the passed-in string, which may
result in segfaults, make a copy of the substring we're interested
in.
fa2f853...
by
Matthew Waters <email address hidden>
build: use cpu_family for arch checks
e.g. on 32-bit arm, we may have armv6, armv7l, armv7hf, etc which all
generally have the same layouts. cpu_family() groups all of these into
just 'arm' that the ABI check table is expecting.
cc13705...
by
Roman Shpuntov <email address hidden>
systemclock: Fix clock time conversion on Windows/xbox
The returned ratio can be bigger than GST_SECOND, in which case we would
forever return 0 for the system clock time. Even in other cases if it's
close to GST_SECOND it would result in accuracy loss.
Instead of doing the division by GST_CLOCK_TIME_NONE during
initialization once, do it every time the clock time is requested.
