Sur d’autres sites (9273)

• Opening Video with opencv3 and python on Amazon EC2

  11 octobre 2016, par stml

  I successfully set up python and opencv3 on an t2.micro instance by following these instructions : http://stackoverflow.com/a/38867965/1213715

  The script which worked on my local machine no longer works. The problem seems to be with importing video. The start of my code now looks like this :

  import numpy as np
  
  import cv2
  
  
  
  cap = cv2.VideoCapture('/home/ec2-user/test.mov')
  
  
  
  if(cap.isOpened() == False):
  
      print "Can't open video"
  
      exit()

  This exits every time. I have tried different paths and different video formats (including .avi).

  In other threads, I read that ffmpeg is essential to cv2 video functions, and successfully installed this using the instructions at https://forums.aws.amazon.com/thread.jspa?messageID=524523. I can now run ffmpeg from the command line - but it has not changed the cv2 output.

  Do I need to link ffmpeg to cv2 somehow, or do I need to recompile entirely - and if so, what change should I make to the original installation instructions ?

  Python version 2.7.12

  Opencv version 3.1.0

• laravel ffmpeg upload video in amazon s3 failed 504 gateway Time-out

  21 mai 2020, par Ahmed Al-Rayan

  Why after uploading a video size of more than 1 Giga, I see a problem in the nginx 504 gateway timeout preventing me from completing the processing process. The meaning of the video after uploading starts the processing process and because of this problem it does not go to processing use laravel ffmpeg and use amazon s3 service to store the videos on it and the entire site uploaded to Digital hosting

  


• Stream RTSP to HTML5 Video - which is the best approach ?

  13 janvier 2020, par Daniel

  As this task is very complicated I’ve created two approaches and I’d like to know which is the better approach for my purpose.

  Approach 1 :

  H264 frames are grabbed out of RTSP stream on the server (i.e. by ffmpeg), then they are put into a websocket and sent to the client. Client uses mp4box.js to fragment the h264 and then HTML5 video can render it with MSE.

  Approach 2 :

  H264 frames are grabbed out of RTSP stream and also fragmented on the server (i.e. by ffmpeg), then they are transferred directly to the client’s HTML5 video to render it with MSE.
  Here is an example for this approach.

  If we consider today’s client devices (modern phones, notebooks), we can state approach1 would be a better solution because it would prevent the central load on the server.

  However I have not really found any good resource or material on how to use approach1, hence I could not yet tried it out.

  I would like to know if approach1 is really better than approach2 ?

  because maybe grabbing and fragmenting would not put much higher load on the server than grabbing only

  (why I’m asking this ? because for approach2 I’ve a concrete example, whereas for approach1 I don’t. If approach1 is really better, I’ll go for it and implement the whole thing.)

  To put it more exact : does ffmpeg stress the server more if it grabs and fragments an rtsp-h264 stream to fmp4 than when it only grabs the frames from rtsp-h264 stream ?