1. 17 7月, 2014 1 次提交
  2. 09 7月, 2014 1 次提交
  3. 08 7月, 2014 1 次提交
  4. 05 7月, 2014 1 次提交
  5. 24 6月, 2014 1 次提交
  6. 20 6月, 2014 1 次提交
  7. 02 6月, 2014 1 次提交
  8. 01 6月, 2014 1 次提交
  9. 26 5月, 2014 1 次提交
  10. 20 5月, 2014 1 次提交
  11. 19 5月, 2014 1 次提交
    • V
      Add transformation matrix API. · bddd8cbf
      Vittorio Giovara 提交于
      Add AV_PKT_DATA_DISPLAYMATRIX and AV_FRAME_DATA_DISPLAYMATRIX as stream and
      frame side data (respectively) to describe a display transformation matrix
      for linear transformation operations on the decoded video.
      
      Add functions to easily extract a rotation angle from a matrix and
      conversely to setup a matrix for a given rotation angle.
      Signed-off-by: NAnton Khirnov <anton@khirnov.net>
      bddd8cbf
  12. 17 5月, 2014 1 次提交
    • O
      lavu: add av_gettime_relative() · 0eec06ed
      Olivier Langlois 提交于
      These functions are using the POSIX clock_gettime() function with the
      CLOCK_MONOTONIC clock id. If these are not present on the targeted
      platform, the new functions will fallback on using the original realtime functions
      av_gettime() and av_usleep().
      
      Monotonic support can be added on other platforms with their
      equivalent native system API eventually if possible.
      
      Whenever time is requested to measure relative time, the monotonic clock,
      when available, is superior to the system realtime clock because it is
      not affected by discontinuous jumps in the system time
      
      In a future step, offering the flexibility to let the user choose between
      rt and monotonic clock for avdevices packets will be investigated.
      
      It is very easy to experience the issues that this patch attempt to address
      by rewinding back in the past the system time while ffmpeg is running.
      
      this is breaking the ffmpeg report printing (ffmepg.c:print_report()) and
      the the rate emulator functionality (-re) without the patch.
      Signed-off-by: NOlivier Langlois <olivier@trillion01.com>
      Signed-off-by: NMichael Niedermayer <michaelni@gmx.at>
      0eec06ed
  13. 14 5月, 2014 1 次提交
  14. 11 5月, 2014 1 次提交
  15. 08 5月, 2014 1 次提交
  16. 03 5月, 2014 1 次提交
  17. 29 4月, 2014 1 次提交
  18. 27 4月, 2014 1 次提交
  19. 23 4月, 2014 2 次提交
  20. 18 4月, 2014 1 次提交
  21. 13 4月, 2014 1 次提交
  22. 08 4月, 2014 1 次提交
  23. 04 4月, 2014 1 次提交
    • A
      replaygain: correctly parse peak values · 8542f9c4
      Alessandro Ghedini 提交于
      According to the ReplayGain spec, the peak amplitude may overflow and may result
      in peak amplitude values greater than 1.0 with psychoacoustically coded audio,
      such as MP3. Fully compliant decoders must allow peak overflows.
      
      Additionally, having peak values in the 0<->UINT32_MAX scale makes it more
      difficult for applications to actually use the peak values (e.g. when
      implementing clipping prevention) since values have to be rescaled down.
      
      This patch corrects the peak parsing by removing the rescaling of the decoded
      values between 0 and UINT32_MAX and the 1.0 upper limit.
      Signed-off-by: NAnton Khirnov <anton@khirnov.net>
      8542f9c4
  24. 03 4月, 2014 2 次提交
  25. 01 4月, 2014 1 次提交
  26. 29 3月, 2014 1 次提交
  27. 24 3月, 2014 2 次提交
  28. 17 3月, 2014 1 次提交
  29. 04 3月, 2014 1 次提交
  30. 24 2月, 2014 1 次提交
  31. 20 2月, 2014 2 次提交
  32. 16 2月, 2014 1 次提交
  33. 07 2月, 2014 1 次提交
  34. 20 1月, 2014 1 次提交
  35. 05 1月, 2014 2 次提交