Skip to content
Snippets Groups Projects
  1. Jun 07, 2015
  2. Jun 02, 2015
  3. May 26, 2015
  4. May 12, 2015
  5. May 10, 2015
  6. Apr 27, 2015
  7. Apr 26, 2015
  8. Apr 24, 2015
  9. Apr 23, 2015
  10. Apr 22, 2015
    • Sebastian Dröge's avatar
      Remove LICENSE_readme · cd735fc0
      Sebastian Dröge authored
      It's completely outdated and just confusing, better if people are
      forced to look at the actual code in question than trusting this file.
      cd735fc0
    • Sebastian Dröge's avatar
      Remove INSTALL file · 684345eb
      Sebastian Dröge authored
      autotools automatically generate this, and when using different versions
      for autogen.sh there will always be changes to a file tracked by git.
      684345eb
  11. Apr 20, 2015
  12. Apr 08, 2015
  13. Apr 03, 2015
  14. Mar 30, 2015
  15. Mar 28, 2015
  16. Mar 24, 2015
  17. Mar 13, 2015
  18. Mar 10, 2015
  19. Mar 09, 2015
  20. Feb 15, 2015
    • Simon Farnsworth's avatar
      mpeg2dec: Fix handling of stride · f3e8dcb9
      Simon Farnsworth authored and Nicolas Dufresne's avatar Nicolas Dufresne committed
      
      A pipeline like:
      
      gst-launch-1.0 filesrc location=file.ts ! tsdemux ! mpegvideoparse ! mpeg2dec  ! vaapisink
      
      would look bad when file.ts contains 704x576 video, because vaapisink would
      give you buffers of stride 768, but libmpeg2 was not told about this and
      used a stride of 704.
      
      Tell libmpeg2 about the stride from  downstream; in the process, teach it to
      reject buffer pools that don't meet libmpeg2's chroma stride requirements
      
      Signed-off-by: default avatarSimon Farnsworth <simon.farnsworth@onelan.co.uk>
      f3e8dcb9
  21. Feb 11, 2015
  22. Feb 06, 2015
    • Sebastian Dröge's avatar
      x264enc: Don't set max latency to the same value as the encoder latency · 5dd1a289
      Sebastian Dröge authored
      The meaning of the max latency is *not* the maximum latency this element will
      introduce. It is the maximum latency this element can endure without
      overflowing any buffers, which is infinite for x264enc.
      
      Fixes latency configuration in zero latency mode, where max latency was
      becoming 0... which usually won't work well if something else introduces
      latency as then max < min in the end, and latency configuration just fails.
      5dd1a289
  23. Feb 02, 2015
  24. Jan 21, 2015
  25. Jan 18, 2015
  26. Jan 12, 2015
Loading