Recherche avancée

Sur d’autres sites (12038)

• New FATE Test Coverage System

  10 août 2010, par Multimedia Mike — FATE Server

  I’ve been feeling a bit scattered for the last week since I was fired from my volunteer position as the FFmpeg QA manager, wondering if there is anything I should attempt to do with the project. It can’t be denied that the new system is working well. But one area I’ve wondered about is test coverage.

  Under my old regime I tracked test coverage as a wiki page which was a highly flawed method— tedious and error-prone. There are those 2 adjectives again— tedious and error-prone ; whenever I see those, I search for automation methods. I think that might be more plausible thanks to the new FATE’s tighter integration with the FFmpeg build system.

  I don’t think anyone is working on this problem so I wanted to toss out a brainstorm :

  1. First, run ’ffmpeg -formats’, ’ffmpeg -codecs’, etc. and parse the output to collect a list of all the features (full list : -formats, -codecs, -bsfs, -protocols, -filters, -pix_fmts). Transform these lists into a standardized list of features, e.g., "DEVSD  ffvhuff         Huffyuv FFmpeg variant" represents features ’decode-video-ffvhuff’, ’encode-video-ffvhuff’, ’ffvhuff-horizband’, and ’ffvhuff-dr1’.
  2. Next, tag each individual test spec with the features that it exercises. E.g., test ’fate-vqa-cc’ exercises features ’demux-wsvqa’, ’decode-video-vqavideo’, and ’decode-audio-adpcm_ima_ws’.
  3. Finally, compare the data from parts 1 and 2. Print a list of all the features that are not exercised in FATE.

  I think a lot of this could be implemented at the GNU make level. Then again, I’m no expert on GNU make syntax so I may be overestimating its capabilities. Or there might be simpler ways to automatically track test coverage stats based on the improved testing infrastructure.

• Can't split 24bit flac files on the command line [closed]

  21 mars 2023, par Martin

  I am trying to export a 24bit flac file in my ubuntu terminal. I've tried two different methods, but neither work.

  


  Method 1 : shntool

  


  when I run this command :
shntool split -f times.cue -O always -o lowq_full_silence.flac

  


  where lowq_full_silence.flac was rendered in audacity as a flac file with level=0 and bit depth=16 bit, my command works.

  


  but if i run this command :

  


  shntool split -f times.cue -O always -o full_hq.flac

  


  where full_hq.flac has level=8 and bit depth=24 bit
The command fails :

  


  shntool [split]: warning: unsupported format 0xfffe (Unknown) while processing file: [full_hq.flac]
shntool [split]: error: cannot continue due to error(s) shown above


  


  https://bugs.launchpad.net/ubuntu/+source/shntool/+bug/2000794

  


  Method 2 : ffmpeg

  


  Trying to split the flac file with comma separated 'split points' input

  


  ffmpeg -i "full_hq.flac" -c copy -map 0 -f segment -segment_times "22,441,556,559" "%d_output.flac"

  


  But the output from this ffmpeg command has broken length metadata :

  


  https://trac.ffmpeg.org/ticket/4905

  


  Is there a better way to split a high quality 24bit flac file into individual segments, where each exported segment file has correct length metadata ?

  


  Files :
https://file.io/lvGTUEgQArb7

  


• avcodec : add common fflcms2 boilerplate

  28 juin 2022, par Niklas Haas

  avcodec : add common fflcms2 boilerplate
  Handling this in general code makes more sense than handling it in
  
  individual codec files, because it would be a lot of unnecessary code
  
  duplication for the plenty of formats that support exporting ICC
  
  profiles (jpg, png, tiff, webp, jxl, ...).
  encode.c and decode.c will be in charge of initializing this state as
  
  needed, so we merely need to make sure to uninit it afterwards from the
  
  common destructor path.
  Signed-off-by : Niklas Haas <git@haasn.dev>
  

  • [DH] configure
  • [DH] libavcodec/Makefile
  • [DH] libavcodec/avcodec.c
  • [DH] libavcodec/decode.c
  • [DH] libavcodec/internal.h