Recherche avancée

Sur d’autres sites (5518)

• Why ffmpeg C - API Doxygen document using c++ style of namespace for structure

  25 décembre 2018, par Vencat

  I’m new to ffmpeg C-API and learning it from doxygen document in official site. I hope the document explains about ffmpeg C-API, but I have seen some c++ style of class and namespace in it, for example please refer the below document part, where they are using c++ style of namespace for c structure.

  AVClass Struct Reference :

  https://ffmpeg.org/doxygen/trunk/structAVClass.html#details

  can anyone clear this to me.?

• Delay in video playback. Not able to identify the cause - AWS S3 region / ffmpeg / Videojs

  17 septembre 2016, par Himansu Kisan

  We are not able to identify the cause for random behavior while playing video on our website. (Sorry, cant share a link since the videos are for registered users only)
  The videos sometimes plays instantly and sometimes it takes over 1 minute to start. Not sure what we are doing wrong.

  We are using AWS S3 Oregon region (not the closest to target region, but it is cheaper) to store video files.
  The video files are encoded using ffmpeg. Below is the syntax

  ffmpeg -i input.mts -codec:v libx264 -threads 4 -movflags +faststart -profile:v high -preset slow -b:v 500k -maxrate 500k -bufsize 1000k -vf scale="trunc(oh*a/2)*2:720" "output.mp4"

  ffmpeg -i input.mts -codec:v libvpx -threads 4 -quality good -cpu-used 5 -b:v 500k -maxrate 500k -bufsize 1000k -qmin 10 -qmax 42 -vf scale="trunc(oh*a/2)*2:720" -codec:a libvorbis -b:a 128k "output.webm"

  On website, we are using Videojs 5.10.8.
  Below is the code snippet

   <video class="video-js vjs-default-skin vjs-big-play-centered" preload="none" controls="controls" poster="abcd.jpg" style="width:100%;height:100%;min-height:360px;" data-setup="{&quot;autoplay&quot;:true}">
  
  <source src="abcd.mp4" type="video/mp4"></source>
  
  <source src="adcd.webm" type="video/webm"></source>
  
  <p class="vjs-no-js">
  
      To view this video please enable JavaScript, and consider upgrading to a web browser
  
      that <a href="http://videojs.com/html5-video-support/" target="_blank">supports HTML5 video</a>
  
  </p>
  
  </video>

  What are we doing wrong ? Please help us out.

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