2005-03-22 11:32:59 +00:00
|
|
|
|
|
|
|
- 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.
|
|
|
|
|
|
|
|
- check for race in _task_pause()/_stop() since the TASK_LOCK is not held by the
|
|
|
|
calling thread and the STREAM_LOCK not by the task code.
|
|
|
|
|
|
|
|
- only emit EOS in PLAYING. Make sure elements reemit the EOS message when going to
|
|
|
|
PLAYING again.
|
|
|
|
|
2005-04-21 09:37:34 +00:00
|
|
|
- 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
|
|
|
|
to GstMessage.
|
2005-03-22 11:32:59 +00:00
|
|
|
|
|
|
|
- implement query ala events as opposed to the current return value of only a
|
|
|
|
guint64. I don't have a use case where this a problem yet, though.
|
|
|
|
|
|
|
|
- implement state change order on get<->loop-get<->loop elements. This probably
|
|
|
|
requires a backtracking algorithm.
|
|
|
|
|
|
|
|
- implement iterators for traversing elements upstream or dowstream.
|
|
|
|
|
|
|
|
- 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?
|
|
|
|
|
|
|
|
- make the seek event return the time where the seek will happen so that GstPipeline
|
2005-04-21 09:37:34 +00:00
|
|
|
can update the stream time. This is linked with making the events return values.
|
2005-03-22 11:32:59 +00:00
|
|
|
|
|
|
|
- implement clock selection as explained in part-gstpipeline.txt
|
|
|
|
|