mirror of
https://gitlab.freedesktop.org/gstreamer/gstreamer.git
synced 2025-01-11 09:55:36 +00:00
docs/design/part-TODO.txt: Updated todo.
Original commit message from CVS: * docs/design/part-TODO.txt: Updated todo.
This commit is contained in:
parent
d5a2005e0c
commit
f5fe75472b
2 changed files with 25 additions and 15 deletions
|
@ -1,3 +1,8 @@
|
|||
2005-11-10 Wim Taymans <wim@fluendo.com>
|
||||
|
||||
* docs/design/part-TODO.txt:
|
||||
Updated todo.
|
||||
|
||||
2005-11-10 Wim Taymans <wim@fluendo.com>
|
||||
|
||||
* gst/base/gstbasesink.c: (gst_base_sink_do_sync):
|
||||
|
|
|
@ -1,8 +1,5 @@
|
|||
|
||||
- changing an object's name after construction is not allowed. Checks are performed
|
||||
when adding objects to parents that no duplicate names are used, changing the name
|
||||
to a duplicate name after adding it is therefore allowed and voids internal
|
||||
consistency.
|
||||
API/ABI
|
||||
-------
|
||||
|
||||
- implement return values from events in addition to the gboolean. This should be
|
||||
done by making the event contain a GstStructure with input/output values, similar
|
||||
|
@ -10,16 +7,6 @@
|
|||
after the seek you want to get the new stream time that will actually be used to
|
||||
update the slider bar.
|
||||
|
||||
- unlinking pads in the PAUSED state needs to make sure the stream thread is not
|
||||
executing code. Can this be done with a flush to unlock all downstream chain
|
||||
functions? Do we do this automatically or let the app handle this?
|
||||
|
||||
- implement clock selection as explained in part-gstpipeline.txt.
|
||||
|
||||
- when a pipeline with a live source goes to PAUSED again, a sample is prerolled
|
||||
in the sinks. This sample should be discarded, possibly with a flush event
|
||||
started from the source.
|
||||
|
||||
- convert framerate to GstFraction in GstCaps.
|
||||
|
||||
- implement latency calculation for live sources.
|
||||
|
@ -47,3 +34,21 @@
|
|||
|
||||
- query POSITION/DURATION return accuracy. Just a flag or accuracy percentage.
|
||||
|
||||
|
||||
IMPLEMENTATION
|
||||
--------------
|
||||
|
||||
- implement clock selection as explained in part-gstpipeline.txt.
|
||||
|
||||
|
||||
DESIGN
|
||||
------
|
||||
|
||||
- unlinking pads in the PAUSED state needs to make sure the stream thread is not
|
||||
executing code. Can this be done with a flush to unlock all downstream chain
|
||||
functions? Do we do this automatically or let the app handle this?
|
||||
|
||||
- when a pipeline with a live source goes to PAUSED again, a sample is prerolled
|
||||
in the sinks. This sample should be discarded, possibly with a flush event
|
||||
started from the source.
|
||||
|
||||
|
|
Loading…
Reference in a new issue