1. 28 Aug, 2015 1 commit
  2. 26 Aug, 2015 3 commits
  3. 25 Aug, 2015 3 commits
  4. 24 Aug, 2015 7 commits
  5. 23 Aug, 2015 3 commits
  6. 21 Aug, 2015 5 commits
  7. 20 Aug, 2015 3 commits
  8. 16 Aug, 2015 4 commits
  9. 15 Aug, 2015 4 commits
    • Martin Storsjö's avatar
      libfdk-aacdec: Clean up properly if the init fails · f34b152e
      Martin Storsjö authored
      Previously most of the error paths leaked.
      
      Also add FF_CODEC_CAP_INIT_THREADSAFE while adding caps_internal;
      this decoder wrapper doesn't have any static data that is initialized.
      Signed-off-by: 's avatarMartin Storsjö <martin@martin.st>
      f34b152e
    • Martin Storsjö's avatar
      libfdk-aacdec: Always decode into an intermediate buffer · 1b90433f
      Martin Storsjö authored
      For ADTS streams, the output format (number of channels, frame size)
      can change at any point (with the latest version of fdk-aac, the decoder
      seems to change format after a handful of frames, not outputting the
      right format immediately, for cases that worked fine with the earlier
      version of the lib).
      
      Previously, the decoder decoded straight into the output frame once the
      number of channels and frame size was known. This obviously does not
      work if the number of channels or frame size changes.
      
      The alternative would be to allocate the AVFrame with the maximum number
      of channels and frame size, and change them afterward decoding into it,
      but that may cause confusion to users e.g. of the get_buffer callback.
      This solution should be more robust.
      
      CC: libav-stable@libav.org
      Signed-off-by: 's avatarMartin Storsjö <martin@martin.st>
      1b90433f
    • Martin Storsjö's avatar
      libfdk-aacdec: Bump the max number of channels to 8 · 87de6ddb
      Martin Storsjö authored
      In the latest version of fdk-aac, the decoder can output up to 8
      channels; take this into account when preallocating buffers that
      need to fit the output from any packet.
      
      CC: libav-stable@libav.org
      Signed-off-by: 's avatarMartin Storsjö <martin@martin.st>
      87de6ddb
    • Martin Storsjö's avatar
      configure: arm: Assume softfp ABI on darwin · cb2dbe2c
      Martin Storsjö authored
      Don't try to detect the float ABI by checking at the toolchain
      name or by trying to assemble and link files with eabi_attributes.
      
      This fixes the float ABI detection when building using clang
      with -fembed-bitcode, where the current eabi_attributes check
      accidentally passes.
      
      This issue was pointed out by James Howe <james.howe@hp.com>.
      
      CC: libav-stable@libav.org
      Signed-off-by: 's avatarMartin Storsjö <martin@martin.st>
      cb2dbe2c
  10. 13 Aug, 2015 1 commit
  11. 12 Aug, 2015 1 commit
    • Martin Storsjö's avatar
      movenc: Add a new flag for writing global sidx indexes for dash · 26ac22e5
      Martin Storsjö authored
      The double meaning of the faststart flag (moving a moov atom
      to the start of files, making them streamable, for non-fragmented
      files, vs inserting a global sidx index at the start of files
      for fragmented files) is confusing - see 40ed1cbf for
      explanation of its origins.
      
      Since the second meaning of the flag hasn't been part of any
      libav release yet, just rename it to get rid of the confusion
      without any extra deprecation (which wouldn't get rid of the
      potential confusion, of users adding -movflags faststart
      even for fragmented files, where it isn't needed for making
      them "streamable").
      
      This gets back the old behaviour, where -movflags faststart
      doesn't have any effect for fragmented files.
      Signed-off-by: 's avatarMartin Storsjö <martin@martin.st>
      26ac22e5
  12. 11 Aug, 2015 5 commits