Recherche avancée

Sur d’autres sites (7360)

• avcodec : Remove libaacplus

  24 janvier 2016, par Timothy Gu

  avcodec : Remove libaacplus
  TODO : bump minor
  It’s inferior in quality to fdk-aac and has an arguably more problematic
  
  license.
  As early as 2012, a HydrogenAudio user reported :
  > It has however one huge advantage : much better quality at low bitrates than
  
  > faac and libaacplus.
  (https://hydrogenaud.io/index.php?PHPSESSID=ckiq394pdglka0kj2fin6ij8t7&topic=95989.msg804633#msg804633)
  I myself have made a few spectrograms for a comparison of the two
  
  encoders as well. The FDK output is consistently better than the
  
  libaacplus one, in all bitrates I tested.
  libaacplus license is 3GPP + LGPLv2. 3GPP copyright notice is completely
  
  proprietory, as follows :
  > No part may be reproduced except as authorized by written permission.
  
  >
  
  > The copyright and the foregoing restriction extend to reproduction in
  
  > all media.
  
  >
  
  > © 2008, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC).
  
  >
  
  > All rights reserved.
  (The latest 26410-d00 zip from 3GPP has the same notice, but the copyright
  
  year is changed to 2015)
  The copyright part of the FDK AAC license (section 2) is a copyleft
  
  license that permits redistribution under certain conditions (and
  
  therefore the LGPL + libfdk-aac combination is not prohibited by
  
  configure) :
  > Redistribution and use in source and binary forms, with or without
  
  > modification, are permitted without payment of copyright license fees
  
  > provided that you satisfy the following conditions :
  
  >
  
  > You must retain the complete text of this software license in
  
  > redistributions of the FDK AAC Codec or your modifications thereto in
  
  > source code form.
  
  >
  
  > You must retain the complete text of this software license in the
  
  > documentation and/or other materials provided with redistributions of
  
  > the FDK AAC Codec or your modifications thereto in binary form.
  
  >
  
  > You must make available free of charge copies of the complete source
  
  > code of the FDK AAC Codec and your modifications thereto to recipients
  
  > of copies in binary form.
  
  >
  
  > The name of Fraunhofer may not be used to endorse or promote products
  
  > derived from this library without prior written permission.
  
  >
  
  > You may not charge copyright license fees for anyone to use, copy or
  
  > distribute the FDK AAC Codec software or your modifications thereto.
  
  >
  
  > Your modified versions of the FDK AAC Codec must carry prominent
  
  > notices stating that you changed the software and the date of any
  
  > change. For modified versions of the FDK AAC Codec, the term
  
  > "Fraunhofer FDK AAC Codec Library for Android" must be replaced by the
  
  > term "Third-Party Modified Version of the Fraunhofer FDK AAC Codec
  
  > Library for Android."
  

  • [DH] Changelog
  • [DH] LICENSE.md
  • [DH] configure
  • [DH] doc/general.texi
  • [DH] doc/platform.texi
  • [DH] libavcodec/Makefile
  • [DH] libavcodec/allcodecs.c
  • [DH] libavcodec/libaacplus.c

• ffmpeg compilation problem : avcodec_find_decoder always returns null

  15 mars 2016, par Adion

  I recently tried to upgrade the ffmpeg libraries I use in my Mac OS X application by downloading and compiling ffmpeg from source.

  My code works correctly with pre-compiled libraries of the same version on windows.
  On Mac OS X, the library appears to work (it can open the file and find the streams and codecs used), but when it gets to avcodec_find_decoder, this function always returns null.

  The code has worked with an older version of the library (compiled a year ago on Mac OS X 10.5)

  I configured fmpeg using

  ./configure --extra-cflags="-arch i386" --extra-ldflags='-arch i386' --arch=x86_32 --target-os=darwin --enable-cross-compile --disable-indev=jack --enable-shared --disable-static

  I checked config.mak, and it appears to have the decoders for the file types I tried enabled (ogg, vorbis, avi, mkv, ...)
  I also checked that the correct header files have been used and that the newly compiled library is used.

  I have found only some older posts relating to this issue, but without any solution :

  http://lists.mplayerhq.hu/pipermail/ffmpeg-devel/2007-January/021399.html

  http://libav-users.943685.n4.nabble.com/avcodec-find-decoder-problem-td944800.html

  Edit : checking further, it appears av_codec_next(NULL) returns null as well, which means there isn’t a single codec available, or that first_avcodec in utils.c is not set (I actually haven’t found at all where this variable is set, I would have assumed av_register_all, but I can’t find it there)

• Announcing Long Term Support in Piwik 2 – The analytics platform for your mission critical projects

  11 janvier 2016, par Matthieu Aubry — About, Development

  We are proud to announce our Long Term Support (LTS) for Piwik 2.X !

  Why Long Term Support (LTS) ?

  Part of our mission is to ready Piwik for the enterprise — and ready the enterprise for Piwik. Our fast release cycle and our ability to quickly innovate has served us well for the past seven years and has lead Piwik to being one of the most popular open source projects, used by over one million websites worldwide. But Piwik’s success today has also shown us that this fast release cycle is not suited for all users and customers. Like most large open source projects (such as Ubuntu, Firefox, Debian, Symfony, Node.js, etc.) at Piwik we now also offer a Long Term Support release which gives users the confidence that Piwik can be used for mission critical projects for months to come.

  What does LTS mean for Piwik ?

  For the duration of the LTS period, Piwik 2.X will continue to receive the following fixes :

  • Critical bugs causing data loss or data corruption.
  • Major and Critical security issues.

  Our goal is to offer you a Piwik LTS release that you can trust for all your mission critical projects.

  How long will Piwik 2.X be supported ?

  Piwik 2.X will be supported for at least 12 months after the initial release of Piwik 3.0.0.
  Piwik 3.0.0 is expected to be released in the second half of 2016.
  This means that Piwik 2.X will be supported at least until the second half of 2017.

  Which Piwik version is LTS ?

  The latest Piwik 2.16.X release is our Long Term Support version.

  How do I benefit from the LTS version ?

  To get the full benefits of Piwik LTS, please make sure you are using the latest LTS version. First, update to the latest Piwik 2.X version, then Configure Piwik to use the LTS release channel and then update to the latest LTS version.

  How do I configure Piwik to use the LTS version ?

  By default, Piwik will not use the LTS version. When you use the one-click update your Piwik instance will be updated to the very latest release : when Piwik 3.0.0 will be released, the one click update will update your instance to 3.0.0. It is however possible to configure your Piwik so that you will stay on Piwik 2.X and keep using the LTS Long Term Support version :

  • Login Piwik as the Super User,
  • Go to Settings > General > Update settings,
  • Under “Release channel” click “Latest stable 2.X Long Term Support version”, and click “Save”.
    

  How do I get professional Piwik Support ?

  If you need professional support for your Piwik service get in touch with the Piwik PRO experts.

  ---

  For other questions, feedback or discussion, feel free to join our forums and comment on this LTS forum post.

  We wish you all a fantastic year 2016 !