Recherche avancée

Sur d’autres sites (7604)

• unable to read stderr

  24 septembre 2020, par Sarmad S.

  I have the following code, which works fine locally :

  


  const child_process = require("child_process");
const path = require("path");

exports.handler = async (event) => {

   var ffprobePath = path.resolve(__dirname, 'ffmpeg-static', 'ffprobe');
   var ffmpegPath = path.resolve(__dirname, 'ffmpeg-static', 'ffmpeg');


   var ffprobeArgs = [
       '-i', 'tb.jpg'
   ]

   var proc = child_process.spawnSync(ffprobePath, ffprobeArgs);

   console.log(proc.stderr.toString()) //toString on null object (stderr is null).


   const response = {
       statusCode: 200,
       body: JSON.stringify("Some text here"),
   };

   return response;
};


  


  However, when uploaded to aws lambda, and invoked, stderr is null.

  


  What am I doing wrong ?

  


• avcodec/tiff : Avoid forward declarations

  30 mars 2021, par Andreas Rheinhardt

  avcodec/tiff : Avoid forward declarations
  In this case it also fixes a potential for compilation failures :
  
  Not all compilers can handle the case in which a function with
  
  a forward declaration declared with an attribute to always inline it
  
  is called before the function body appears. E.g. GCC 4.2.1 on OS X 10.6
  
  doesn't like it.
  Reviewed-by : Pavel Koshevoy <pkoshevoy@gmail.com>
  
  Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
  

  • [DH] libavcodec/tiff.c

• When I use Fluent-Ffmpeg to access Ffmpeg, there are two different threads but I dont want it

  25 mars 2019, par Ahmet Hakan Billur

  I try to broadcast with rtsp live stream from IP camera on web app that is improved with node.js-jsmpeg([a link]https://www.npmjs.com/package/fluent-ffmpeg !), web socket, html5(canvas).Everything ok that live streaming works but missing frame and high CPU usaged by streaming on web app and I try to reduce so I can intervene ffmpeg with fluent-ffmpeg but when I monitor CPU usaged I can see there 2 different threads following as and look at screenshot of CPU ;
  

  ffmpeg -rtsp_trasport tcp -i rtsp ://10.6.0.225 -f mpeg1video - is worked by jsmpeg and canvas/html5
  index.html

      
  
  
  
      
  
      
  
      
  
      
  
  
  
      <div><canvas width="640" height="360"></canvas></div>
  
      div><canvas width="640" height="360"></canvas>  
  
      <code class="echappe-js">&lt;script type=&quot;text/javascript&quot; src='http://stackoverflow.com/feeds/tag/jsLib/jsmpeg.js'&gt;&lt;/script&gt;
      
  &lt;script type=&quot;text/javascript&quot; src='http://stackoverflow.com/feeds/tag/jsLib/ffmpegUtil.js'&gt;&lt;/script&gt;
  &lt;script type=&quot;text/javascript&quot;&gt;<br />
  
        var canvas = document.getElementById('videoCanvas');<br />
  
        var ws = new WebSocket(&quot;ws://10.6.0.206:9999&quot;)<br />
  
        var player = new jsmpeg(ws, {canvas:canvas, autoplay:true,audio:false,loop: true});<br />
  
      &lt;/script&gt;
  

  other one /usr/bin/ffmpeg -i rtsp ://10.6.0.225 -y out.ts is work by following piece of code in app.js

  Stream = require('node-rtsp-stream');
  
  stream = new Stream({
  
      name: 'name',
  
      streamUrl: 'rtsp://10.6.0.225',
  
      wsPort: 9999
  
  });
  
  
  
  var ffmpeg = require('fluent-ffmpeg');
  
  var proc = new ffmpeg();
  
  
  
  proc
  
  .addInput('rtsp://10.6.0.225')
  
  .on('start', function(ffmpegCommand) {
  
      /// log something maybe
  
      console.log('start-->'+ffmpegCommand)
  
  })
  
  .on('progress', function(data) {
  
      /// do stuff with progress data if you want
  
      console.log('progress-->'+data)
  
  })
  
  .on('end', function() {
  
      /// encoding is complete, so callback or move on at this point
  
      console.log('end-->')
  
  })
  
  .on('error', function(error) {
  
      /// error handling
  
      console.log('error-->'+error)
  
  
  
  })
  
  .output('out.ts')
  
  .run();

  and then I don’t want to get two different ffmpeg command threads in there.
  Does anyone have an idea ?
  Thanks in advice.