1. 30 Jan, 2018 12 commits
  2. 29 Jan, 2018 3 commits
  3. 22 Jan, 2018 1 commit
  4. 19 Jan, 2018 1 commit
  5. 07 Jan, 2018 1 commit
  6. 19 Dec, 2017 2 commits
  7. 14 Dec, 2017 6 commits
  8. 13 Dec, 2017 2 commits
  9. 11 Dec, 2017 3 commits
  10. 29 Nov, 2017 2 commits
  11. 28 Nov, 2017 2 commits
    • Guillaume Desmottes's avatar
      omx: wait for flush complete and buffers being released when flushing · 4211e4c2
      Guillaume Desmottes authored
      As stated in the existing comment, when flusing we should wait for OMX
      to send the flush command complete event AND all ports being released.
      We were stopping as soon as one of those condition was met.
      
      Fix a race between FillThisBufferDone/EmptyBufferDone and the flush
      EventCmdComplete messages. The OMX implementation is supposed to release
      its buffers before posting the EventCmdComplete event but the ordering
      isn't guaranteed as the FillThisBufferDone/EmptyBufferDone and
      EventHandler callbacks can be called from different threads (cf 2.7
      'Thread Safety' in the spec).
      
      https://bugzilla.gnome.org/show_bug.cgi?id=789475
      4211e4c2
    • Guillaume Desmottes's avatar
      gst_omx_port_set_flushing: simplify waiting loop · 4c0a8a6d
      Guillaume Desmottes authored
      No semantic change so far, I just made the 'while' end condition easier
      to understand as a first step before changing it.
      - move error/time out checks inside the loop to make it clearer on what
      we are actually waiting for.
      - group port->buffers checks together with parenthesis as they are part
      of the same conceptual check: waiting for all buffers to be released.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=789475
      4c0a8a6d
  12. 27 Nov, 2017 1 commit
  13. 23 Nov, 2017 1 commit
  14. 19 Oct, 2017 3 commits