Recherche avancée

Sur d’autres sites (12042)

• Node js request huge amount of pictures

  5 janvier 2019, par Manos Koutselakis

  I am trying to request a huge amount of images on node js (n > 3000)
  and then save them into a folder.
  I have tried using request library and request-promise.
  The problem is that if the number of pictures is too big some pictures do not complete downloading, leaving incomplete data or get an error(an empty .jpeg file). Is there a better way of downloading huge amounts of pictures ?
  Also i need when the pictures all download to request a function compile()
  to make them into a video. I am using ffmpeg for that.

  Below are 2 ways i tried doing this.

  const req = require('request');
  
  const request = require('request-promise');
  
  const fs = require('fs');
  
  const ffmpegPath = require('@ffmpeg-installer/ffmpeg').path;
  
  const ffmpeg = require('fluent-ffmpeg');
  
  ffmpeg.setFfmpegPath(ffmpegPath);
  
  
  
  function downloadImgs(imgUrls) {
  
    let promises = [];
  
    let prom;
  
    for (let i = 0; i < imgUrls.length; i++) {
  
      imgPath = `assets/pics/st_${pad(i + 1, 3)}.jpg`
  
  
  
      prom = request(imgUrls[i]);
  
      prom.on('error', () => console.log('err'));
  
      prom.pipe(fs.createWriteStream(imgPath));
  
      promises.push(prom);
  
    }
  
  
  
    Promise.all(promises).then(() => {
  
      console.log('I Run');
  
      compilee();
  
    });
  
  
  
    //SECOND TRY-----------------------------------------
  
    for (let i = 0; i < imgUrls.lengh; i++) {
  
      imgUrl = imgUrls[i];
  
      req(imgUrl)
  
        .on('error', () => console.log("img error", imgUrl))
  
        .pipe(fs.createWriteStream(`assets/pics/st_${pad(i + 1, 3)}.jpg`)).on('close', () => {
  
          console.log('downloaded', x)
  
        })
  
    }
  
    compilee();
  
  
  
  //---------------------------------------------------------
  
  
  
    function compilee() {
  
      command
  
        .on('end', onEnd)
  
        // .on('progress', onProgress)
  
        .on('error', onError)
  
        .input('assets/pics/st_%03d.jpg')
  
        .inputFPS(5)
  
        .output('assets/output/pepe.mp4')
  
        .outputFps(30)
  
        .run();
  
    }

  The errors i am getting for the first : UnhandledPromiseRejectionWarning : RequestError : Error : socket hang up

  and the second :
  Error : socket hang up
  at createHangUpError (_http_client.js:330:15)
  at TLSSocket.socketOnEnd (_http_client.js:433:23)
  at TLSSocket.emit (events.js:187:15)
  at endReadableNT (_stream_readable.js:1098:12)
  at process.internalTickCallback
  (internal/process/next_tick.js:72:19) code : ’ECONNRESET’ }

  Also, should i download the pictures on the server or on the client if i want to sent the video to the client immediately.

• ffmpeg : always use single threaded decoding for attached pictures

  6 octobre 2017, par Marton Balint

  ffmpeg : always use single threaded decoding for attached pictures
  Since af1761f7b5b1b72197dc40934953b775c2d951cc ffmpeg waits for a frame in each
  
  stream before writing the output header. If we are using threaded decoding for
  
  attached pictures, we have to read till EOF to be able to finally flush the
  
  decoder and output the decoded frame. This essentially makes ffmpeg buffer all
  
  non-attached picture packets, which will cause a "Too many packets buffered for
  
  output stream" eventually.
  By forcing single threaded decoding, we get a frame from a single packet as
  
  well and we can avoid the error.
  Fixes part of ticket #6375 :
  
  ffmpeg -i 46564100.mp3 -acodec libmp3lame -ab 128k -ac 2 out.mp3
  Reviewed-by : Hendrik Leppkes <h.leppkes@gmail.com>
  
  Signed-off-by : Marton Balint <cus@passwd.hu>
  

  • [DH] fftools/ffmpeg.c

• build : change checkheaders to use regular build rules

  7 août 2012, par Mans Rullgard

  build : change checkheaders to use regular build rules