Recherche avancée

Sur d’autres sites (11248)

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

• Process stalls when launched in .NET (ffmpeg)

  13 octobre 2016, par Rhys Causey

  I’m trying to launch ffmpeg as a Process in .NET (C#), but in some cases, depending on the arguments (specifically, if I omit video arguments in order to create an audio file), it’s stalling. It launches, outputs some lines, but then just stalls (using 0% CPU). When the parent .NET process is killed, it continues, and if I let it continue, ffmpeg produces the file correctly. I thought it might be due to using Peek() to look at the stream, so I just simplified it to the following, which behaves the same :

  _process = new Process
  
  {
  
      StartInfo =
  
      {
  
          UseShellExecute = false,
  
          RedirectStandardOutput = false,
  
          RedirectStandardError = true,
  
          FileName = "c:\\ffmpeg.exe",
  
          Arguments = string.Format(
  
      "-i {0} {1} {2} {3} -y {4}", inputPath, videoArgs, audioArgs, options, outputPath)
  
      }
  
  };
  
  _process.Start();
  
  _process.WaitForExit();

  ffmpeg gets to the point where it outputs information about the input video/audio streams before stalling. Executing the command via the command prompt works as expected.

  Does anyone know what the problem could be ?

  Edit :

  Just to add, I tried UseShellExecute = true (and RedirectStandardError = false), and this works. I still need to read the output, however, so this doesn’t really help me.

• Merge remote-tracking branch ’qatar/master’

  5 janvier 2014, par Michael Niedermayer

  Merge remote-tracking branch ’qatar/master’
  * qatar/master :
  
    cmdutils : update copyright year to 2014.
  Conflicts :
  
  	cmdutils.c
  See : 0b1cfc4f28d81a8a49fdd5589b2eed06477abd61
  
  Merged-by : Michael Niedermayer <michaelni@gmx.at>