Recherche avancée

Médias (0)

Mot : - Tags -/médias

Aucun média correspondant à vos critères n’est disponible sur le site.

Autres articles (38)

  • Le plugin : Podcasts.

    14 juillet 2010, par

    Le problème du podcasting est à nouveau un problème révélateur de la normalisation des transports de données sur Internet.
    Deux formats intéressants existent : Celui développé par Apple, très axé sur l’utilisation d’iTunes dont la SPEC est ici ; Le format "Media RSS Module" qui est plus "libre" notamment soutenu par Yahoo et le logiciel Miro ;
    Types de fichiers supportés dans les flux
    Le format d’Apple n’autorise que les formats suivants dans ses flux : .mp3 audio/mpeg .m4a audio/x-m4a .mp4 (...)

  • MediaSPIP v0.2

    21 juin 2013, par

    MediaSPIP 0.2 is the first MediaSPIP stable release.
    Its official release date is June 21, 2013 and is announced here.
    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 (...)

  • Personnaliser en ajoutant son logo, sa bannière ou son image de fond

    5 septembre 2013, par

    Certains thèmes prennent en compte trois éléments de personnalisation : l’ajout d’un logo ; l’ajout d’une bannière l’ajout d’une image de fond ;

Sur d’autres sites (6197)

  • 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}));
    }
);
}


    


  • avformat/hls : don't propagate deprecated "user-agent" AVOption

    28 avril 2018, par wm4
    avformat/hls : don't propagate deprecated "user-agent" AVOption

    This code will print a warning if any user agent is set - even if the
    
API user used the proper non-deprecated "user_agent" option.
    

    This change should not even break anything, because even if the user
    
sets the deprecated "user-agent" option, http.c copies it to the
    
"user_agent" option anyway.
    • [DH] libavformat/hls.c

Navigation