it only comes at the start it's state that needs to be kept on pads very similar to the caps on the buffer (Wim), but you would lose speed that way (Edward) descriptor of the stream, for timing information caching in the pad: great putting it on every buffer: not so great elements mostly store it for clipping or demuxing makes sense to keep as an event (for example for GDP) "given a buffer, how do I get the timing info for that buffer" (Wim) parity error between segment and accumulator

timestamps

rounding errors for nanoseconds

use a clock-base

clock-base would be per-stream, not global

clock distribution

make it atomic to set clock and base time

GST_CLOCK_TIME_NONE

shoving a signed int into a uint creates problems

bindings

needing to use macros

negative timestamps

Jan has a use case for DVD's sending older data after sending time info

error reporting

Internal flow error coming from the source

no way to know where it came from except looking from the log

caps negotiation and intersection failing

Stefan would already be happy with something in the logs saying why

this is for app developers trying to figure out nego

Jan: should be possible to try and negotiate, get a failure message, and try again with a different decoder/element