1. 09 Jan, 2019 1 commit
  2. 15 Dec, 2018 1 commit
  3. 03 Nov, 2018 1 commit
  4. 06 Sep, 2018 1 commit
  5. 20 Apr, 2018 2 commits
  6. 20 Aug, 2017 1 commit
  7. 26 Jul, 2017 2 commits
  8. 03 Apr, 2017 1 commit
  9. 08 Mar, 2017 1 commit
  10. 29 Jul, 2016 1 commit
  11. 14 May, 2016 1 commit
  12. 24 Sep, 2015 1 commit
  13. 03 Jul, 2015 1 commit
  14. 02 Jul, 2015 1 commit
  15. 10 Jun, 2015 1 commit
  16. 31 Mar, 2015 1 commit
  17. 06 Dec, 2014 4 commits
  18. 10 Nov, 2014 2 commits
  19. 31 Oct, 2014 1 commit
  20. 09 Jun, 2014 1 commit
  21. 07 Apr, 2014 1 commit
  22. 21 Mar, 2014 1 commit
  23. 14 Mar, 2014 1 commit
    • Thibault Saunier's avatar
      pipeline: Always set the encoding profile presence to 1 · 0a903cdd
      Thibault Saunier authored
      We currenty do not support multiple tracks with same type in GESPipeline
      and we actually need to set the presence field to avoid a scenario where
      we have only video in a video track, and no audio in the audio track. So
      audiotestsrc is used and we end up encoding the whole audio stream but
      no decoded video frame as reached the decodebin src pad, so the pad
      has not been created and thus it will not be linked to the encodebin.
      On the audio part, the EOS will be emitted so fast that the resulting stream will
      not have any video in it as the muxer will not even have a video pad created.
      
      Setting the presence will ensure that the muxer does have a video pad
      (because of how encodebin behaves) and thus will create a pad for it
      and wait for its EOS.
      0a903cdd
  24. 17 Feb, 2014 1 commit
  25. 04 Feb, 2014 1 commit
  26. 31 Oct, 2013 1 commit
  27. 22 Sep, 2013 1 commit
  28. 12 Sep, 2013 1 commit
  29. 09 Sep, 2013 2 commits
  30. 21 Aug, 2013 1 commit
  31. 19 Aug, 2013 1 commit
    • Thibault Saunier's avatar
      pipeline: Remove the dynamic lock · 0c871049
      Thibault Saunier authored
      We actually do not need it has everywhere where we would need it we are
      already locked against the timeline.dyn_lock, we need to make sure it is
      always the case in the future.
      
      The hierarchy of the mutex was wrong and could possibly lead to
      deadlocks
      0c871049
  32. 22 Jul, 2013 2 commits