1. 30 Sep, 2012 1 commit
    • Stefano Sabatini's avatar
      ffprobe: extend disposition printing support · 301f6da0
      Stefano Sabatini authored
      This generalizes the previous work on disposition printing.
      
      Disposition flags are shown in a dedicated section, which should improve
      output intellegibility, extensibility and filtering operations.
      
      This breaks output syntax with the recently introduced disposition
      printing.
      301f6da0
  2. 27 Sep, 2012 1 commit
  3. 24 Sep, 2012 1 commit
  4. 23 Sep, 2012 1 commit
  5. 22 Sep, 2012 1 commit
  6. 20 Sep, 2012 1 commit
  7. 17 Sep, 2012 1 commit
  8. 15 Sep, 2012 1 commit
    • Ben Jackson's avatar
      lavc/vp6: Implement "slice" threading for VP6A decode · 39a3894a
      Ben Jackson authored
      The YUV channels of VP6 are encoded in a highly linear fashion which does
      not have any slice-like concept to thread.  The alpha channel of VP6A is
      fairly independent of the YUV and comprises 40% of the work.  This patch
      uses the THREAD_SLICE capability to split the YUV and A decodes into
      separate threads.
      
      Two bugs are fixed by splitting YUV and alpha state:
      - qscale_table from VP6A decode was for alpha channel instead of YUV
      - alpha channel filtering settings were overwritten by YUV header parse
      Signed-off-by: 's avatarBen Jackson <ben@ben.com>
      Signed-off-by: 's avatarMichael Niedermayer <michaelni@gmx.at>
      39a3894a
  9. 08 Sep, 2012 1 commit
  10. 07 Sep, 2012 1 commit
  11. 06 Sep, 2012 1 commit
  12. 04 Sep, 2012 1 commit
    • Michael Niedermayer's avatar
      adpcmenc: Calculate the IMA_QT predictor without overflow · aa264da5
      Michael Niedermayer authored
      Previously, the value given to put_bits was 10 bits long for positive
      predictors, even though 9 bits were to be written. The extra bit could
      in some cases overwrite existing bits in the bitstream writer cache.
      
      This fixes a failed assert in put_bits.h, when running a version
      built with -DDEBUG.
      
      The fate test result gets slightly improved, thanks to getting rid
      of the overwritten bits in the bitstream writer cache.
      Signed-off-by: 's avatarMartin Storsjö <martin@martin.st>
      aa264da5
  13. 02 Sep, 2012 1 commit
  14. 01 Sep, 2012 2 commits
  15. 30 Aug, 2012 1 commit
  16. 28 Aug, 2012 1 commit
  17. 26 Aug, 2012 1 commit
  18. 25 Aug, 2012 1 commit
  19. 22 Aug, 2012 2 commits
  20. 21 Aug, 2012 2 commits
  21. 20 Aug, 2012 1 commit
  22. 16 Aug, 2012 1 commit
  23. 14 Aug, 2012 2 commits
  24. 10 Aug, 2012 1 commit
  25. 09 Aug, 2012 2 commits
  26. 08 Aug, 2012 1 commit
  27. 05 Aug, 2012 1 commit
  28. 04 Aug, 2012 2 commits
    • Philip Langdale's avatar
      movtextenc: 3GPP TS 26.245 Timed Text Encoder. · 2daaf776
      Philip Langdale authored
      This change introduces a basic encoder for 3GPP Timed Text subtitles,
      also known as TX3G, Quicktime subtitles, or "movtext" in the existing
      code.
      
      This initial change doesn't attempt to write styling information,
      and just writes the plain text of the subtitles. I intend to add
      support for styles eventually, but it's challenging due to a lack
      of existing players that support them.
      
      Note that an additional change is required to the mov/mp4 muxer to
      write empty subtitle packets to indicate subtitle duration.
      Signed-off-by: 's avatarPhilip Langdale <philipl@overt.org>
      2daaf776
    • Ronald S. Bultje's avatar
      fate: add tests for lagarith lossless video codec. · c5d5d178
      Ronald S. Bultje authored
      Based on patch by Oana Stratulat <oanaandreeastratulat@gmail.com>.
      c5d5d178
  29. 03 Aug, 2012 1 commit
  30. 30 Jul, 2012 2 commits
  31. 29 Jul, 2012 1 commit
    • Anton Khirnov's avatar
      lavf: deprecate r_frame_rate. · aba232cf
      Anton Khirnov authored
      According to its description, it is supposed to be the LCM of all the
      frame durations. The usability of such a thing is vanishingly small,
      especially since we cannot determine it with any amount of reliability.
      Therefore get rid of it after the next bump.
      
      Replace it with the average framerate where it makes sense.
      
      FATE results for the wtv and xmv demux tests change. In the wtv case
      this is caused by the file being corrupted (or possibly badly cut) and
      containing invalid timestamps. This results in lavf estimating the
      framerate wrong and making up wrong frame durations.
      In the xmv case the file contains pts jumps, so again the estimated
      framerate is far from anything sane and lavf again makes up different
      frame durations.
      
      In some other tests lavf starts making up frame durations from different
      frame.
      aba232cf
  32. 28 Jul, 2012 2 commits