Recherche avancée

Médias (1)

Mot : - Tags -/graphisme

Autres articles (54)

  • Déploiements possibles

    31 janvier 2010, par

    Deux types de déploiements sont envisageable dépendant de deux aspects : La méthode d’installation envisagée (en standalone ou en ferme) ; Le nombre d’encodages journaliers et la fréquentation envisagés ;
    L’encodage de vidéos est un processus lourd consommant énormément de ressources système (CPU et RAM), il est nécessaire de prendre tout cela en considération. Ce système n’est donc possible que sur un ou plusieurs serveurs dédiés.
    Version mono serveur
    La version mono serveur consiste à n’utiliser qu’une (...)

  • Websites made ​​with MediaSPIP

    2 mai 2011, par

    This page lists some websites based on MediaSPIP.

  • Use, discuss, criticize

    13 avril 2011, par

    Talk to people directly involved in MediaSPIP’s development, or to people around you who could use MediaSPIP to share, enhance or develop their creative projects.
    The bigger the community, the more MediaSPIP’s potential will be explored and the faster the software will evolve.
    A discussion list is available for all exchanges between users.

Sur d’autres sites (7589)

  • ffmpeg throwing "errorMessage" : "spawn ffmpeg ENOENT"

    25 avril 2016, par user2792129

    My ffmpeg function thats running as a shell command isnt working. I think its because ’ffmpeg’ isnt really referring to anything. I have the ffmpeg node module in my bundle, but i dont know the execFile command is referring to it here.

    Im following aws-lambda-ffmpeg as an example of how to call this particular function. They are referring to ’ffmpeg’ as a 64-bit linux build they created from John Vansickle’s static FFMPEG builds in their gulp function.

    I want to know how to replace ’ffmpeg’ with something that will just recognize it like a node_module without having to do the whole gulp static build process. To my understanding the only reason they are doing that is to get the latest build which i really dont need.

    If I am wrong and a static build using gulp is needed for another reason please let me know.

    function ffmpegProcess(description, cb) {
    console.log('Starting FFmpeg');

    child_process.execFile(
       'ffmpeg',
       [
           '-y',
           '-loglevel', 'warning',
           '-i', 'download',
           '-c:a', 'copy',
           '-vf', scaleFilter,
           '-movflags', '+faststart',
           '-metadata', 'description=' + description,
           'out.' + config.format.video.extension,
           '-vf', 'thumbnail',
           '-vf', scaleFilter,
           '-vframes', '1',
           'out.' + config.format.image.extension
       ],
       {
           cwd: tempDir
       },
       function(err, stdout, stderr) {
           console.log('FFmpeg done.');
           return cb(err, 'FFmpeg finished:' + JSON.stringify({ stdout: stdout, stderr: stderr}));
       }
    );
    }
  • ffmpeg throwing "errorMessage" : "spawn ffmpeg ENOENT"

    4 juin 2024, par ian

    My ffmpeg function thats running as a shell command isnt working. I think its because 'ffmpeg' isnt really referring to anything. I have the ffmpeg node module in my bundle, but i dont know the execFile command is referring to it here.

    



    Im following aws-lambda-ffmpeg as an example of how to call this particular function. They are referring to 'ffmpeg' as a 64-bit linux build they created from John Vansickle's static FFMPEG builds in their gulp function.

    



    I want to know how to replace 'ffmpeg' with something that will just recognize it like a node_module without having to do the whole gulp static build process. To my understanding the only reason they are doing that is to get the latest build which i really dont need.

    



    If I am wrong and a static build using gulp is needed for another reason please let me know.

    



    function ffmpegProcess(description, cb) {
console.log('Starting FFmpeg');

child_process.execFile(
    'ffmpeg',
    [
        '-y',
        '-loglevel', 'warning',
        '-i', 'download',
        '-c:a', 'copy',
        '-vf', scaleFilter,
        '-movflags', '+faststart',
        '-metadata', 'description=' + description,
        'out.' + config.format.video.extension,
        '-vf', 'thumbnail',
        '-vf', scaleFilter,
        '-vframes', '1',
        'out.' + config.format.image.extension
    ],
    {
        cwd: tempDir
    },
    function(err, stdout, stderr) {
        console.log('FFmpeg done.');
        return cb(err, 'FFmpeg finished:' + JSON.stringify({ stdout: stdout, stderr: stderr}));
    }
);
}


    


  • avfilter/vf_bwdif : Add neon for filter_line3

    4 juillet 2023, par John Cox
    avfilter/vf_bwdif : Add neon for filter_line3
    

    Signed-off-by : John Cox <jc@kynesim.co.uk>
    Signed-off-by : Martin Storsjö <martin@martin.st>

    • [DH] libavfilter/aarch64/vf_bwdif_init_aarch64.c
    • [DH] libavfilter/aarch64/vf_bwdif_neon.S