Recherche avancée

Sur d’autres sites (8991)

• Node 18 or Node 20 break ffmpeg (in google cloud functions -> ffprobe was killed with signal SIGSEGV)

  10 janvier 2024, par user20206929

  Please see below, the code is working on node js 16, but not when upgrading to node 18 or 20.

  


  const ffmpeg = require("fluent-ffmpeg");

// Following is inside a .https.onRequest Google Cloud function with enough memory

try {
  const duration = new Promise((resolve, reject) => {
  ffmpeg.ffprobe(videoUrl, async (err, metadata) => {
    if (err) {
      if (res.headersSent) {
        console.error("Response already sent");
        return;
      } else {
        console.log("Metadata:", metadata);
        console.log("err: " + err);
        res.status(400).send("Error getting video metadata");
        return;
      }
    }
  const duration = metadata.format.duration;
  console.log("video duration in second: " + duration);
  resolve(duration);
  });
});
  videoDuration = await duration;
} catch (err) {
  console.log(err);
  throw err;
}


  


  When upgrading to node 18/20 (No other change than upgrading node), the error "ffprobe not found" appears.

  


  But setting the path manually using ffmpeg.setFfprobePath(ffprobePath) ;
trigger the error : Error : ffprobe was killed with signal SIGSEGV

  


  So it seem its a permissions issue.

  


  However, I tried a lot of different solutions, none of them made this work.
For instance i tried to download manually the ffprobe from the official website https://ffbinaries.com/downloads. Then manually add it to the code.

  


  I tried to use https://www.npmjs.com/package/@ffprobe-installer/ffprobe or others package like https://www.npmjs.com/package/ffprobe-static

  


  I also tried to download the ffprobe file to the temporary folder of google cloud, and change the permission of this folder.

  


  All of those was doing the same error.

  


  None of what i could think of made any difference.

  


  Please help because i need to update node 16 to 18 or 20 before google remove node 16 on january 31 2024 and for now i don't see a solution.

  


  I also looked for other solution to get this duration from a video file url, but using ffmpeg seem to be the only one that should work out of the box. As it is working on node 16.

  


  Thank you,

  


  UPDATE - 11/26/2023

  


  GCP Functions NodeJS 16 runtime uses Ubuntu 18.04 with FFMpeg installed.
NodeJS 18/20 use Ubuntu 22.04, and Google decided not to include FFMpeg.

  


  https://cloud.google.com/functions/docs/runtime-support#node.js
https://cloud.google.com/functions/docs/reference/system-packages

  


  No workaround or solutions found as of now

  


  UPDATE - 01/10/2024

  


  Google added back ffmpeg to latest version, this is working as before now.

  


• Does anybody know how to concat on ffmpeg and python ? [closed]

  22 décembre 2023, par Jonas Harker

  I created a code on Python that supposedly concatenates two videos using Python to run an ffmpeg command through subprocess.
I get this error message :

  


  2c0] Could not open encoder before EOF
[vost#0:0/libx264 @ 0000024013bfa480] Task finished with error code: -22 (Invalid argument)
[aost#0:1/aac @ 0000024013bfb2c0] Task finished with error code: -22 (Invalid argument)
[aost#0:1/aac @ 0000024013bfb2c0] Terminating thread with return code -22 (Invalid argument)
[vost#0:0/libx264 @ 0000024013bfa480] Terminating thread with return code -22 (Invalid argument)
[out#0/mp4 @ 0000024013b91d80] Nothing was written into output file, because at least one of its streams received no packets.
frame=    0 fps=0.0 q=0.0 Lsize=       0kB time=N/A bitrate=N/A speed=N/A    
Conversion failed!
El archivo Batman - Mask of The Phantasm, Open Matte Version (1993 - 1080p BluRay)_segment_11_segment_2.mp4 ha sido procesado.
El archivo temporal output_temp.mp4 ha reemplazado a Batman - Mask of The Phantasm, Open Matte Version (1993 - 1080p BluRay)_segment_11_segment_2.mp4.
Ejecutando: ffmpeg -i "D:\BTO\MemeLaughnClap\Shorted\Batman - Mask of The Phantasm, Open Matte Version (1993 - 1080p BluRay)_segment_11_segment_3.mp4" -i "D:\BTO\MemeLaughnClap\Media\FV.mp4" -filter_complex concat=n=2:v=1:a=1 -c:v libx264 -preset medium -crf 23 -c:a aac -b:a 192k -y "D:\BTO\MemeLaughnClap\Shorted\output_temp.mp4"
ffmpeg version 2023-12-18-git-be8a4f80b9-full_build-www.gyan.dev Copyright (c) 2000-2023 the FFmpeg developers
  built with gcc 12.2.0 (Rev10, Built by MSYS2 project)


  


  I hoped they would concat, but they did not.

  


• machine hangs during ffmpeg command execution [closed]

  15 décembre 2023, par Tejas

  I'm running this ffmpeg command that does multiple trims on input video and concats those trims to generate output.

  


  ffmpeg -i https://d8r14y803bnlk.cloudfront.net/usetldr/2736037/u/796/st/5a919413ff884892bbfffcd0671687a9/p/67c1a16438bf4bb78b785557f4cef7ef/OJx1SIKTNbbGHmQfKT4C_render.mp4 -filter_complex "[0:v:0]trim=start=0.0:end=4.289,setpts=PTS-STARTPTS,format=yuva420p[0v];[0:v:0]trim=start=4.84:end=1034.7,setpts=PTS-STARTPTS,format=yuva420p[1v];[0v][1v]concat=n=2:v=1:a=0" -crf 18 -an -preset ultrafast -y /tmp/8TZeqB3Z6h.mp4


  


  This command works fine on my M1 mac but hangs EC2 instances (c5.4xlarge).

  


  I'm using ffmpeg version 6.1-static https://johnvansickle.com/ffmpeg/  Copyright (c) 2000-2023 the FFmpeg developers built with gcc 8 (Debian 8.3.0-6) on EC2.

  


  Any idea why this could be happening ?