gstreamer/tests
Carlos Rafael Giani a1d2f387c6 multiqueue: Recalculate fill level after changing high-threshold
This ensures the following special case is handled properly:

1. Queue is empty
2. Data is pushed, fill level is below the current high-threshold
3. high-threshold is set to a level that is below the current fill level

Since mq->percent wasn't being recalculated in step #3 properly, this
caused the multiqueue to switch off its buffering state when new data is
pushed in, and never post a 100% buffering message. The application will
have received a <100% buffering message from step #2, but will never see
100%.

Fix this by recalculating the current fill level percentage during
high-threshold property changes in the same manner as it is done when
use-buffering is modified.

https://bugzilla.gnome.org/show_bug.cgi?id=763757
2016-04-15 16:04:54 +03:00
..
benchmarks benchmark: tracerserialize: add missing return statement 2016-02-15 12:34:17 -03:00
check multiqueue: Recalculate fill level after changing high-threshold 2016-04-15 16:04:54 +03:00
examples gstreamer: Fix memory leaks when context parse fails 2015-10-02 17:31:11 +03:00
misc netclock: Link the replay example to GIO 2016-03-25 10:23:46 +02:00
.gitignore Add new streamiddemux binaries to .gitignore 2015-03-14 16:05:57 +00:00
Makefile.am configure: add --disable-tools and --disable-benchmarks options 2012-06-26 23:12:56 +01:00
README README: update after removal of "old" dir. 2010-07-05 12:26:42 +03:00

This directory contains regression tests, functionality tests, examples,
benchmarks, ...

benchmarks/
   benchmarks to profile pieces of GStreamer
check/
   unit tests using the check library, non-interactive
examples/
   small examples demonstrating the use of various features
misc/
   prototypes, random bits, ...