• Sebastian Dröge's avatar
    aggregator: Always handle serialized events/queries directly before waiting · 74797e96
    Sebastian Dröge authored
    Otherwise it can happen that we start waiting for another pad, while one
    pad already has events that can be handled and potentially also a buffer
    that can be handled. That buffer would then however not be accessible by
    the subclass from GstAggregator::get_next_time() as there would be the
    events in front of it, which doesn't allow the subclass then to
    calculate the next time based on already available buffers.
    As a side-effect this also allows removing the duplicated event handling
    code in the aggregate function as we'll always report pads as not ready
    when there is a serialized event or query at the top of at least one
    pad's queue.
    Fixes #428
Last commit
Last update
gst Loading commit data...
Makefile.am Loading commit data...
meson.build Loading commit data...