7 Queries are used to get information about the stream.
8 A query is started on a specific pad and travels up or downstream.
14 - multiple return values, grouped together when they make sense.
15 - one pad function to perform the query
21 - GstQuery extends GstMiniObject and contains a GstStructure (see GstMessage)
22 - some standard query types are defined below
23 - methods to create and parse the results in the GstQuery.
26 gboolean (*GstPadQueryFunction) (GstPad *pad,
30 pad returns result in query structure and TRUE as result or FALSE when
31 query is not supported.
38 get info on current position of the stream in stream_time.
42 get info on the total duration of the stream.
46 get amount of latency introduced in the pipeline. (See part-latency.txt)
50 get the current playback rate of the pipeline
54 get info on how seeking can be done
55 - getrange, with/without offset/size
56 - ranges where seeking is efficient (for caching network sources)
57 - flags describing seeking behaviour (forward, backward, segments,
62 get info about the currently configured playback segment.
66 convert format/value to another format/value pair.
70 return list of supported formats that can be used for GST_QUERY_CONVERT.
72 - GST_QUERY_BUFFERING:
74 query available media for efficient seeking (See part-buffering.txt)
78 a custom query, the name of the query defines the properties of the query.
82 query the uri of the source or sink element
84 - GST_QUERY_ALLOCATION:
86 the buffer allocation properties (See part-bufferpool.txt)
88 - GST_QUERY_SCHEDULING:
90 the scheduling properties (See part-scheduling.txt)
92 - GST_QUERY_ACCEPT_CAPS:
94 check if caps are supported (See part-negotiation.txt)
98 get the possible caps (See part-negotiation.txt)