1. 14 Mar, 2019 1 commit
  2. 04 Mar, 2019 1 commit
  3. 26 Feb, 2019 1 commit
  4. 14 Feb, 2019 1 commit
  5. 25 Jan, 2019 6 commits
  6. 17 Jan, 2019 1 commit
  7. 09 Jan, 2019 1 commit
  8. 08 Jan, 2019 1 commit
    • Guillaume Desmottes's avatar
      omxbufferpool: fix race when releasing input buffers · 9dc359d0
      Guillaume Desmottes authored
      If buffers were released from the pool while
      gst_omx_video_enc_handle_frame() was waiting for new buffers,
      gst_omx_port_acquire_buffer() was never awaken as the buffers weren't
      released through OMX's messaging system.
      
      GQueue isn't thread safe so also protect it with the lock mutex.
      9dc359d0
  9. 21 Dec, 2018 1 commit
    • Guillaume Desmottes's avatar
      omxbufferpool: fix early input buffer release · 3828d976
      Guillaume Desmottes authored and Guillaume Desmottes's avatar Guillaume Desmottes committed
      We used to track the 'allocating' status on the pool. It is used while
      allocating so output buffers aren't passed right away to OMX and input
      ones are not re-added to the pending queue.
      
      This was causing a bug when exporting buffers to v4l2src. On start
      v4l2src acquires a buffer, read its stride and release it right away.
      As no buffer was received by the encoder element at this point, 'allocating'
      was still on TRUE and so the the buffer wasn't put back to the pending
      queue and, as result, no longer available to the pool.
      
      Fix this by checking the active status of the pool instead of manually
      tracking it down. The pool is considered as active at the very end of
      the activation process so we're good when buffers are released during
      the activation.
      3828d976
  10. 05 Dec, 2018 1 commit
  11. 26 Nov, 2018 1 commit
  12. 05 Nov, 2018 1 commit
  13. 26 Sep, 2018 1 commit
  14. 19 Sep, 2018 4 commits
  15. 10 Sep, 2018 3 commits
  16. 31 Aug, 2018 1 commit
  17. 30 Aug, 2018 14 commits