Sur d’autres sites (4124)

• How to use (django-celery,RQ) worker to execute a video filetype conversion (ffmpeg) in django on heroku (My code works locally)

  15 janvier 2013, par GetItDone

  One part of my website includes a form that allows users to upload video. I use ffmpeg to convert the video to flv. My media and static files are stored on Amazon S3. I can get everything to work perfectly locally, however I can't seem to figure out how to use a worker to run the video conversion subprocess in production. I have dj-celery and rq installed in my app. The code in my view that I was able to get to work locally is :

  #views.py
  
  def upload_broadcast(request):
  
      if request.method == 'POST':
  
          form = VideoUploadForm(request.POST, request.FILES)
  
          if form.is_valid():
  
              new_video=form.save()
  
              def convert_to_flv(video):
  
                  filename = video.video_upload
  
                  sourcefile = "%s%s" % (settings.MEDIA_ROOT, filename)
  
                  flvfilename = "%s.flv" % video.id
  
                  imagefilename = "%s.png" % video.id
  
                  thumbnailfilename = "%svideos/flv/%s" % (settings.MEDIA_ROOT, imagefilename)
  
                  targetfile = "%svideos/flv/%s" % (settings.MEDIA_ROOT, flvfilename)
  
                  ffmpeg = "ffmpeg -i %s -acodec mp3 -ar 22050 -f flv -s 320x240 %s" % (sourcefile, targetfile)
  
                  grabimage = "ffmpeg -y -i %s -vframes 1 -ss 00:00:02 -an -vcodec png -f rawvideo -s 320x240 %s" % (sourcefile, thumbnailfilename)
  
                  print ("SOURCE: %s" % sourcefile)
  
                  print ("TARGET: %s" % targetfile)
  
                  print ("TARGET IMAGE: %s" % thumbnailfilename)
  
                  print ("FFMPEG TASK CODE: %s" % ffmpeg)
  
                  print ("IMAGE TASK CODE: %s" % grabimage)
  
                  try:
  
                      ffmpegresult = subprocess.call(ffmpeg)
  
                      print "---------------FFMPEG---------------"
  
                      print ffmpegresult
  
                  except:
  
                      print "Not working."
  
                  try:
  
                      videothumbnail = subprocess.call(grabimage)
  
                      print "---------------IMAGE---------------"
  
                      print videothumbnail
  
                  except:
  
                      print "Not working."
  
                  video.flvfilename = flvfilename
  
                  video.videothumbnail = imagefilename
  
                  video.save()
  
  
  
              convert_to_flv(new_video)
  
  
  
              return HttpResponseRedirect('/video_list/')
  
      else:
  
  ...

  This is my first time trying to use a worker (or ever pushing a project to production), so even with the documentation it is still unclear to me what I need to do. I have tried several different things but nothing seems to work. Is there just a simple way to tell celery to run the ffmpegresult = subprocess.call(ffmpeg) ? Thanks in advance for any help or insight.

  EDIT- Added heroku logs

  2013-01-10T20:58:57+00:00 app[web.1]: TARGET: /media/videos/flv/8.flv
  
  2013-01-10T20:58:57+00:00 app[web.1]: IMAGE TASK CODE: ffmpeg -y -i /media/videos/practice.wmv -vframes 1 -ss 00:00:02 - an -vcodec png -f rawvideo -s 320x240 /media/videos/flv/8.png
  
  2013-01-10T20:58:57+00:00 app[web.1]: SOURCE: /media/videos/practice.wmv
  
  2013-01-10T20:58:57+00:00 app[web.1]: FFMPEG TASK CODE: ffmpeg -i /media/videos/practice.wmv -acodec mp3 -ar 22050 -f fl v -s 320x240 /media/videos/flv/8.flv
  
  2013-01-10T20:58:57+00:00 app[web.1]: TARGET IMAGE: /media/videos/flv/8.png
  
  2013-01-10T20:58:57+00:00 app[web.1]: Not working.
  
  2013-01-10T20:58:57+00:00 app[web.1]: Not working.

  NEWER EDIT

  I tried adding a tasks.py and added the task :

  celery = Celery('tasks', broker='redis://guest@localhost//')
  
  
  
  @celery.task
  
  def ffmpeg_task(video):
  
      converted_file = subprocess.call(video)
  
      return converted_file

  then I changed the relevant section of my view to :

  ...
  
  try:
  
      ffmpeg_task.delay(ffmpeg)
  
      print "---------------FFMPEG---------------"
  
      print ffmpegresult
  
  except:
  
      print "Not working."
  
  ...

  My new logs are :

  2013-01-15T13:19:52+00:00 app[web.1]: TARGET IMAGE: /media/videos/flv/12.png
  
  2013-01-15T13:19:52+00:00 app[web.1]: SOURCE: /media/videos/practice.wmv
  
  2013-01-15T13:19:52+00:00 app[web.1]: FFMPEG TASK CODE: ffmpeg -i /media/videos/practice.wmv -acodec mp3 -ar 22050 -f fl v -s 320x240 /media/videos/flv/12.flv
  
  2013-01-15T13:19:52+00:00 app[web.1]: IMAGE TASK CODE: ffmpeg -y -i /media/videos/practice.wmv -vframes 1 -ss 00:00:02 -an -vcodec png -f rawvideo -s 320x240 /media/videos/flv/12.png
  
  2013-01-15T13:19:52+00:00 app[web.1]: TARGET: /media/videos/flv/12.flv
  
  2013-01-15T13:20:17+00:00 app[web.1]: 2013-01-15 13:20:17 [2] [CRITICAL] WORKER TIMEOUT (pid:12)
  
  2013-01-15T13:20:17+00:00 app[web.1]: 2013-01-15 13:20:17 [2] [CRITICAL] WORKER TIMEOUT (pid:12)
  
  2013-01-15T13:20:17+00:00 app[web.1]: 2013-01-15 13:20:17 [19] [INFO] Booting worker with pid: 19

  Am I completely missing something ? I'll keep trying, but will be very appreciative of any direction or assistance.

• ffmpeg stream chrome kiosk mode ubuntu 16.04 server

  15 février 2021, par Raul

  I have a weird out-of-sync issue while using ffmpeg to stream to youtube live a chrome browser from an ub untu 16.04 server.

  



  Issue : output video streamed to youtube has audio/video out of sync, sometimes with as much as 3s

  



  Current flow :

  



  1) start pulseaudio - we using something like this to start it :

  



  pulseaudio --start -vvv --disallow-exit --log-target=syslog --high-priority --exit-idle-time=-1 --daemonize


  



  2) start Xvfb

  



  Xvfb :0 -ac -screen 0 1920x1080x24


  



  3) start chrome linux in kiosk mode

  



  google-chrome --kiosk --disable-gpu --incognito --no-first-run --disable-java --disable-plugins --disable-translate --disk-cache-size=$((1024 * 1024)) --disk-cache-dir=/tmp/chrome/ --user-data-dir=/tmp/chrome/ --force-device-scale-factor=1 --window-size=1920,1080 --window-position=0,0 LOCATION_URL


  



  4) start ffmpeg

  



  ffmpeg -y \
  -thread_queue_size 8192 -rtbufsize 250M -f x11grab -video_size 1920x1080 -framerate 24 -i :0 \
  -thread_queue_size 8192 -channel_layout stereo -f alsa -i pulse \
  -c:v libx264 -pix_fmt yuv420p -c:v libx264 -g 48 -crf 24 -filter:v fps=24 -preset ultrafast -tune zerolatency \
  -c:a aac -strict -2 -channel_layout stereo -ab 96k -ac 2 -flags +global_header \
  -f flv YOUTUBE_LIVE_STREAMING_RTMP


  



  Note : this is running on an amazon ec2 instance, meaning there is no soundcard, so alsa and pulseaudio are creating a dummy audio card. However, the latency does not come from there. Logs :

  



  Nov 25 06:14:22 ip-172-31-29-8 pulseaudio[26602]: [pulseaudio] protocol-native.c: Adjust latency mode enabled, configuring sink latency to half of overall latency.
Nov 25 06:14:22 ip-172-31-29-8 pulseaudio[26602]: [pulseaudio] protocol-native.c: Requested latency=23.22 ms, Received latency=23.22 ms
Nov 25 06:14:22 ip-172-31-29-8 pulseaudio[26602]: [pulseaudio] protocol-native.c: Final latency 69.66 ms = 23.22 ms + 2*11.61 ms + 23.22 ms


  



  At this point, here's what we observed :

  



  


  1. if we start ffmpeg exactly after issuing the command to start chrome, we see the DTS errors from ffmpeg. Audio is out of sync with the video and has delay of 3-5seconds AHEAD. We also noticed the out of sync remains the same for the full duration of the stream

  


  2. if we start ffmpeg after around 10seconds, audio and video are almost in sync. We then manually added a -itsoffset -0.125 to the ffmpeg command and everything is perfect.

  


  



  Questions :

  



  

  1. Why would ffmpeg have so much lag if it's started right after chrome ?

  


  2. Is starting the ffmpeg after 10s or X seconds the expected behavior ? That is, is this because the system needs to wait for audio/video signals to be "ready" or something ?

  


  3. Is there a way to 100% calculate or know when Chrome is fully ready and start ffmpeg ? We found sometimes it takes 5s, sometimes 10. Depends on the URL we load.

  


  4. Besides the DTS error that ffmpeg throws, is there any other way to know if audio/video is out-of-sync ? as sometimes we have a delay of between 0.5 to 1s, but ffmpeg does not report anything. And a restart is required to "re-balance" the audio/video inputs and get them back in sync.

  


  5. Can pulseaudio be the problem in this scenario ?

  


  



  Thank you

  



  UPDATE Dec 20

  



  We were able to do some tricks to force chrome to start the audio on page load, and that will force connect to pulseaudio. Doing that, plus adding a 3s delay for ffmpeg to start, there is no more delay when ffmpeg starts.
However, our app is a webRTC app, and we have a STRANGER thing happening : if we start the page with no webcam/audio, once the webcam/audio is enabled, ffmpeg (while showing no errors) has a delay of 2s or so. While keep talking, in about max 30s, that delay is GONE.

  



  So the new questions are :

  



  

  1. Besides the DTS error that ffmpeg throws, is there any other way to know if audio/video is out-of-sync ? as sometimes we have a delay of between 0.5 to 1s, but ffmpeg does not report anything.

  


  2. What could cause the initial audio/video out of sync issue and then catching up ?

  


  


• ffmpeg stream chrome kiosk mode ubuntu 16.04 server

  21 décembre 2016, par Raul

  I have a weird out-of-sync issue while using ffmpeg to stream to youtube live a chrome browser from an ub untu 16.04 server.

  Issue : output video streamed to youtube has audio/video out of sync, sometimes with as much as 3s

  Current flow :

  1) start pulseaudio - we using something like this to start it :

  pulseaudio --start -vvv --disallow-exit --log-target=syslog --high-priority --exit-idle-time=-1 --daemonize

  2) start Xvfb

  Xvfb :0 -ac -screen 0 1920x1080x24

  3) start chrome linux in kiosk mode

  google-chrome --kiosk --disable-gpu --incognito --no-first-run --disable-java --disable-plugins --disable-translate --disk-cache-size=$((1024 * 1024)) --disk-cache-dir=/tmp/chrome/ --user-data-dir=/tmp/chrome/ --force-device-scale-factor=1 --window-size=1920,1080 --window-position=0,0 LOCATION_URL

  4) start ffmpeg

  ffmpeg -y \
  
    -thread_queue_size 8192 -rtbufsize 250M -f x11grab -video_size 1920x1080 -framerate 24 -i :0 \
  
    -thread_queue_size 8192 -channel_layout stereo -f alsa -i pulse \
  
    -c:v libx264 -pix_fmt yuv420p -c:v libx264 -g 48 -crf 24 -filter:v fps=24 -preset ultrafast -tune zerolatency \
  
    -c:a aac -strict -2 -channel_layout stereo -ab 96k -ac 2 -flags +global_header \
  
    -f flv YOUTUBE_LIVE_STREAMING_RTMP

  Note : this is running on an amazon ec2 instance, meaning there is no soundcard, so alsa and pulseaudio are creating a dummy audio card. However, the latency does not come from there. Logs :

  Nov 25 06:14:22 ip-172-31-29-8 pulseaudio[26602]: [pulseaudio] protocol-native.c: Adjust latency mode enabled, configuring sink latency to half of overall latency.
  
  Nov 25 06:14:22 ip-172-31-29-8 pulseaudio[26602]: [pulseaudio] protocol-native.c: Requested latency=23.22 ms, Received latency=23.22 ms
  
  Nov 25 06:14:22 ip-172-31-29-8 pulseaudio[26602]: [pulseaudio] protocol-native.c: Final latency 69.66 ms = 23.22 ms + 2*11.61 ms + 23.22 ms

  At this point, here’s what we observed :

  1. if we start ffmpeg exactly after issuing the command to start chrome, we see the DTS errors from ffmpeg. Audio is out of sync with the video and has delay of 3-5seconds AHEAD. We also noticed the out of sync remains the same for the full duration of the stream

  2. if we start ffmpeg after around 10seconds, audio and video are almost in sync. We then manually added a -itsoffset -0.125 to the ffmpeg command and everything is perfect.

  Questions :

  1. Why would ffmpeg have so much lag if it’s started right after chrome ?
  2. Is starting the ffmpeg after 10s or X seconds the expected behavior ? That is, is this because the system needs to wait for audio/video signals to be "ready" or something ?
  3. Is there a way to 100% calculate or know when Chrome is fully ready and start ffmpeg ? We found sometimes it takes 5s, sometimes 10. Depends on the URL we load.
  4. Besides the DTS error that ffmpeg throws, is there any other way to know if audio/video is out-of-sync ? as sometimes we have a delay of between 0.5 to 1s, but ffmpeg does not report anything. And a restart is required to "re-balance" the audio/video inputs and get them back in sync.
  5. Can pulseaudio be the problem in this scenario ?

  Thank you

  UPDATE Dec 20

  We were able to do some tricks to force chrome to start the audio on page load, and that will force connect to pulseaudio. Doing that, plus adding a 3s delay for ffmpeg to start, there is no more delay when ffmpeg starts.
  However, our app is a webRTC app, and we have a STRANGER thing happening : if we start the page with no webcam/audio, once the webcam/audio is enabled, ffmpeg (while showing no errors) has a delay of 2s or so. While keep talking, in about max 30s, that delay is GONE.

  So the new questions are :

  1. Besides the DTS error that ffmpeg throws, is there any other way to know if audio/video is out-of-sync ? as sometimes we have a delay of between 0.5 to 1s, but ffmpeg does not report anything.
  2. What could cause the initial audio/video out of sync issue and then catching up ?