Recherche avancée

Sur d’autres sites (4455)

• 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.

• On ALAC’s Open Sourcing

  1er novembre 2011, par Multimedia Mike — Codec Technology

  Apple open sourced their lossless audio codec last week. Pretty awesome ! I have a theory that, given enough time, absolutely every codec will be open source in one way or another.

  I know I shouldn’t bother reading internet conversation around any news related to multimedia technology. And if I do read it, I shouldn’t waste any effort getting annoyed about them. But here are some general corrections :

  • ALAC is not in the same league as — nor is it a suitable replacement for — MP3/AAC/Vorbis or any other commonly used perceptual audio codec. It’s not a matter of better or worse ; they’re just different families of codecs designed for different purposes.
  • Apple open sourced ALAC, not AAC– easy mistake, though there’s nothing to ‘open source’ about AAC (though people can, and will, argue about its absolute ‘open-ness’).
  • There’s not much technical room to argue between ALAC and FLAC, the leading open source lossless audio compressor. Both perform similarly in terms of codec speeds (screamingly fast) and compression efficiency (results vary slightly depending on source material).
  • Perhaps the most frustrating facet is the blithe ignorance about ALAC’s current open source status. While this event simply added an official “open source” status to the codec, ALAC has effectively been open source for a very long time. According to my notes, the ALAC decoding algorithm was reverse engineered in 2005 and added into FFmpeg in March of the same year. Then in 2008, Google — through their Summer of Code program — sponsored an open source ALAC encoder.

  From the multimedia-savvy who are versed in these concepts, the conversation revolves around which would win in a fight, ALAC or FLAC ? And who between Apple and FFmpeg/Libav has a faster ALAC decoder ? The faster and more efficient ALAC encoder ? I contend that these issues don’t really matter. If you have any experience working with lossless audio encoders, you know that they tend to be ridiculously fast to both encode and decode and that many different lossless codecs compress at roughly the same ratios.

  As for which encoder is the fastest : use whatever encoder is handiest and most familiar, either iTunes or FFmpeg/Libav.

  As for whether to use FLAC or ALAC — if you’ve already been using one or the other for years, keep on using it. Support isn’t going to vanish. If you’re deciding which to use for a new project, again, perhaps choose based on software you’re already familiar with. Also, consider hardware support– ALAC enjoys iPod support, FLAC is probably better supported in a variety of non-iPod devices, though that may change going forward due to this open sourcing event.

  For my part, I’m just ecstatic that the question of moral superiority based on open source status has been removed from the equation.

  Code-wise, I’m interested in studying the official ALAC code to see if it has any corner-case modes that the existing open source decoders don’t yet account for. The source makes mention of multichannel (i.e., greater than stereo) configurations, but I don’t know if that’s in FFmpeg/Libav.

• Evolution #2746 : Multilinguisme par secteur : manque d’ergonomie

  9 décembre 2015, par Guillaume Fahrner

  "Par ailleurs, quid du déplacement d’un article d’une rubrique en français dans l’anglaise ? ça change ça langue par héritage ?"
  Oui, idem pour n’importe quel objet, rubrique comprise (sauf les secteurs) :-)

  "Donc, il FAUT pouvoir changer la langue sur une base qui n’est pas saine au départ."

  Plusieurs solutions sans rien changer :
  - la langue est MAJ lors de l’édition d’un objet et est définie par héritage (pose le problème de la mise à jour de la date)
  - client mysql pour faire ca @mano