Recherche avancée

Sur d’autres sites (11703)

• php stream any mp4

  3 avril 2012, par GRaecuS

  I'm developing a web app that converts videos and allows to play them through Flowplayer.

  On the current status, I use ffmpeg to convert the videos to mp4 and qtfaststart to fix their metadata for streaming. Everything is working smoothly as I can download any converted mp4 and view it correctly.

  For serving the videos to Flowplayer, I use a php file which contains the following (summarized) code :

  header("Content-Type: {$mediatype}");
  
  
  
  if ( empty($_SERVER['HTTP_RANGE']) )
  
  {
  
      if ( $filetype == 'flv' && $seekPos != 0 )
  
      {
  
          header("Content-Length: " . ($filesize + 13));
  
          print('FLV');
  
          print(pack('C', 1));
  
          print(pack('C', 1));
  
          print(pack('N', 9));
  
          print(pack('N', 9));
  
      }
  
      else
  
      {           
  
          header("Content-Length: {$filesize}");
  
      }
  
  
  
      $fh = fopen($filepath, "rb") or die("Could not open file: {$filepath}");
  
  
  
      # seek to requested file position
  
      fseek($fh, $seekPos);
  
  
  
      # output file
  
      while(!feof($fh))
  
      {
  
          # output file without bandwidth limiting
  
          echo fread($fh, $filesize);
  
      }
  
      fclose($fh);
  
  }
  
  else //violes rfc2616, which requires ignoring  the header if it's invalid
  
  {   
  
      $fp = @fopen($file, 'rb');
  
  
  
      $size   = filesize($file); // File size
  
      $length = $size;           // Content length
  
      $start  = 0;               // Start byte
  
      $end    = $size - 1;       // End byte
  
      // Now that we've gotten so far without errors we send the accept range header
  
      /* At the moment we only support single ranges.
  
       * Multiple ranges requires some more work to ensure it works correctly
  
       * and comply with the spesifications: http://www.w3.org/Protocols/rfc2616/rfc2616-sec19.html#sec19.2
  
       *
  
       * Multirange support annouces itself with:
  
       * header('Accept-Ranges: bytes');
  
       *
  
       * Multirange content must be sent with multipart/byteranges mediatype,
  
       * (mediatype = mimetype)
  
       * as well as a boundry header to indicate the various chunks of data.
  
       */
  
      header("Accept-Ranges: 0-$length");
  
      // header('Accept-Ranges: bytes');
  
      // multipart/byteranges
  
      // http://www.w3.org/Protocols/rfc2616/rfc2616-sec19.html#sec19.2
  
      if (isset($_SERVER['HTTP_RANGE']))
  
      {
  
          $c_start = $start;
  
          $c_end   = $end;
  
          // Extract the range string
  
          list(, $range) = explode('=', $_SERVER['HTTP_RANGE'], 2);
  
          // Make sure the client hasn't sent us a multibyte range
  
          if (strpos($range, ',') !== false)
  
          {
  
              // (?) Shoud this be issued here, or should the first
  
              // range be used? Or should the header be ignored and
  
              // we output the whole content?
  
              header('HTTP/1.1 416 Requested Range Not Satisfiable');
  
              header("Content-Range: bytes $start-$end/$size");
  
              // (?) Echo some info to the client?
  
              exit;
  
          }
  
          // If the range starts with an '-' we start from the beginning
  
          // If not, we forward the file pointer
  
          // And make sure to get the end byte if spesified
  
          if ($range0 == '-')
  
          {
  
  
  
              // The n-number of the last bytes is requested
  
              $c_start = $size - substr($range, 1);
  
          }
  
          else
  
          {
  
              $range  = explode('-', $range);
  
              $c_start = $range[0];
  
              $c_end   = (isset($range[1]) && is_numeric($range[1])) ? $range[1] : $size;
  
          }
  
          /* Check the range and make sure it's treated according to the specs.
  
           * http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html
  
           */
  
          // End bytes can not be larger than $end.
  
          $c_end = ($c_end > $end) ? $end : $c_end;
  
          // Validate the requested range and return an error if it's not correct.
  
          if ($c_start > $c_end || $c_start > $size - 1 || $c_end >= $size)
  
          {
  
              header('HTTP/1.1 416 Requested Range Not Satisfiable');
  
              header("Content-Range: bytes $start-$end/$size");
  
              // (?) Echo some info to the client?
  
              exit;
  
          }
  
          $start  = $c_start;
  
          $end    = $c_end;
  
          $length = $end - $start + 1; // Calculate new content length
  
          fseek($fp, $start);
  
          header('HTTP/1.1 206 Partial Content');
  
      }
  
  
  
      // Notify the client the byte range we'll be outputting
  
      header("Content-Range: bytes $start-$end/$size");
  
      header("Content-Length: $length");
  
  
  
      // Start buffered download
  
      $buffer = 1024 * 8;
  
      while(!feof($fp) && ($p = ftell($fp)) <= $end)
  
      {
  
          if ($p + $buffer > $end)
  
          {
  
              // In case we're only outputtin a chunk, make sure we don't
  
              // read past the length
  
              $buffer = $end - $p + 1;
  
          }
  
          set_time_limit(0); // Reset time limit for big files
  
          echo fread($fp, $buffer);
  
          flush(); // Free up memory. Otherwise large files will trigger PHP's memory limit.
  
      }
  
  
  
      fclose($fp);
  
  }

  Unfortunately, it is working only for the majority of the videos. For some of them, Flowplayer keeps returning Error 200, even though they were encoded correctly.

  How can I fix this ? Is it a coding problem or those videos are faulty ?

• ffmpeg, /dev/video0, -f decklink

  20 mars 2019, par Camille Goudeseune

  I’m trying to capture video from a PCI card, the Blackmagic DeckLink Mini Recorder, via ffmpeg, on a headless host running Ubuntu 18.04.2 LTS, hopefully with a command like

  ffmpeg -f decklink -i /dev/video0 ...

  How can I make that work ? I have two obstacles.

  No /dev/video0

  ffmpeg -i /dev/video0 ... fails : /dev/video0: No such device or address.
  v4l2-ctl --list-devices fails with the same error message.

  I built /dev/video0, and it looks okay :

  mknod /dev/video0 c 81 0
  
  chown root.video /dev/video0
  
  chmod g+rw /dev/video0

  To compare this file with a working one, I ran strace cat /dev/video0 on this host, and on another host (Ubuntu 14) with a working /dev/video0. The outputs began to differ here (good, then bad) :

  fstat(1, {st_mode=S_IFREG|0644, st_size=0, ...}) = 0
  
  open("/dev/video0", O_RDONLY)           = 3  
  
  fstat(3, {st_mode=S_IFCHR|0660, st_rdev=makedev(81, 0), ...}) = 0
  
  fadvise64(3, 0, 0, POSIX_FADV_SEQUENTIAL) = 0
  
  ----
  
  
  
  fstat(1, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 0), ...}) = 0
  
  openat(AT_FDCWD, "/dev/video0", O_RDONLY) = -1 ENXIO (No such device or address)

  So /dev/video0 is broken at a level lower than ffmpeg or v4l2 or even cat.

  On Ubuntu 14, man 8 MAKEDEV suggests that the error message means that "the kernel does not have the driver configured or loaded."

  This Ubuntu 18 host lacks that manpage, but it does have a few /snap/core/*/sbin/MAKEDEV, all the same, so I tried

  /snap/core/6350/sbin/MAKEDEV -n -v video

  It would have created over a hundred devices videoXX, radioXX, vtxXX, vbiXX. Those devices didn’t exist yet, so it seemed harmless to try it.

  rm /dev/video0; /snap/core/6350/sbin/MAKEDEV video

  That rebuilt /dev/video0, but "No such device" remains, from cat or ffmpeg.

  No decklink

  ffmpeg -f decklink ... fails with Unknown input format: 'decklink'.

  Neither black nor deck nor link is mentioned by ffmpeg -devices (fbdev, lavfi, oss, v4l2) and ffmpeg -formats (about 350), either for Ubuntu’s own version 3.4.4-0ubuntu0.18.04.1, or for version N-93330-g7ff89574c7 compiled from source on 2019 Mar 13 :

  git clone https://git.ffmpeg.org/ffmpeg.git ffmpeg
  
  cd ffmpeg
  
  ./configure --enable-nonfree --disable-doc --disable-w32threads --enable-pthreads

  (Although ./configure --help mentions --enable-decklink, using that yielded "ERROR : DeckLinkAPI.h not found." updatedb && locate DeckLinkAPI.h finds no file with that name, either.)

  The DeckLink PCI card is recognized by hwinfo and lspci.

  lsmod reports the loaded modules blackmagic and blackmagic_io.

  Maybe the PCI card is installed ok, but ffmpeg just can’t reach it because I can’t configure it for that.

  Edit : Rebooting didn’t fix anything.

• FFMPEG stereo track stops capturing at random times during a capture session

  26 mai 2022, par mrwassen

  I am currently working on building a workflow to capture and archive a large stash of family and friends PAL and NTSC VHS tapes. The hardware setup is as follows :

  


  

  • JVC HR-7860S VCR

  


  • s-video / RCA audio >

  


  • ADVC-3000 converter

  


  • SDI / BNC cable >

  


  • Blackmagic Decklink Mini Recorder 4K PCIe card

  


  • installed in a fairly hi-spec windows machine : AMD Ryzen 9 5900X 3.7 Ghz base 12 core, GEFORCE RTX 3060 12 gB, 32 gB ram

  


  


  The plan is to capture to lossless AVI, then drop into an NLE (Vegas Pro v.16) to do a minimal amount of cleanup / trimming, then render to a more compressed video format (TBD) for upload to AWS S3 accessible through a family website.

  


  The issue I am having is that when I run the capture using ffmpeg/directshow e.g. for a perfectly fine 90 min. PAL tape, at some random point of time during the capture one of the 2 stereo channels just stops capturing. This has happened with all of the tapes I have tested so far, and it happens at different times during the same video. I have examined the frames surrounding points in time when this happens, and it doesn't correlate to any transitions or jitter, but often just randomly in the middle of a perfectly smooth scene. Once the one channel stops capturing it never starts back up again during that capture session.

  


  The ADVC-3000 and the VCR are both showing both stereo channels playing normally throughout the capture. The windows machine running the capture hardly breaks a sweat at any time, and the transfer easily keeps up constantly showing a speed = 1x which I assume means nothing lagging. Also there are no video/audio sync issues at any point in time even towards the end of long tapes e.g. 90 mins.

  


  I am fairly new at ffmpeg, so I have spent extensive amounts of time reading up on forum posts and experimenting and have ended up with the following syntax :

  


  ffmpeg -y -f dshow -rtbufsize 2000M -i video="Blackmagic WDM Capture":audio="Blackmagic WDM Capture" -codec:v v210 -pix_fmt yuv422p -codec:a pcm_s16le -b:a 128k -t 02:00:00 -r 25 -threads 4 -maxrate 2500k -filter:a "volume=1.5" output_v210_audio.avi


  


  The capture runs without a single dropped frame, the only error I am getting when launching (and perhaps this is a smoking gun ?) is :

  


  


  "Non-monotonous DTS in output stream 0:1 ; previous : 0, current : -30 ;
changing to 1. This may result in incorrect timestamps in the output
file."

  


  


  I have tried to troubleshoot this in the hopes that it is tied to my issue but so far without luck.

  


  Hoping somebody can help correct or modify my command line or perhaps other ideas to help resolve the issue.