Recherche avancée

Sur d’autres sites (4363)

• nodejs fluent-ffmpeg process is too slow

  22 août 2021, par snovosel

  I'm attempting to run the following ffmpeg command using fluent-ffmpeg and locally this command will take between 5-10 seconds. I have the same service deployed to a digital ocean server with 4CPU and 32GB of RAM as a test and the command will hang for sometimes up to 40 minutes. I'm uploading files 15mb-50mb in size as .mov files or .mp4 files. In all cases this has been too slow to be feasible... How can I begin to debug this ?

  


  const handleVideoResize = async (filePath) => {
  try {
    const { height, width } = await getVideoDimensions(filePath); // ffmpeg probe to get the dimensions

    const newWidth = 423;
    const newHeight = 534;

    const x = width - (newWidth / newHeight) * height;

    const destFilePath = path.resolve(`./tmp/final-${uuidv4()}.webm`);

    const outputStream = fs.createWriteStream(destFilePath);

    FFmpeg()
      .input(filePath)
      .input(path.resolve("assets/watermark.png"))
      .complexFilter([
        `[0]crop=${width - x}:${height},scale=${newWidth}:${newHeight}[a]`,
        "[1]scale=iw*0.2:-1[wm];[a][wm]overlay=x=(W-w)-15:y=(H-h)-15",
        `colorchannelmixer=aa=0.6[1]`
      ])
      .format("webm")
      .outputFormat("webm")
      .on("start", () => {
        printText("ffmpeg child process spawned ---");
      })
      .on("end", () => {
        printText("video stream finished");
      })
      .on("error", err => {
        printError("err ffmpeg", err);
      })
      .output(outputStream)
      .run();
  } catch (error) {
    printError("error handle video resize", error);
    return;
  }
};


  


• Low latency routing of rtp input to rtsp output with ffmpeg on a server

  29 mai 2020, par guillefix

  I want to be able to do some simple low-latency screen share. I know peer-to-peer would be the lowest latency, but it seems using an intermediate server is a lot easier to setup. I have found this awesome little library, which sets up an RTSP server, which I'm running on my digital ocean server. I then :

  



  

  1. Set up OBS to stream using RTP to the server on port 8558 with libx264 encoding.

  


  2. Run ffmpeg -re -stream_loop -1 -i rtp://127.0.0.1:8558 -c:v libx264 -c:a aac -f rtsp rtsp://localhost:8554/mystream on the server.

  


  3. Open rtsp://<server ip="ip">:8554/mystream</server> on VLC.

  


  



  However, the latency seems to be quite high. With my crappy internet it must have been like half a minute. A friend with better internet saw it fluctuating between 4-15 seconds. Furthermore, there seems to be a lot of artifacts on the video (problems with encoding ? I'm not sure why these happen ?)

  



  I attach below my OBS settings, and an example of artifacts.

  



  My question is : is there some settings on OBS and on ffmpeg that would allow this to have as low end-to-end latency as possible, while not having too many bad artifacts ? I'm not very well versed on video encoding and streaming, so this is all quite new to me. I'm willing to learn !

  



  

  



  

  


• OpenCV OSX Mavericks video codec issue

  29 juin 2014, par Abhischek

  Firstly, I’ve installed ffmpeg using

  sudo port install ffmpeg

  on my Macbook OSX 10.9 and XCode 5.1. I’ve done the same for OpenCV

  sudo port install opencv

  and I got face detect working using this SO answer. However, when trying to open a video file in the source code folder using VideoCapture I get the error "WARNING : Couldn’t read movie file Alireza_Day1_001.avi". Has anyone faced the same issue ? (FYI VideoCapture from my webcam is working fine, but tried opening a .mov and .avi file without luck) Any help is much appreciated !