2005-11-10 15:07:46 +00:00
|
|
|
API/ABI
|
|
|
|
-------
|
2005-03-22 11:32:59 +00:00
|
|
|
|
2006-05-10 13:53:48 +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 GstQuery. A typical use case is performing a non-accurate seek to a
|
|
|
|
keyframe, after the seek you want to get the new stream time that will
|
|
|
|
actually be used to update the slider bar.
|
2005-03-22 11:32:59 +00:00
|
|
|
|
2005-10-28 18:14:24 +00:00
|
|
|
- GstEvent, GstMessage register like GstFormat or GstQuery.
|
2005-11-03 20:14:24 +00:00
|
|
|
|
2005-11-09 12:01:46 +00:00
|
|
|
- query POSITION/DURATION return accuracy. Just a flag or accuracy percentage.
|
|
|
|
|
2006-05-10 13:53:48 +00:00
|
|
|
- add some sort of time/frame stepping functionality, either with a flag on
|
|
|
|
the seek event or some new seek event type. The idea would be to operate on
|
|
|
|
the current playback position instead of the current configured segment when
|
|
|
|
doing the seek.
|
|
|
|
Idea is that frame stepping forwards can be done in the sinks, ie, just
|
|
|
|
dropping N frames/time, sending more complicated queries upstream which can
|
|
|
|
ideally handle those cases more efficiently too.
|
2005-11-15 15:44:46 +00:00
|
|
|
|
2006-05-10 13:53:48 +00:00
|
|
|
- use | instead of + as divider in serialization of Flags
|
|
|
|
(gstvalue/gststructure)
|
2005-11-10 15:07:46 +00:00
|
|
|
|
|
|
|
IMPLEMENTATION
|
|
|
|
--------------
|
|
|
|
|
2005-11-19 18:28:40 +00:00
|
|
|
- implement latency calculation for live sources.
|
|
|
|
|
2006-04-28 12:58:15 +00:00
|
|
|
- implement more QOS, see part-qos.txt.
|
2005-11-19 18:28:40 +00:00
|
|
|
|
|
|
|
- implement BUFFERSIZE.
|
2005-11-10 15:07:46 +00:00
|
|
|
|
2005-11-23 13:14:46 +00:00
|
|
|
- implement pad_block with probes.
|
|
|
|
|
2005-11-10 15:07:46 +00:00
|
|
|
|
|
|
|
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?
|
|
|
|
|