Recherche avancée

Sur d’autres sites (7927)

• Merge commit ’ea7f79f93796d68559a495be824b6bbd94dfe5f6’

  1er mars 2014, par Michael Niedermayer

  Merge commit ’ea7f79f93796d68559a495be824b6bbd94dfe5f6’
  * commit ’ea7f79f93796d68559a495be824b6bbd94dfe5f6’ :
  
    qt-faststart : Avoid unintentionally sign extending BE_32
  See : 582f36ca3fb1c69dbe3478f174d36278f5dd3f63
  
  See : 69ce34c796dd2d595f3312848cf6d0c87506e0d0
  
  Merged-by : Michael Niedermayer <michaelni@gmx.at>
  

  • [DH] tools/qt-faststart.c

• can't re-stream using FFMPEG to MP4 HTML5 video

  12 mars 2016, par deandob

  I have been struggling to get live streaming working from FFMPEG for many hours so raising the white flag and asking for help here.

  My scenario is I have an IP security camera that I can successfully connect via RTSP (h.264) and save the video as file segments, and they play back fine either through a standalone app like VLC or via a node.js web server app that sends the ’video/mp4’ & keep-alive header and streams the mp4 files previously saved by FFMPEG to a HTML5 video client.

  However I want to take the same RTSP stream and re-stream it live to a HTML5 client. I know the HTML5 client bits and the FFMPEG remuxing to MP4 work as the MP4 recording/streaming works.

  I have tried the following :

  1) Set the output as a HTTP string. I don’t think FFMPEG supports this as I get ’input/output error’ and the FFMPEG documentation talks about another app called FFSERVER which isn’t supported on Windows

  ffmpeg -i rtsp://admin:12345@192.168.1.234:554 -vcodec copy -f mp4 -movflags frag_keyframe+empty_moov http://127.0.0.1:8888

  2) As ffmpeg runs as a spawn in node.js, I have tried piping the STDOUT to a node http server, using the same header I use for the recording playback stream. I can view this stream in VLC which is a good sign but I can’t get the HTML client to recognize the stream and it shows blank, or occasionally a static image of the stream.

  var liveServer = http.createServer(liveStream); 
  
  var liveStream = function (req, resp) {                                            // handle each client request by instantiating a new FFMPEG instance
  
      resp.writeHead(200, {"Content-Type": "video/mp4", "Connection": "keep-alive"});
  
          var xffmpeg = child_process.spawn("ffmpeg", [
  
              "-i", "rtsp://admin:12345@192.168.1.234:554" , "-vcodec", "copy", "-f", "mp4", "-movflags", "frag_keyframe+empty_moov", "-"   // output to stdout
  
              ],  {detached: false});
  
  
  
              xffmpeg.stdout.pipe(resp);
  
  
  
              xffmpeg.on("exit", function (code) {
  
                   console.log("Xffmpeg terminated with code " + code);
  
              });
  
  
  
              xffmpeg.on("error", function (e) {
  
                    console.log("Xsystem error: " + e);
  
              });
  
  
  
              xffmpeg.stdout.on("data",function(data) {
  
                    console.log('Xdata rcv ' + data);
  
              });
  
  
  
              xffmpeg.stderr.on("data", function (data) {
  
                    console.log("XFFMPEG -> " + data);
  
      }
  
  }

  I have tried both IE11 and Chrome HTML5 clients.

  I suspect there is something not quite right with the format of the stream being sent which stops the HTML5 video client but not enough to stop VLC. The irritating thing is that the code above works just fine for playing back MP4 streams that have been recorded.

  Any ideas how to get live re-streaming via FFMPEG working ? Thanks.

• Revision 43be86dbff : vp10 : remove double MV value check. This has virtually no effect on coding effi

  8 septembre 2015, par Ronald S. Bultje

  Changed Paths :
   Modify /vp10/common/mvref_common.c

  
   Modify /vp10/common/mvref_common.h

  
  
  vp10 : remove double MV value check.

  This has virtually no effect on coding efficiency, but it is more
  logical from a theoretical perspective (since it makes no sense to
  me that you would exclude a MV from a list just because it’s sign-
  inversed value is identical to a value already in a list), and it
  also makes the code simpler (it removes a duplicate value check in
  cases where signbias is equal between the two MVs being compared).

  See issue 662.

  Change-Id : I23e607c6de150b9f11d1372fb2868b813c322d37