mirrors/gstreamer
mirrors/gstreamer
1
1
Fork 0
mirror of https://gitlab.freedesktop.org/gstreamer/gstreamer.git synced 2024-12-25 01:30:38 +00:00
Code Issues 1 Projects Releases Wiki Activity

more updates

Browse source
This commit is contained in:
Wim Taymans 2010-11-08 14:08:36 +01:00
parent 0ed1d4257d
commit 25480c7f49
1 changed files with 23 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

24
docs/random/plan-0.11.txt
View file

@ -1,8 +1,7 @@
Plan for 0.11 Plan for 0.11
============= =============
First attempt at making a list of tasks in rougly chronological order. First attempt at making a list of tasks in roughly chronological order.
* General cleanup * General cleanup
@ -13,6 +12,7 @@ First attempt at making a list of tasks in rougly chronological order.
This should allow us to continue expanding later in the same way that 0.10 was This should allow us to continue expanding later in the same way that 0.10 was
exapanded. exapanded.
* Review GstCaps fields * Review GstCaps fields
- go over caps fields for audio, video, compressed media-type etc - go over caps fields for audio, video, compressed media-type etc
@ -20,10 +20,14 @@ First attempt at making a list of tasks in rougly chronological order.
We need to express things with less fields. This would speed up caps, make We need to express things with less fields. This would speed up caps, make
them less verbose and speed up some elements. them less verbose and speed up some elements.
* Add GstFlowReturn for events (and query) * Add GstFlowReturn for events (and query)
This would allow us to know more precisely what went wrong. This would allow us to know more precisely what went wrong.
http://cgit.freedesktop.org/~wtay/gstreamer/log/?h=events2
* add return structure for events and query * add return structure for events and query
Make events return more information. (a seek event might want to return the Make events return more information. (a seek event might want to return the
@ -33,6 +37,7 @@ First attempt at making a list of tasks in rougly chronological order.
refcount being exactly 1. If the query is not writable, it simply cannot be refcount being exactly 1. If the query is not writable, it simply cannot be
answered. answered.
* Make GstMiniObject a simple boxed type * Make GstMiniObject a simple boxed type
- Move copy and free function to structure - Move copy and free function to structure
@ -46,10 +51,16 @@ First attempt at making a list of tasks in rougly chronological order.
Typechecking of various types is much more efficient when there is only Typechecking of various types is much more efficient when there is only
one class. one class.
http://cgit.freedesktop.org/~wtay/gstreamer/log/?h=miniobject2
* Convert GstCaps to GstMiniObject * Convert GstCaps to GstMiniObject
Currently it has its own refcounting and flags. Currently it has its own refcounting and flags.
http://cgit.freedesktop.org/~wtay/gstreamer/log/?h=miniobject2
* Incremental caps * Incremental caps
- Remove array from caps ? - Remove array from caps ?
@ -58,6 +69,9 @@ First attempt at making a list of tasks in rougly chronological order.
We need to perform less caps operations when negotiating formats. One way is We need to perform less caps operations when negotiating formats. One way is
to only handle small caps objects incrementally. to only handle small caps objects incrementally.
http://cgit.freedesktop.org/~ensonic/gstreamer/log/?h=lazycaps
* Make GstBufferMetadata * Make GstBufferMetadata
- Make functions to register metadata - Make functions to register metadata
@ -67,6 +81,9 @@ First attempt at making a list of tasks in rougly chronological order.
More flexible metadata for buffers. More flexible metadata for buffers.
http://cgit.freedesktop.org/~wtay/gstreamer/log/?h=buffermeta
* Negotiation of metadata * Negotiation of metadata
- figure out if we need to negotiate the metadata on the caps or if we can - figure out if we need to negotiate the metadata on the caps or if we can
@ -76,6 +93,7 @@ First attempt at making a list of tasks in rougly chronological order.
handling the buffer contents but that is then not understood by other handling the buffer contents but that is then not understood by other
elements. elements.
* Rework reverse negotiation * Rework reverse negotiation
- upstream event to notify of a downstream caps change - upstream event to notify of a downstream caps change
@ -93,6 +111,7 @@ First attempt at making a list of tasks in rougly chronological order.
API easier, we can then use metadata to specify additional contraints for the API easier, we can then use metadata to specify additional contraints for the
new buffer (such as strides, etc) new buffer (such as strides, etc)
* Incremental event progation * Incremental event progation
- certain events would be sticky on a pad like for caps - certain events would be sticky on a pad like for caps
@ -104,6 +123,7 @@ First attempt at making a list of tasks in rougly chronological order.
This would allow an application to have more control over the state of the This would allow an application to have more control over the state of the
dataflow in a pipeline. dataflow in a pipeline.
* GstSegment changes * GstSegment changes
- remove segment accumulation - remove segment accumulation