Recherche avancée

Sur d’autres sites (4366)

• How to programmatically start/stop FFMPEG stream transcoding

  10 décembre 2019, par Paul Wieland

  I have an ip webcam which provides an MJPEG stream. I can successfully transcode and save that stream with ffmpeg under OSX. The following gives me pretty much what I want :

  ffmpeg -f mjpeg -i "http://user:pass@10.0.1.200/nphMotionJpeg?Resolution=640x480&Quality=Standard" -b:v 1500k -vcodec libx264 /tmp/test.mp4

  That will start an FFMPEG session and begin saving the live stream to my test.mp4 file. pressing q will quit ffmpeg and save the file.

  I would like to programmatically start & stop the recording using a PHP or Bash shell script. I have tried the following :

  <?php
  
  
  
  $pid = pcntl_fork();
  
  
  
  if($pid == -1){
  
      die("could not fork"); 
  
  }elseif($pid){
  
      // we are the parent...
  
      print $pid.' started recording. waiting 10 seconds...';
  
      sleep(10); // Wait 10 seconds
  
  
  
      print_r(shell_exec("kill ".$pid)); // Kill the child recording process
  
  
  
      echo 'done';
  
      exit(); 
  
  }else{
  
      // we are the child process. call ffmpeg.
  
      exec('../lib/ffmpeg -f mjpeg -i "http://user:pass@10.0.1.200/nphMotionJpeg?Resolution=640x480&Quality=Standard" -b:v 1500k -vcodec libx264 /tmp/test.mp4');
  
  }

  But there are two problems :

  1. The ffmpeg process does not end/die (probably because its forked again)
  2. When I manually kill the ffmpeg process, the video file is not readable

• stop or kill node media server

  9 juillet 2019, par user_66663333

  I am trying to implement stop feature for live video streaming using node-media-server.

  Basically I want to stop node-media-server completely, restart it later.

  const NodeMediaServer = require("node-media-server");
  
      let config = {
  
        logType: 3,
  
        rtmp: {
  
          port: rtmpPort,
  
          chunk_size: 60000,
  
          gop_cache: true,
  
          ping: 60,
  
          ping_timeout: 30,
  
        },
  
        http: {
  
          port: httpPort,
  
          allow_origin: "*",
  
        },
  
        relay: {
  
          ffmpeg: "/usr/bin/ffmpeg",
  
          tasks: [
  
            {
  
              app: "cctv",
  
              mode: "static",
  
              edge: "rtsp://" + cameraUrl + "/h264_ulaw.sdp",
  
              name: "uterum",
  
              rtsp_transport: "udp",
  
            },
  
          ],
  
        },
  
      };
  
  
  
      let nms = new NodeMediaServer(config);
  
      nms.run();

• Why is ffmpeg taking up so much memory when I try to stop a livestream ?

  4 juillet 2019, par FiskFan1999

  When the ffmpeg function is running, there are no problems with memory and everything runs smoothly. However, when I attempt to stop the stream/ffmpeg by pressing q (or ctrl-c), ffmpeg freezes, doesn’t take any other inputs, and suddenly takes up an obscene amount of memory.

  I am using ffmpeg to livestream on youtube. I am using a MacBook Mid 2015 running macOS Mojave.

  here is the function I am using with ffmpeg.

  ffmpeg -re -f lavfi -i testsrc2=s=1280x720:r=60 -re -i "INPUT FILE.mp3" -vcodec libx264 -pix_fmt yuv420p -preset "ultrafast" -r 60 -g 120 -b:v 6168000 -filter_complex "[0]scale=1280:720;[1]aloop=start=0:size=202*44100:loop=-1" -acodec libmp3lame -ar 44100 -threads 3 -b:a 640000 -qscale:a 5 -bufsize 512k -f flv ${YOUTUBE_URL}/${KEY}

  The command runs perfectly and as expected while it is running. At this point, in Activity Monitor I can see that ffmpeg seems to peak to about 101 MB. When I press q, which is the button to end the encoding, if the stream had been going for about ten minutes ffmpeg freezes and in Activity monitor the ffmpeg command appears to climb to several gigabytes of memory without any sign of stopping. The most I have noticed is about 6 GB before I killed the command. Ffmpeg seems to be writing almost a gigabyte of data into memory a second. In fact, this slows down my computer when it occurs and threatens to completely fill up my memory.

  When this occurs, there are no error messages (except for warnings about running out of memory) and the terminal running ffmpeg seems to not respond to any kill commands, and the only way to alleviate the situation is to force close the terminal window itself.

  I’m wondering if somehow I am creating a memory leak issue or if I wrote something wrong or didn’t include something that would be necessary for live-streaming with ffmpeg.