Recherche avancée

Sur d’autres sites (6816)

• Try out the latest Piwik 3.0.0 beta version : Piwik 3.0.0 is almost here !

  15 novembre 2016, par Matthieu Aubry — Uncategorized

  Dear Piwik community,

  We are excited today to announce our publicly available Piwik 3.0.0 beta 3 release. We have been been working hard behind the scenes on the new 3.0.0 release for almost one year now. We, the passionate team at Piwik, are dedicated to bringing you a new and improved Piwik experience and invite you to join our beta channel to switch to Piwik 3 today !

  Enable the beta release channel

  Ready to enjoy a much faster Piwik experience and the magic of a modern user interface ? Follow the instructions here and you can upgrade to Piwik 3.0.0 beta in just one click.

  Please note that beta versions have a risk of containing bugs so we don’t recommend to use on a production server. If you find and report a bug in a beta version, we will aim to fix it as quickly as possible.

  Premium plugins in Piwik 3

  In the Piwik Marketplace you can discover & download plugins to enrich the functionality of your Piwik, as well as themes to change the look and feel of your Piwik user interface. The Marketplace integration was much improved in this new release, most notably : you can now purchase and download Premium plugins within Piwik !

  Important changes

  The Piwik 3 upgrade comes with some important changes that may require your attention which we detail in this blog post and in the developer changelog.

  The full list of more than 150 changes can be found in the Piwik 3 beta changelogs : beta 1, beta 2, beta 3.

  What to do next

  When you use the Piwik beta channel and if you come across any issues in Piwik such as a bug, feature missing, regression… let us know on our tracker and create a new issue so we can get this sorted.

  As we are in the final days of Piwik 3 development, we are looking forward to your feedback and help testing !

  Welcome to the future of Piwik,

  Happy Analytics !

• Using lcov With FFmpeg/Libav

  21 novembre 2011, par Multimedia Mike — Programming, code coverage, ffmpeg, lcov, libav

  Last year, I delved into code coverage tools and their usage with FFmpeg. I learned about using GNU gcov, which is powerful but pretty raw about the details it provides to you. I wrote a script to help interpret its output and later found another script called gcovr to do the same, only much better.

  I later found another tool called lcov which is absolutely amazing for understanding code coverage of your software. I’ve been meaning to use it to further FATE test coverage for the multimedia projects.

  
  
  Click for larger image
  

  Basic Instructions
  Install the lcov tool, of course. In Ubuntu, 'apt-get install lcov' will do the trick.

  Build the project with code coverage support, i.e.,

  ./configure —enable-gpl —samples=/path/to/fate/samples \
   —extra-cflags="-fprofile-arcs -ftest-coverage" \
   —extra-ldflags="-fprofile-arcs -ftest-coverage"
  make
  

  Clear the coverage data :

  lcov —directory . —zerocounters
  

  Run the software (in this case, the FATE test suite) :

  make fate
  

  Let lcov work its magic :

  lcov —directory . —capture —output-file coverage.info
  mkdir html-output
  genhtml -o html-output coverage.info
  

  At this point, you can aim your web browser at html-output/index.html to learn everything you could possibly want to know about code coverage of the test suite. You can sort various columns in order to see which modules have the least code coverage. You can drill into individual source files and see highlighted markup demonstrating which lines have been executed.

  As you can see from the screenshot above, FFmpeg / Libav are not anywhere close to full coverage. But lcov provides an exquisite roadmap.

• avcodec : Remove libstagefright

  3 janvier 2016, par Derek Buitenhuis

  avcodec : Remove libstagefright
  It serves absolutely no purpose other than to confuse potentional
  
  Android developers about how to use hardware acceleration properly
  
  on the the platform. The stagefright "API" is not public, and the
  
  MediaCodec API is the proper way to do this.
  Furthermore, stagefright support in avcodec needs a series of
  
  magic incantations and version-specific stuff, such that
  
  using it actually provides downsides compared just using the actual
  
  Android frameworks properly, in that it is a lot more work and confusion
  
  to get it even running. It also leads to a lot of misinformation, like
  
  these sorts of comments (in [1]) that are absolutely incorrect.
  [1] http://stackoverflow.com/a/29362353/3115956
  Signed-off-by : Derek Buitenhuis <derek.buitenhuis@gmail.com>
  

  • [DH] Changelog
  • [DH] MAINTAINERS
  • [DH] configure
  • [DH] libavcodec/Makefile
  • [DH] libavcodec/allcodecs.c
  • [DH] libavcodec/libstagefright.cpp
  • [DH] libavcodec/version.h
  • [DH] tools/build_libstagefright