capsfeatures: Add documentation about ANY GstCapsFeatures

This commit is contained in:
Sebastian Dröge 2013-04-19 11:23:31 +02:00
parent 86b4e1841e
commit 7ae54c34e5
2 changed files with 8 additions and 2 deletions

View file

@ -33,7 +33,8 @@ that makes most sense for the media format by the element or pad
implementation and afterwards every remaining unfixed fields is set to implementation and afterwards every remaining unfixed fields is set to
an arbitrary value that would be a subset of the unfixed field value. an arbitrary value that would be a subset of the unfixed field value.
EMPTY caps are fixed caps, ANY caps are not fixed. EMPTY caps are fixed caps, ANY caps are not fixed. Caps with ANY caps
features are not fixed.
Subset Subset
------ ------

View file

@ -30,7 +30,12 @@
* structures with different feature sets to the caps. * structures with different feature sets to the caps.
* *
* Empty #GstCapsFeatures are equivalent with the #GstCapsFeatures that only * Empty #GstCapsFeatures are equivalent with the #GstCapsFeatures that only
* contain #GST_CAPS_FEATURE_MEMORY_SYSTEM_MEMORY. * contain #GST_CAPS_FEATURE_MEMORY_SYSTEM_MEMORY. ANY #GstCapsFeatures as
* created by gst_caps_features_new_any() are equal to any other #GstCapsFeatures
* and can be used to specify that any #GstCapsFeatures would be supported, e.g.
* for elements that don't touch buffer memory. #GstCaps with ANY #GstCapsFeatures
* are considered non-fixed and during negotiation some #GstCapsFeatures have
* to be selected.
* *
* Examples for caps features would be the requirement of a specific #GstMemory * Examples for caps features would be the requirement of a specific #GstMemory
* types or the requirement of having a specific #GstMeta on the buffer. Features * types or the requirement of having a specific #GstMeta on the buffer. Features