1. 21 May, 2015 5 commits
  2. 19 May, 2015 3 commits
  3. 16 May, 2015 2 commits
  4. 14 May, 2015 1 commit
  5. 12 May, 2015 1 commit
  6. 11 May, 2015 1 commit
  7. 10 May, 2015 1 commit
  8. 09 May, 2015 1 commit
  9. 07 May, 2015 1 commit
  10. 06 May, 2015 6 commits
  11. 05 May, 2015 1 commit
  12. 01 May, 2015 3 commits
  13. 30 Apr, 2015 6 commits
  14. 29 Apr, 2015 1 commit
    • Rémi Denis-Courmont's avatar
      vdpau: fix importing surface from main memory · 1798c312
      Rémi Denis-Courmont authored
      On the one hand, when decoding in hardware, the video surface
      dimensions will match the coded dimensions, rather than the visible
      ones. Otherwise the hardware decoder would not have enough space for
      its output. In this the libavcodec plugin does not add padding (since
      libavcodec SIMD optimizations are not involved).
      
      On the other hand, when decoding in software, the video surface height
      must not include the padding added by libavcodec SIMD optimizations. So
      then the visible height needs to be used to avoid bleeding green lines.
      
      (cherry picked from commit 3b3bd7e49d52875024c6f1b0ef4eac124a637c2d)
      
      Conflicts:
      	modules/hw/vdpau/chroma.c
      1798c312
  15. 28 Apr, 2015 2 commits
  16. 27 Apr, 2015 4 commits
  17. 25 Apr, 2015 1 commit