Recherche avancée

Sur d’autres sites (8183)

• Using ffmpeg Silencedetect in C#

  11 septembre 2018, par jayjay

  I want to build a programm which splitts a long audio file into small peaces.
  I like to use ffmpeg silencedetect. From the console it works fine and returns the detected silence etc.
  Now i want to count many resulting tracks there are an gave the user the possibiliy to change the time parameter of the silencedetect function.
  I want to call the silencedetect function from C# code.
  But i don´t know how to work with the output in C#.

  Thank you for your help.

  Greetings Jan

• avcodec/omx : Fix handling of fragmented buffers

  17 janvier 2019, par Dave Stevenson

  avcodec/omx : Fix handling of fragmented buffers
  See https://trac.ffmpeg.org/ticket/7687
  If an encoded frame is returned split over two or more
  
  IL buffers due to the size, then there is a race between
  
  whether get_buffer will fail, return NULL, and a truncated
  
  frame is passed on, or IL will return the remaining part
  
  of the encoded frame.
  
  If get_buffer returns NULL, part of the frame is left behind
  
  in the codec, and will be collected on the next call. That
  
  then leaves a frame stuck in the codec. Repeat enough times
  
  and the codec FIFO is full, and the pipeline stalls.
  A performance improvement in the Raspberry Pi firmware means
  
  that the timing has changed, and now frequently drops into the
  
  case where get_buffer returns NULL.
  Add code such that should a buffer be received without
  
  OMX_BUFFERFLAG_ENDOFFRAME that get_buffer is called with wait
  
  set, so we wait for the remainder of the frame.
  
  This code has been made conditional on the Pi build in case
  
  other IL implementations don't handle ENDOFFRAME correctly.
  Signed-off-by : Dave Stevenson <dave.stevenson@raspberrypi.org>
  
  Signed-off-by : Aman Gupta <aman@tmm1.net>
  
  Signed-off-by : Martin Storsjö <martin@martin.st>
  

  • [DH] libavcodec/omx.c

• swscale/aarch64 : vscale optimization

  13 août 2022, par Swinney, Jonathan

  swscale/aarch64 : vscale optimization
  Use scalar times vector multiply accumlate instructions instead of
  
  vector times vector to remove the need for replicating load instructions
  
  which are slightly slower.
  On AWS c7g (Graviton 3, Neoverse V1) instances :
  
  yuv2yuvX_8_0_512_accurate_neon :  1144.8  987.4
  
  yuv2yuvX_16_0_512_accurate_neon : 2080.5 1869.4
  Signed-off-by : Jonathan Swinney <jswinney@amazon.com>
  
  Signed-off-by : Martin Storsjö <martin@martin.st>
  

  • [DH] libswscale/aarch64/output.S