Recherche avancée

Sur d’autres sites (7257)

• FFMPEG : av_read_frame() return error AVERROR_EXIT ?

  19 mai 2015, par TTGroup

  I’m using FFMPEG to decode H264 stream from IP Camera. Sometimes the function av_read_frame() return error AVERROR_EXIT.

  I tested with two cameras. In here, the camera in LAN network worked fine with no error, but the camera in WAN network usually return AVERROR_EXIT.

  I have searched on the internet, but I didn’t find the solution yet.

  Someone can show me the problem ?

  Thanks,

  T&T

• lavf : move TLS-related ifdeffery to library specific files

  26 mai 2015, par wm4

  lavf : move TLS-related ifdeffery to library specific files
  There is no need to have this mess in network.c.
  Signed-off-by : Martin Storsjö <martin@martin.st>
  

  • [DH] libavformat/network.c
  • [DH] libavformat/tls.h
  • [DH] libavformat/tls_gnutls.c
  • [DH] libavformat/tls_openssl.c

• avformat : make avformat_network_init() explicitly optional

  16 janvier 2018, par wm4

  avformat : make avformat_network_init() explicitly optional
  It was sort of optional before - if you didn't call it, networking was
  
  initialized on demand, and an ugly warning was logged. Also, the doxygen
  
  comments threatened that it would be made strictly required one day.
  Make it explicitly optional. I would prefer to deprecate it fully, but
  
  there might still be legitimate reasons to use this. But the average
  
  user won't need it.
  This is needed only for two reasons : to initialize TLS libraries like
  
  OpenSSL and GnuTLS, and winsock.
  OpenSSL and GnuTLS were already silently initialized on demand if the
  
  global network init function was not called. They also have various
  
  thread-safety acrobatics, which make concurrent initialization within
  
  libavformat safe. In addition, the libraries are moving towards making
  
  their global init functions safe, which removes all need for central
  
  global init. In particular, GnuTLS 3.5.16 and OpenSSL 1.1.0g have been
  
  found to have safe init functions. In all cases, they use internal
  
  reference counters to avoid that the global uninit functions interfere
  
  with concurrent uses of the library by other API users who called global
  
  init.
  winsock should be thread-safe as well, and maintains an internal
  
  reference counter as well.
  Since we still support ancient TLS libraries, which do not have this
  
  fixed, and since it's unknown whether winsock and GnuTLS
  
  reinitialization is costly in any way, don't deprecate the libavformat
  
  functions yet.
  

  • [DH] doc/APIchanges
  • [DH] libavformat/avformat.h
  • [DH] libavformat/network.c
  • [DH] libavformat/network.h
  • [DH] libavformat/utils.c
  • [DH] libavformat/version.h