1. 06 Oct, 2010 1 commit
  2. 06 Jul, 2010 1 commit
  3. 02 Jul, 2010 1 commit
  4. 11 Jun, 2010 1 commit
  5. 31 May, 2010 1 commit
  6. 10 May, 2010 1 commit
  7. 08 May, 2010 1 commit
  8. 24 Mar, 2010 1 commit
  9. 23 Mar, 2010 1 commit
  10. 03 Mar, 2010 1 commit
  11. 18 Feb, 2010 2 commits
  12. 04 Feb, 2010 1 commit
  13. 29 Jan, 2010 1 commit
    • Wim Taymans's avatar
      ffmpegcodecmap: don't escape codec_data · d3f9ee43
      Wim Taymans authored
      Don't escape the codec_data, it breaks some streams (but likely also fixes
      others). It's better to leave it as is, like most other players do.
      
      See #608332
      d3f9ee43
  14. 23 Jan, 2010 3 commits
  15. 13 Jan, 2010 1 commit
  16. 22 Nov, 2009 1 commit
  17. 11 Nov, 2009 1 commit
    • Jan Schmidt's avatar
      ffmpeg: VC-1/WMV3 fixes. · 62d54db0
      Jan Schmidt authored
      Use format field in the pad caps to differentiate VC-1 from WMV3.
      Fix a typo in the caps creation and parsing - the field is called
      'format' - not 'fourcc'
      
      Add a dodgy hack to populate the extradata size field
      (first byte) when it is 0 - as it seems to be for some (Matroska)
      test files.
      62d54db0
  18. 10 Nov, 2009 1 commit
    • Sjoerd Simons's avatar
      Always give the most video restricted caps possible · 19e81024
      Sjoerd Simons authored
      When the video caps aren't fixed yet, make sure we return the most
      precise set of caps. It seems a regression was introduced in cc082f,
      causing restricted caps to never be used if the context == NULL
      
      None of the restricted caps generation uses the context, so no need to
      check whether the context.
      
      Fixes bug #578160.
      19e81024
  19. 09 Sep, 2009 1 commit
  20. 08 Sep, 2009 1 commit
  21. 14 Aug, 2009 1 commit
  22. 08 Aug, 2009 1 commit
  23. 20 Jul, 2009 1 commit
  24. 13 May, 2009 1 commit
  25. 12 May, 2009 1 commit
    • Wim Taymans's avatar
      codecmap: revert bogus commit. · 92b8a5ad
      Wim Taymans authored
      We don't need to set a default frame_size, ffmpeg has set this value to 0 to
      inform us that there is a fixed relation between the amount of input samples
      and output samples. Now we only need to implement handling that fact.
      92b8a5ad
  26. 17 Apr, 2009 1 commit
    • Wim Taymans's avatar
      ffmpeg: add default frame_size for g726 · 11db4588
      Wim Taymans authored
      Without a frame_size configured in the context, the ffmpeg encoders do nothing.
      Since the G726 does not configure a size itself, we set ourselves a frame_size
      that corresponds to 20ms of audio, which is a reasonable default.
      11db4588
  27. 15 Apr, 2009 1 commit
  28. 17 Mar, 2009 1 commit
  29. 11 Mar, 2009 1 commit
  30. 10 Mar, 2009 1 commit
  31. 09 Mar, 2009 1 commit
  32. 05 Mar, 2009 2 commits
  33. 04 Mar, 2009 1 commit
  34. 27 Feb, 2009 1 commit
  35. 22 Feb, 2009 2 commits