[Bug 748946] videoaggregator: add "ignore-eos" property to input pads to ignore EOS

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=748946

Tim-Philipp Müller <t.i.m at zen.co.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED
   Target Milestone|git master                  |1.5.2

--- Comment #7 from Tim-Philipp Müller <t.i.m at zen.co.uk> ---
Pushed, thanks (with one minor modification - I changed the log message a
little so it's clearer):

commit 220a1334792d8ff40f00df05e83918a77f5eef5a
Author: Nirbheek Chauhan <nirbheek at centricular.com>
Date:   Sat Jun 6 20:40:13 2015 +0530

    tests: Add test for the 'ignore-eos' compositor sink pad property

    When the 'ignore-eos' property is set on a pad, compositor will keep
resending
    the last buffer on the pad till the pad is unlinked. We count the buffers
    received on appsink, and if it's more than the buffers sent by
videotestsrc, the
    test passes.

commit b395c055ebd47a724fd2bc815d525cee531f25ba
Author: Nirbheek Chauhan <nirbheek at centricular.com>
Date:   Tue Feb 10 00:49:35 2015 +0530

    videoaggregator: add "ignore-eos" property for input pads

    When set, it causes videoaggregator to repeatedly aggregate the last buffer
on
    an EOS pad instead of skipping it and outputting silence. This is useful,
for
    instance, while playing back files seamless one after the other, to avoid
    videoaggregator ever outputting silence (the checkerboard pattern).

    It is to be noted that if all the pads on videoaggregator have this
property set
    on them, the mixer will never forward EOS downstream for obvious reasons.
Hence,
    at least one pad with 'ignore-eos' set to FALSE must send EOS to the mixer
    before it will be forwarded downstream.

    https://bugzilla.gnome.org/show_bug.cgi?id=748946

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.