1. 16 Nov, 2012 1 commit
  2. 07 Nov, 2012 2 commits
  3. 16 Oct, 2012 1 commit
  4. 15 Oct, 2012 1 commit
  5. 03 Oct, 2012 1 commit
  6. 01 Oct, 2012 3 commits
  7. 28 Sep, 2012 1 commit
  8. 27 Sep, 2012 2 commits
  9. 26 Aug, 2012 1 commit
  10. 26 Jul, 2012 1 commit
  11. 25 Jun, 2012 1 commit
  12. 29 May, 2012 1 commit
  13. 17 May, 2012 2 commits
    • Mans Rullgard's avatar
      pcmenc: set correct bitrate value · 7d7b40f4
      Mans Rullgard authored
      This fixes a bogus bitrate value in the header of WAV files with
      alaw/ulaw audio.
      Signed-off-by: 's avatarMans Rullgard <mans@mansr.com>
      7d7b40f4
    • Anton Khirnov's avatar
      ffmpeg: add support for audio filters. · fc49f22c
      Anton Khirnov authored
      Some of the FATE changes are due to off-by-one different rounding being used
      (lrintf vs av_rescale_q).
      Some fate changes are due to 1 audio frame less being encoded (the new variant seems
      matching what qatar does and according to ffprobe its closer to the requested duration)
      the mapchan feature sadly is lost in this commit because it depends on resampling
      being done in ffmpeg.c which is now moved completely into the av filter layer
      -async is broken after this commit, this will be fixed in subsequent commits
      the new filter reconfiguration system is flawed and will drop a frame on each
      parameter change which is why the nelly moser checksums need updating.
      
      Conflicts:
      
      	ffmpeg.c
      	tests/ref/fate/smjpeg
      fc49f22c
  14. 04 May, 2012 1 commit
  15. 01 May, 2012 1 commit
  16. 24 Apr, 2012 1 commit
    • Justin Ruggles's avatar
      FATE: avoid channel mixing in lavf-dv_fmt · c5671aeb
      Justin Ruggles authored
      This partially reverts acb17302
      which would only have needed to change the checksums if channel mixing had
      been properly avoided. This changes the output file size reference and the
      seek test reference back to the previous values.
      c5671aeb
  17. 23 Apr, 2012 1 commit
    • Dale Curtis's avatar
      matroska: Add incremental parsing of clusters. · 8336eb6f
      Dale Curtis authored
      Reduces the amount of upfront data required for cluster parsing
      thus decreasing latency on seek and startup.
      
      The change in the seek-lavf_mkv FATE test is due to incremental
      parsing no longer reading as much data as the old parser and
      thus not having that additional data to generate index entries
      based on keyframes.  Index entries are added correctly as the
      file is parsed.
      
      All FATE tests pass and Chrome has been using this patch for ~6
      months without issue.
      
      Currently incremental parsing is not supported for files with
      SSA tracks since they require merging packets between clusters.
      In this case the code falls back to non-incremental parsing.
      Signed-off-by: 's avatarAaron Colwell <acolwell@chromium.org>
      Signed-off-by: 's avatarDale Curtis <dalecurtis@chromium.org>
      Signed-off-by: 's avatarLuca Barbato <lu_zero@gentoo.org>
      8336eb6f
  18. 20 Apr, 2012 3 commits
  19. 05 Apr, 2012 1 commit
  20. 20 Mar, 2012 2 commits
  21. 17 Mar, 2012 1 commit
  22. 16 Mar, 2012 1 commit
  23. 09 Mar, 2012 1 commit
  24. 05 Mar, 2012 1 commit
    • Justin Ruggles's avatar
      aiffdec: do not set AVCodecContext.frame_size · 8d1a20aa
      Justin Ruggles authored
      It is unnecessary. Also, for some codecs we're reading more than 1 frame per
      packet. Instead we use a private context variable to calculate the bit rate,
      stream duration, and packet durations.
      
      Updated FATE seek test, which has slightly different timestamps due to a
      more accurate bit rate calculation.
      8d1a20aa
  25. 03 Mar, 2012 2 commits
  26. 26 Feb, 2012 1 commit
  27. 13 Feb, 2012 1 commit
  28. 11 Feb, 2012 2 commits
  29. 07 Feb, 2012 1 commit
    • Anton Khirnov's avatar
      avconv: rework -t handling for encoding. · 1270e12e
      Anton Khirnov authored
      Current code compares the desired recording time with InputStream.pts,
      which has a very unclear meaning. Change the code to use actual
      timestamps of the frames passed to the encoder.
      
      In several tests, one less frame is encoded, which is more correct.
      
      In the idroq test one more frame is encoded, which is again more
      correct.
      
      Behavior with stream copy should be unchanged.
      1270e12e
  30. 02 Feb, 2012 1 commit