From 5898223bb98564c1a3757c0d1aa7680d82745c80 Mon Sep 17 00:00:00 2001 From: Wim Taymans Date: Fri, 12 Oct 2012 12:55:03 +0200 Subject: [PATCH] qos: messages are posted, not dropped --- docs/design/part-qos.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/design/part-qos.txt b/docs/design/part-qos.txt index daffa0171b..e80a7a1846 100644 --- a/docs/design/part-qos.txt +++ b/docs/design/part-qos.txt @@ -84,7 +84,7 @@ fast and does not significantly contribute to the QoS problems. Options to disable this feature could also be presented on elements. This message can be posted by a sink/src that performs synchronisation against the -clock (live) or it could be dropped by an upstream element that performs QoS +clock (live) or it could be posted by an upstream element that performs QoS because of QOS events received from a downstream element (!live). The GST_MESSAGE_QOS contains at least the following info: