Recherche avancée

Sur d’autres sites (6962)

• 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.

  


• Revision 2b8dc065d1 : google style guide include guards Change-Id : I2c252f3ddcc99e96c1f5d3dab8bcb25a2

  30 novembre 2012, par Jim Bankoski

  Changed Paths : Modify /vp9/common/arm/vp9_bilinearfilter_arm.h Modify /vp9/common/arm/vp9_idct_arm.h Modify /vp9/common/arm/vp9_loopfilter_arm.h Modify /vp9/common/arm/vp9_recon_arm.h Modify /vp9/common/arm/vp9_subpixel_arm.h Modify /vp9/common/vp9_alloccommon.h (...)

• google speech to text errors out (grpc invalid deadline NaN)

  15 décembre 2019, par jamescharlesworth

  I have a ffmpeg script that cuts an audio file into a short 5 second clip, however after I cut the file, calling the google speech recognize command errors out.

  Creating a clip - full code link :

  const uri = 'http://traffic.libsyn.com/joeroganexp/p1400.mp3?dest-id=19997';
  
  const command = ffmpeg(got.stream(uri));
  
  command
  
    .seek(0)
  
    .duration(5)
  
    .audioBitrate(128)
  
    .format('mp3')
  
  ...

  which works fine and creates ./clip2.mp3.

  I then take that file and upload it to speech to text api and it times out (script here. When I put timeout and maxRetries argument I can get the actual error :

  Error: 2 UNKNOWN: Getting metadata from plugin failed with error: Deadline is too far in the future
  
      at Object.callErrorFromStatus (/Users/jamescharlesworth/Downloads/demo/node_modules/@grpc/grpc-js/build/src/call.js:30:26)
  
      at Http2CallStream.<anonymous> (/Users/jamescharlesworth/Downloads/demo/node_modules/@grpc/grpc-js/build/src/client.js:96:33)
  
      at Http2CallStream.emit (events.js:215:7)
  
      at /Users/jamescharlesworth/Downloads/demo/node_modules/@grpc/grpc-js/build/src/call-stream.js:98:22
  
      at processTicksAndRejections (internal/process/task_queues.js:75:11) {
  
    code: 2,
  
    details: 'Getting metadata from plugin failed with error: Deadline is too far in the future',
  
    metadata: Metadata { internalRepr: Map {}, options: {} },
  
    note: 'Exception occurred in retry method that was not classified as transient'
  
  }
  
  </anonymous>

  Stepping through the grpc code i see that the deadline is an invalid date.
  
  This seems to be causing the issue but i assume it may be from incorrect params passed into the speech client.recognize() method.

  A few other things to note :

  • The script works for some audio files, not all
  • I can upload the broken my clip mp3 clip2.mp3 to the demo app here and it works fine.
  • If I change the seek command of my ffmpeg script to start at 0.01 speech recognize command will work (however it breaks other audio clips as its not the correct starting point). I notice that when i do this the png of the mp3 gets stripped out and is a much smaller file size