Recherche avancée

Sur d’autres sites (3329)

• Why is "ffmpeg : command not found" in heroku, even with proper buildpack/config ?

  14 novembre 2022, par Jim

  In a node.js app hosted on heroku, ffmpeg is used by spawning processes, but is throwing errors anytime an ffmpeg command runs

  


  the error ffmpeg: command not found is thrown both in cli test heroku run ffmpeg as well as production logs

  


  Ive considered :

  


  

  • buildpack order

  


  • buildpack clearing/re-adding/redeploying

  


  • buildpack required env vars

  


  • heroku-stack-20 conflicts with buildpack#1 somehow ?

  


  


  Buildpack order :

  


  

  1. https://github.com/jonathanong/heroku-buildpack-ffmpeg-latest.git

  


  2. https://github.com/heroku/heroku-buildpack-awscli.git

  


  3. https://github.com/timanovsky/subdir-heroku-buildpack.git

  


  4. heroku/nodejs

  


  


  Buildpack configs - from watching build logs, even though i havent set ffmpeg path, a default is found.

  


  beginning build logs (completes successfully, runs successfully - minus ffmpeg) :

  


  -----> Building on the Heroku-20 stack
-----> Using buildpacks:
       1. https://github.com/jonathanong/heroku-buildpack-ffmpeg-latest.git
       2. https://github.com/xrisk/heroku-opus.git
       3. https://github.com/heroku/heroku-buildpack-awscli.git
       4. https://github.com/timanovsky/subdir-heroku-buildpack.git
       5. heroku/nodejs
-----> ffmpeg app detected
-----> Installing ffmpeg
       Variable FFMPEG_DOWNLOAD_URL isn't set, using default value
       Downloading https://johnvansickle.com/ffmpeg/builds/ffmpeg-git-amd64-static.tar.xz
       Unpacking the archive
       Installation successful
-----> heroku-opus app detected
       exporting PATH and LIBRARY_PATH
-----> Building in /tmp/build_51b5ac83/opus
-----> Starting opus compilation
       Downloading opus-1.3.1.tar.gz
       Unpacking opus
       Running configure
       Running make install
-----> AWS CLI app detected
-----> Downloading AWS CLI
-----> Installing AWS CLI
       You can now run: /app/.awscli/bin/aws --version
       aws-cli/2.8.12 Python/3.9.11 Linux/4.4.0-1104-aws exe/x86_64.ubuntu.20 prompt/off
-----> Successfully installed AWS CLI
-----> Subdir buildpack app detected
-----> Subdir buildpack in server
       creating cache: /tmp/codon/tmp/cache
       created tmp dir: /tmp/codon/tmp/cache/subdirBuBFb
       moving working dir: server to /tmp/codon/tmp/cache/subdirBuBFb
       cleaning build dir /tmp/build_51b5ac83
       copying preserved work dir from cache /tmp/codon/tmp/cache/subdirBuBFb to build dir /tmp/build_51b5ac83
       cleaning tmp dir /tmp/codon/tmp/cache/subdirBuBFb
-----> Node.js app detected


  


  Any suggestions to further debug this ?

  


• Is there any memory problem that "Too many active WebGL contents." keeps coming out in my web console

  18 novembre 2022, par jerry

  

  


  Now I'm using RTSP stream with jsmpeg, ffmpeg, node-rtsp-stream in React.js

  


  I set multiple streaming in react component about 1 to maximum 25

  


  and when I change route to many , It apeard my console

  


  I'm a little afraid of if it caused by memory leak problem

  


  I cannot figure out it is okay or critical problem

  


  Could you tell me how to solve this problem or is it fine

  


  &#xA;// out of component&#xA;const streams: Streams = {};&#xA;&#xA;...&#xA;&#xA;  const { preset } = props;&#xA;&#xA;  const elementsRef = useRef<any>(new Array(preset?.partition).fill(0).map((v) => createRef()));&#xA;&#xA;&#xA;  // Mount&#xA;  useEffect(() => {&#xA;    const { JSMpeg } = window;&#xA;&#xA;    const sortedStream = _.sortBy(preset?.stream, ["position"]);&#xA;    console.log(sortedStream);&#xA;&#xA;&#xA;    sortedStream.forEach((v, i: number) => {&#xA;&#xA;      const player = new JSMpeg.Player(v.camera_monitoring.ws, {&#xA;        canvas: elementsRef?.current[v.position]?.current, // Canvas should be a canvas DOM element&#xA;      });&#xA;      console.dir(elementsRef?.current[v.position]?.current);&#xA;&#xA;      streams[v.id] = player;&#xA;    });&#xA;  }, []);&#xA;&#xA;  // UnMount&#xA;  useEffect(() => {&#xA;    return () => {&#xA;      Object.keys(streams).forEach((v) => {&#xA;        console.log("unmount key:", v);&#xA;        if (streams[v] !== null) {&#xA;          streams[v].destroy();&#xA;          streams[v] = null;&#xA;        }&#xA;      });&#xA;    };&#xA;  }, []);&#xA;&#xA;&#xA;&#xA;... &#xA;</any>

  


  https://github.com/phoboslab/jsmpeg

  


  above library `jsmpeg.min.js` is set by global ( in public directory and set in my html )

  


  actually my code are so many antipattern in contrast react style, To make an excuse, It is my limits of one's ability

  


• How to resolve "ffmpeg was killed with signal SIGSEGV" in docker container

  25 juin 2024, par Gmanicus

  I have a Node.js application deployed to a docker container with fluent-ffmpeg, @ffmpeg-installer/ffmpeg, and @ffprobe-installer/ffmprobe.

  


  Here is the fluent-ffmpeg init script :

  


  import ffmpeg = require('fluent-ffmpeg');
const ffmpegPath = require('@ffmpeg-installer/ffmpeg').path;
const ffprobePath = require('@ffprobe-installer/ffprobe').path;

ffmpeg.setFfmpegPath(ffmpegPath);
ffmpeg.setFfprobePath(ffprobePath);

export default ffmpeg;


  


  This gets used to take a snapshot of a video and save that image to file :

  


  ffmpeg('ism manifest here')
        .inputOption(`-ss timestamp`)
        .outputOptions([
            '-vframes 1',
            '-vf crop=640:230:320:490,eq=saturation=0:contrast=1000,negate'
        ])
        .output('test.png')
        .run();


  


  Whenever any configuration of ffmpeg command is run, it nearly instantaneously fails with :

  


  Error: ffmpeg was killed with signal SIGSEGV&#xA;     at ChildProcess.<anonymous> (/app/node_modules/fluent-ffmpeg/lib/processor.js:180:22)&#xA;     at ChildProcess.emit (node:events:517:28)&#xA;     at Process.ChildProcess._handle.onexit (node:internal/child_process:292:12)&#xA;</anonymous>

  


  I have attempted to raise the memory and CPU usage limits of the server in the docker-compose file :

  


  ...
    deploy:
      resources:
        limits:
          cpus: '0.75'
          memory: 2G
        reservations:
          cpus: '0.50'
          memory: 1G


  


  But nothing has worked. Running this on my local machine works just fine. Help ?

  


  UPDATE :

  


  I just attempted running a small dockerized ffmpeg test script on its own in its own brand new container. Same issue. So, it doesn't seem to have anything to do with my server's configuration.