gstreamer/tests/check
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
..
elements multiqueue: Recalculate fill level after changing high-threshold 2016-04-15 16:04:54 +03:00
generic check: Rename states unit test 2015-08-14 11:10:37 +02:00
gst tests: bufferpool: fix wrong assumptions about pointers and object lifecycles 2016-04-10 20:11:00 +01:00
libs tests: baseparse: make work with CK_FORK=no 2016-04-11 10:44:22 +01:00
pipelines gstreamer: use new gst_element_class_add_static_pad_template() 2016-03-24 14:43:41 +02:00
tools tests: refactor tools check a little 2014-10-31 16:10:01 +00:00
.gitignore tests: add check for gst-inspect --exists functionality 2012-09-01 23:02:10 +01:00
Makefile.am tests: add PTHREAD_CFLAGS for make check to pass on OS X 2016-04-11 18:03:49 +01:00