Recherche avancée

Sur d’autres sites (4917)

• HTTP live streaming from android device to amazon web server S3

  25 juin 2014, par jawad bin zafar

  I want to stream a video being capture by an android device to an amazon S3 server. Is it possible only in java or I have to use JNI and FFMPEG. Any sample code or online tutorial/Link. Help plz.

• ffmpeg binary which can work on Ubuntu version 13.10 [on hold]

  6 décembre 2013, par user2007454

  Can anybody tell me where can I find ffmpeg binary for ubuntu version 13.10, I have spent days in ffmpeg compilation but every time I try to convert my video file from one format to other I am getting an eror I think working with binary would be a good idea plz do share your comments on this

  ffmpeg -i linux_vid.mp4 linux_vid.avi
  
  ffmpeg version 0.8.9-6:0.8.9-0ubuntu0.13.10.1, Copyright (c) 2000-2013 the Libav developers
  
    built on Nov  9 2013 19:15:22 with gcc 4.8.1
  
  *** THIS PROGRAM IS DEPRECATED ***
  
  This program is only provided for compatibility and will be removed in a future release. Please use avconv instead.
  
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'linux_vid.mp4':
  
    Metadata:
  
      major_brand     : isom
  
      minor_version   : 512
  
      compatible_brands: isomiso2avc1mp41
  
      encoder         : Lavf54.59.106
  
      comment         : 1364833251131047
  
    Duration: 00:00:56.45, start: 0.000000, bitrate: 231 kb/s
  
      Stream #0.0(und): Video: h264 (Constrained Baseline), yuv420p, 320x238 [PAR 4057:4095 DAR 129824:97461], 133 kb/s, PAR 41531:41920 DAR 349:262, 24 fps, 24 tbr, 12288 tbn, 48 tbc
  
      Stream #0.1(und): Audio: aac, 44100 Hz, stereo, s16, 93 kb/s
  
  [buffer @ 0x94225c0] w:320 h:238 pixfmt:yuv420p
  
  [mpeg4 @ 0x943fa80] Invalid pixel aspect ratio 41531/41920, limit is 255/255
  
  Output #0, avi, to 'linux_vid.avi':
  
      Stream #0.0(und): Video: mpeg4, yuv420p, 320x238 [PAR 41531:41920 DAR 349:262], q=2-31, 200 kb/s, 90k tbn, 24 tbc
  
      Stream #0.1(und): Audio: libmp3lame, 44100 Hz, stereo, s16, 200 kb/s
  
  Stream mapping:
  
    Stream #0.0 -> #0.0
  
    Stream #0.1 -> #0.1
  
  Error while opening encoder for output stream #0.0 - maybe incorrect parameters such as bit_rate, rate, width or height

• Node.js Webm live stream server : issues with tag

  10 décembre 2013, par breathe0

  I'm using Node.js as stream server to stream realtime Webm videos that is sent by FFMPEG (executed from another application, the stream is done via HTTP) and received by a webapp that uses the tag.

  This is what I'm doing : FFMPEG streams the received frames using the following command :

  ffmpeg -r 30 -f rawvideo  -pix_fmt bgra -s 640x480 
  
  -i \\.\pipe\STREAM_PIPE -r 60 
  
  -f segment  -s 240x160 -codec:v libvpx  -f webm 
  
  http://my.domain.com/video_stream.webm

  (the stream comes from an application that uses the Kinect as source and communicates with FFMPEG through a pipe, sending one frame after another)

  When the webapp connects, it receives immediately this response from the server :

  HTTP/1.1 200 OK
  
  X-Powered-By: Express
  
  content-type: video/webm
  
  cache-control: private
  
  connection: close
  
  Date: Fri, 06 Dec 2013 14:36:31 GMT

  and a Webm header (previously stored on the server, with the same resolution and frame rate of the source stream and tested as working on VLC) is immediately appended. Then the webapp starts to receive the data streamed by FFMPEG. Here is a screenshot of Mkvinfo GUI showing the fields of the header :

  

  However, even if the Network tab of the Chrome console shows that there is an actual stream of data (meaning that what is streamed is not completely garbage, otherwise the connection would be dropped), the player doesn't display anything. We tried to manually prepend our header to the dumped video received by the webapp and VLC plays it just fine, but this is not happening with the tag.

  What can cause this problem ? Are we missing something about the encoding on the FFMPEG side or we stored wrong values on the header (or they're not enough) ?

  PS : I cannot rely on an extern stream server.

  PPS : We tried the following experiments :

  • substituting the video header with the one stored in the server makes the video playable on both vlc and video tag
  • if we dump the video that is already started (without an header) and we prepend the video header stored in the server or even its original header, the video is playable in VLC but not on the tag (we're carefully prepending the header just before the beggining of the cluster).