Recherche avancée

Sur d’autres sites (10138)

• How can i stop ffmpeg buffer from streaming ?

  23 juin 2020, par sniper

  I try to obtain a screenshoot for live streaming when websockets announce he need a screenshoot.

  


  At this moment I use this command for a subprocess on python :

  


  command = 'ffmpeg -ss 00:00:01 -i '+str(urllive)+' -vframes 1 -q:v 2 /var/www/html/ai/dist/img/'+str(canlive)+'.png -y'

  


  the script is working very well but this command is a for iteration, and execute the command for 7-12 times in less than 1 second.
The problem is when ffmpeg take the screenshoot start the streaming and take the buffer for this stream.
The buffer stream have around 7MB * 10(iteration) mean 70 MB, and load the network traffic with 70MB*8 = 560Mbps on that second.
How can i disable or reduce the buffer on ffmpeg client ?
  
I tried with bufsize 1M, -fflags nobuffer args but no success.

  


  ffmpeg version 3.4.6

  


• Stopping rq worker doesn't stop underlying ffmpeg process

  23 mars 2020, par sqr

  I am fairly new to python and rq, and have come to a point I can’t solve by myself.

  I am using ffmpeg-python to encode livestreams, this is distributed in rq workers and displayed on a web app using flask, but since the livestreams can go on forever, I need some way to stop this process while it is still in execution. Opening the terminal where the rq worker is executing the task and pressing ’q’ (ffmpeg shortcut to quit) works, and marks the job as OK, but I need to be able to do this from my web app.

  I have tried getting the worker ID and sending it a SIGKILL, this stops the worker but the task continues running, which is something I don’t understand at all. It’s as if the actual ffmpeg process was being executed somewhere else and stopping the worker didn’t stop ffmpeg. Note that I am not using ffmpeg.run_async, I am using ffmpeg.run which as far as my limited knowledge goes, should not be executed asynchronously. While the streaming is being encoded the worker is marked as busy and has the Job ID properly assigned, so I really don’t understand why, when the worker is killed, the underlying process is still in execution.

  If instead of sending a SIGKILL I send a SIGTERM, the worker says it’s waiting for a warm exit and is never closed, as the ffmpeg process is still doing it’s thing.

  One of my ideas was trying to send a ’q’ keystroke to the worker (which I have no idea how to do even though i’ve been doing some research) or trying to switch from rq to celery, that supposedly supports the cancellation of tasks that are being executed.

  This is my routes file

  @app.route('/streamings', methods=['GET', 'POST'])
  
  @login_required
  
  def streamings():
  
  ...
  
      if form2.submit_stop.data and form2.validate():
  
          conn1 = Redis.from_url('redis://')
  
          queue = rq.Queue('tasks-q', connection=Redis.from_url('redis://'))
  
          workers = rq.Worker.all(queue=queue)
  
  
  
          for worker in workers:
  
              peine = worker.get_current_job_id()
  
              if peine == form2.fld1.data:
  
                  os.kill(worker.pid, signal.SIGKILL)

  and this is my tasks file

  def restream(origin, server, stream_key):
  
      stream_server = generate_url(server, stream_key)
  
      try:
  
          stream_map = None
  
          stream1 = ffmpeg.input(get_manifest(origin), re=None)
  
          stream2 = ffmpeg.input('mosca_66.png')
  
          stream_ol = ffmpeg.overlay(stream1, stream2, x='main_w-overlay_w-50', y='50')
  
          a1 = stream1.audio
  
          stream = ffmpeg.output(stream_ol, a1, stream_server, format='flv', vcodec='libx264', acodec='aac', preset='medium', g='120', crf='23', maxrate='4M', bufsize='5M', channel_layout='stereo')
  
          print(stream.get_args())
  
          ffmpeg.run(stream)
  
      except:
  
          set_complete() 

  Any insight on possible solutions would be greatly appreciated.

  Thanks

• FATE : stop using numeric arguments to -vsync

  4 décembre 2021, par Anton Khirnov

  FATE : stop using numeric arguments to -vsync
  Symbolic names are always preferable.
  

  • [DH] tests/fate/h264.mak
  • [DH] tests/fate/hevc.mak
  • [DH] tests/fate/mov.mak
  • [DH] tests/fate/mpeg4.mak
  • [DH] tests/fate/vcodec.mak