Recherche avancée

Médias (91)

Autres articles (111)

  • MediaSPIP version 0.1 Beta

    16 avril 2011, par

    MediaSPIP 0.1 beta est la première version de MediaSPIP décrétée comme "utilisable".
    Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
    Pour avoir une installation fonctionnelle, il est nécessaire d’installer manuellement l’ensemble des dépendances logicielles sur le serveur.
    Si vous souhaitez utiliser cette archive pour une installation en mode ferme, il vous faudra également procéder à d’autres modifications (...)

  • Dépôt de média et thèmes par FTP

    31 mai 2013, par

    L’outil MédiaSPIP traite aussi les média transférés par la voie FTP. Si vous préférez déposer par cette voie, récupérez les identifiants d’accès vers votre site MédiaSPIP et utilisez votre client FTP favori.
    Vous trouverez dès le départ les dossiers suivants dans votre espace FTP : config/ : dossier de configuration du site IMG/ : dossier des média déjà traités et en ligne sur le site local/ : répertoire cache du site web themes/ : les thèmes ou les feuilles de style personnalisées tmp/ : dossier de travail (...)

  • 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 (16098)

  • Find videos with specific codec in a directory and move them to another directory [closed]

    31 janvier 2020, par sergeantSalty

    iam trying to find all videos in a directory that have the h264 codec and then move them to another directory.
    The problem iam facing is not to move them but to find the videos.

    Here is what I have so far.

    > @echo off
    set "ffprobe=C:\ffmpeg\bin\ffprobe.exe -v error -select_streams v:0 -show_entries stream=codec_name -of default=noprint_wrappers=1:nokey=1"
    FOR /R %%f IN (*.mkv) DO (

    %ffprobe% "%%f"
    )  
    PAUSE()

    When I run this, I see the codecs in cmd correctly. But when I try to compare the codec and then move them it wont do anything.

    Some pseudocode

    if outputOfFFprobe == "h264" then move

    How can I compare the output from ffprobe.exe to the string "h264" and if it matches then move the file to another directory.

    Iam grateful for any suggestions !

  • Video - Could not find tag for codec wavpack in stream #1, codec not currently supported in container Could not write file MKV to MP4 with FFmpeg

    9 janvier, par Theagames10

    Trying to convert an hour long MKV file into an MP4 using FFmpeg, but during the conversion process it keeps giving me this error :

    



    Could not find tag for codec wavpack in stream #1, codec not currently supported in container
Could not write header for output file #0 (incorrect codec parameters ?): Invalid argument


    



    I have tried to use other converters, but they all have file size limits, It takes to long to convert with Handbrake and VLC. I tried to search for some kind of answer on google, but there has been no forum posts anywhere for a solution to this kind of issue.

    


  • Firebase function error : Cannot find ffmpeg

    9 janvier 2020, par Nathan

    I’m using the firebase storage to execute a function when a video gets uploaded to the default bucket, in the function I’m using Ffmpeg to convert the video and set some other options like size, then I want to reupload the file back to storage and I keep getting this error :

    Error: Cannot find ffmpeg
    at /srv/node_modules/fluent-ffmpeg/lib/processor.js:136:22
    at FfmpegCommand.proto._getFfmpegPath (/srv/node_modules/fluent-ffmpeg/lib/capabilities.js:90:14)
    at FfmpegCommand.proto._spawnFfmpeg (/srv/node_modules/fluent-ffmpeg/lib/processor.js:132:10)
    at FfmpegCommand.proto.availableFormats.proto.getAvailableFormats (/srv/node_modules/fluent-ffmpeg/lib/capabilities.js:517:10)
    at /srv/node_modules/fluent-ffmpeg/lib/capabilities.js:568:14
    at nextTask (/srv/node_modules/async/dist/async.js:4578:27)
    at Object.waterfall (/srv/node_modules/async/dist/async.js:4589:9)
    at Object.awaitable(waterfall) [as waterfall] (/srv/node_modules/async/dist/async.js:208:32)
    at FfmpegCommand.proto._checkCapabilities (/srv/node_modules/fluent-ffmpeg/lib/capabilities.js:565:11)
    at /srv/node_modules/fluent-ffmpeg/lib/processor.js:298:14

    I have used npm install to install both fluent-ffmpeg and ffmpeg-static yet it says it cannot find it ? Here’s my code :

    const ffmpeg = require('fluent-ffmpeg');
    const ffmpeg_static = require('ffmpeg-static');
    const {Storage} = require('@google-cloud/storage');
    const fs = require('fs');
    const os = require('os');
    var path = require('path');

    // Creates a client
    const storage = new Storage({
    projectId: 'projectID',
    });

    function promisifyCommand(command) {
    return new Promise((resolve, reject) => {
     command.on('end', resolve).on('error', reject).run();
    });
    }

    exports.updatePost = functions.storage.object().onFinalize(async (object) => {

    const fileBucket = object.bucket; // The Storage bucket that contains the file.
    const filePath = object.name; // File path in the bucket.
    const contentType = object.contentType; // File content type.
    const resourceState = object.resourceState; // The resourceState is 'exists' or 'not_exists' (for file/folder deletions).
    const metageneration = object.metageneration; // Number of times metadata has been generated. New objects have a value of 1.

    // Get file name
    const fileName = path.basename(filePath);

    // Exit if this is a move or deletaion event.
    if(resourceState === 'not_exists'){
       console.log('This is a deletion event');
       return;
    }

    // Download file from bucket
    const bucket = storage.bucket(fileBucket);
    const tempFilePath = path.join(os.tmpdir(), fileName)
    // We add a '_output.flac' suffix to target audio file name. That's where we'll upload the converted audio.
    const targetTempFileName = fileName.replace(/\.[^/.]+$/, "") + '_output.mp4';
    const targetTempFilePath = path.join(os.tmpdir(), targetTempFileName);
    const targetStorageFilePath = path.join(path.dirname(filePath), targetTempFileName);

    await bucket.file(filePath).download({destination: tempFilePath});
       console.log('Video downloaded locally to', tempFilePath);
       // Convert the video to suitable formats
       const command = ffmpeg(tempFilePath)
       .setFfmpegPath(ffmpeg_static.path)
       .withSize('50%')
       .toFormat('mp4')
       .output(targetTempFilePath);
       await promisifyCommand(command);
           console.log('New video created');

           //Upload video again
           await bucket.upload(targetTempFilePath, {destination: targetStorageFilePath});
               console.log('Output video uploaded to', targetStorageFilePath);
               // Delete the local file from server as it's been uploaded to storage
               fs.unlinkSync(tempFilePath);
               fs.unlinkSync(targetTempFilePath);

               console.log('Tempory files removed.', targetTempFilePath);
    });

    I have searched everywhere and people are also saying that running the ffmpeg module on the function will also exceed the limit very quickly and where told to use ffmpeg-static instead ?
    Thanks,

    Nathan