Recherche avancée

Médias (91)

Autres articles (110)

  • MediaSPIP 0.1 Beta version

    25 avril 2011, par

    MediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
    The zip file provided here only contains the sources of MediaSPIP in its standalone version.
    To get a working installation, you must manually install all-software dependencies on the server.
    If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...)

  • Multilang : améliorer l’interface pour les blocs multilingues

    18 février 2011, par

    Multilang est un plugin supplémentaire qui n’est pas activé par défaut lors de l’initialisation de MediaSPIP.
    Après son activation, une préconfiguration est mise en place automatiquement par MediaSPIP init permettant à la nouvelle fonctionnalité d’être automatiquement opérationnelle. Il n’est donc pas obligatoire de passer par une étape de configuration pour cela.

  • Amélioration de la version de base

    13 septembre 2013

    Jolie sélection multiple
    Le plugin Chosen permet d’améliorer l’ergonomie des champs de sélection multiple. Voir les deux images suivantes pour comparer.
    Il suffit pour cela d’activer le plugin Chosen (Configuration générale du site > Gestion des plugins), puis de configurer le plugin (Les squelettes > Chosen) en activant l’utilisation de Chosen dans le site public et en spécifiant les éléments de formulaires à améliorer, par exemple select[multiple] pour les listes à sélection multiple (...)

Sur d’autres sites (9414)

  • 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
  • what's the recommended CDN or Hosting should I use for online media converter app ? [on hold]

    20 novembre 2017, par Moe D.

    I’m working on web application that will let users download videos from facebook, twitter and vimeo as MP4 or MP3.

    I don’t know what’s the recommended CDN or Hosting plan or product I should use to can host all these big media files ( mp3 and mp4 ) with a lot of download requests per hour and to be affordable in the same time ?

    And will auto deleting files that older than 6 hours on the cloud save some cloud storage costs ?