mirror of
https://gitlab.freedesktop.org/gstreamer/gstreamer.git
synced 2024-12-19 14:56:36 +00:00
b37766658e
Original commit message from CVS: * docs/design/part-TODO.txt: Updated TODO list, basesrc supports seeking to non-bytes formats. * docs/design/part-element-sink.txt: Update docs. * gst/gstbin.c: (bin_replace_message), (gst_bin_handle_message_func): * gst/gstbus.c: (gst_bus_post), (gst_bus_pop): * gst/gstevent.c: (gst_event_finalize): * gst/gstpad.c: (gst_pad_event_default_dispatch), (gst_pad_send_event): Use shiny new _TYPE_NAME macros. * libs/gst/base/gstbasesrc.c: (gst_base_src_get_range): Move debug statement up. * gst/gstelement.c: (gst_element_set_locked_state): Add some debugging.
40 lines
1.3 KiB
Text
40 lines
1.3 KiB
Text
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
|
|
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.
|
|
|
|
- GstEvent, GstMessage register like GstFormat or GstQuery.
|
|
|
|
- query POSITION/DURATION return accuracy. Just a flag or accuracy percentage.
|
|
|
|
- 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.
|
|
|
|
|
|
IMPLEMENTATION
|
|
--------------
|
|
|
|
- implement latency calculation for live sources.
|
|
|
|
- implement QOS.
|
|
|
|
- implement BUFFERSIZE.
|
|
|
|
- implement pad_block with probes.
|
|
|
|
|
|
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?
|
|
|