Recherche avancée

Sur d’autres sites (7260)

• FFMpeg, rtsp cameras and series of bad framses

  21 avril 2022, par Denis Gottardello

  I have a problem with ffmpeg and rtsp cameras.
As you can see in the screenshot below

  


  

  


  sometimes a serie of damaged frames come.
It is not a problem related to camera. The date and time is unreadable and the problem happens with different vendors of camera, with differen pcs and in different places.With the official software the live is perfect.
I'm trying with the lates ffmpeg source (5.0.1) in a Debian 11 machine.
I'm particolar intertested in this problem because I have written a software based on ffpmeg library and I have the same problem (using ffmpeg as library), in bouth Windows and Linux.

  


  This is the command line to record

  


  


  


  ./ffmpeg -i rtsp://192.168.1.11:554/onvif1  a.avi

  


  


  



  What can I do to resolve ?

  


• ONVIF Device Manager API and Decoder

  10 juillet 2023, par spiderelite

  I'm working on the source code of the onvif device manager software and I want to find the Api and decoder it uses.

  


  I first separated the odm.player part of the code into another solution and built it separately. the separated part contains these parts from the source code (in order of execution) :

  


  utils.linq
utils.diagnostics
utils.common
odm.player.lib
odm.player.media
live555
odm.player.net
utils.xml
utils.bootstrapping
odm.player.host


  


  Im tring to find the decoder and Api it uses(in the above parts) to decode the media. i need to find the specific part of the program to contain some information from a decoder.

  


  I know the source code is using ffmpeg and live555 libraries but I need to find their use and API in the odm.player part.

  


  I checked odm.player.host because it is the last project and depends on previous ones, but didn't find anything.

  


  what should i do next ? is there any official documentation of the API ? is there any important keyword related to ffmpeg that can I search it in the code ?

  


• libavcodec/qsvenc.c delay in 1 microsecond replaced to more appropriate 500 microseconds

  28 juillet 2015, par Ivan Uskov

  libavcodec/qsvenc.c delay in 1 microsecond replaced to more appropriate 500 microseconds
  This commit replaces the 1 microsecond delay by 500 microsecond for the
  
  case when the MFX library does return MFX_WRN_DEVICE_BUSY status.
  
  In general this warning never appears for simple encoding or
  
  transcoding session because the GPU is so fast so it almost always is not busy and
  
  any delay value just does not executes.
  
  But for heavy transcoding tasks for example, when several QSV sessions
  
  are running simultaneously then using a 1-microsecond delay may
  
  result in 1000 iterations per each frame.
  
  So here possible a paradoxical case when GPU loading also loads CPU by dummy tasks.
  
  Official MFX/QSV samples by Intel are using 1 millisecond (i.e. 1000
  
  microseconds) everywhere where MFX_WRN_DEVICE_BUSY does appear.
  
  So 500us is a much more optimal value than 1us.
  Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>
  

  • [DH] libavcodec/qsvenc.c