Recherche avancée

Sur d’autres sites (9012)

• anyone had success with OpenFP ? [closed]

  30 mai 2013, par Robert Shaw

  http://sourceforge.net/projects/open-fp/

  Built and ran openfp - a sound fingerprinting project available in many places. Includes :
  openfp_extract (calls ffmpeg) _server and _match.

  Hours today fiddling with the samples but I always get MATCH RESULTS 0, even with identical afp files in the signatures directory. What is the trick to get a match ?

  Usings PCM 16 mono 22kHz . Do endian and signed matter as long as its always the same ?

  I hope to try and match bird or animal sounds, anybody think it can work ?

  Thanks in advance ! - Robert

• Find frame in video using ffmpeg

  11 février 2020, par Tom

  I have an image saved as 1.jpg and I want to find frames similar to this image in a video and get frame numbers of these frames or timestamps.
  This command can find similar images but it outputs results in a hard-to-parse format. How can I fix this command to just get the similar frames and no other information ?

  ffmpeg.exe  -i "1.mkv" -r 1 -loop 1 -i 1.jpg -an -filter_complex "blend=difference:shortest=1,blackframe=99:32" -f null -

• avcodec : disallow hwaccel with frame threads

  23 octobre 2015, par Hendrik Leppkes

  avcodec : disallow hwaccel with frame threads
  HWAccels with frame threads are fundamentally flawed in avcodecs current
  
  design, and there are several known problems ranging from image corruption
  
  to driver crashes.
  These problems come down to two design problems in the interaction of
  
  threads and HWAccel decoding :
  (1)
  
  While avcodec prevents parallel decoding and as such simultaneous access
  
  to the hardware accelerator from the decoding threads, it cannot account
  
  for the user code and its access to the hardware surfaces and the hardware
  
  itself.
  This can result in image corruption or even driver crashes if the
  
  user code locks image surfaces while they are being used by the decoder
  
  threads as reference frames.
  The current HWAccel API does not offer any way to ensure exclusive access
  
  to the hardware or the surfaces if frame threading is used.
  (2)
  
  Initialization of the HWAccel with frame threads is non-trivial, and many
  
  decoders had and still have issues that cause excess calls to the
  
  get_format callback.
  This will potentially cause duplicate HWAccel initialization, which in
  
  extreme cases can even lead to driver crashes if the HWAccel is
  
  re-initialized while the user code is actively accessing the hardware
  
  surfaces associated with it, or lead to image corruption due to lost
  
  reference frames.
  While both of these issues are solvable, fixing (1) would at least require
  
  a huge API redesign which would move a lot of complexity into the user
  
  code.
  The only reason the combination of frame threads and HWAccel was
  
  considered useful is to allow a seamless fallback to multi-threaded
  
  software decoding if the HWAccel is not available, however the issues
  
  outlined above far outweigh this.
  The proper solution for a fallback is to re-open the AVCodecContext with
  
  threading enabled if the HWAccel failed, which is a practice commonly used
  
  by various user applications using avcodec today already.
  Reviewed-by : Gwenole Beauchesne <gb.devel@gmail.com>
  
  Reviewed-by : wm4 <nfxjfg@googlemail.com>
  
  Signed-off-by : Hendrik Leppkes <h.leppkes@gmail.com>
  

  • [DH] libavcodec/utils.c