Recherche avancée

Sur d’autres sites (6983)

• Use FFMPEG to stream images from one client to another through IIS (or other) server

  20 avril 2012, par eselk

  I'm new to FFMPEG and maybe I should post this in their forums, but you guys here seem to know everything, so here goes. I have a client app that takes screen shots and saves them as images (256 color bitmaps currently, can change if needed), it does this at a rate of about 4 fps. I currently use my own socket code written in C# to push these to my socket server (also C#) running on a Windows 2008 server. That server then sends these images out to several clients that display them as they are received and also buffers them to allow for rewind, pause, etc, like a DVR. My current format requires approx 100KB per frame, and thus only works for a very small number of clients.

  I started looking at FFMPEG and the compression with MPEG1 and especially MPEG4 is amazing, and so is the quality. What I'm looking for is a basic guide, tutorial, or steps, to produce something similar to my current design, but using FFMPEG and actual video streaming. Ideally the player side could be something like Flash or anything that is easy to embed in a .NET WinForm (or a browser control I can host in the WinForm), and it would need to support buffering still so they can pause and rewind (about 5 or 10 mins, which seems like a lot, but remember this is only 4 fps and 256 color, about 1 or 2 MB per min in my testing).

  I see that FFMPEG, the command-line utility, and I assume the API, even has options for posting to a server via UDP or TCP, so maybe I'll use that instead of my own socket code. Ideally my app would feed images to FFMPEG library at a rate of 4fps as they come from the screen-shot unit, and it would send these up to my IIS server (or another server ?) which would then server them to client(s) that could use them similar to a YouTube video.

• avcodec/libdavs2 : workaround memory leak

  27 juin 2022, par Zhao Zhili

  avcodec/libdavs2 : workaround memory leak
  davs2_decoder_close doesn't free those on the fly frames which
  
  don't get output yet. It's a design bug, but easy to workaround.
  Before the patch :
  
  Direct leak of 1198606 byte(s) in 2 object(s) allocated from :
  
      #0 0x563af5e1e5f0 in malloc (ffmpeg+0x6675f0)
  
      #1 0x563af9765ef3 in davs2_malloc davs2/source/common/common.h:1240
  
      #2 0x563af9765ef3 in davs2_alloc_picture davs2/source/common/header.cc:815
  Indirect leak of 3595818 byte(s) in 6 object(s) allocated from :
  
      #0 0x563af5e1e5f0 in malloc (ffmpeg+0x6675f0)
  
      #1 0x563af9765ef3 in davs2_malloc davs2/source/common/common.h:1240
  
      #2 0x563af9765ef3 in davs2_alloc_picture davs2/source/common/header.cc:815
  Signed-off-by : Zhao Zhili <zhilizhao@tencent.com>
  

  • [DH] libavcodec/libdavs2.c

• 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