Recherche avancée

Médias (9)

Mot : - Tags -/soundtrack

Autres articles (54)

  • Les autorisations surchargées par les plugins

    27 avril 2010, par

    Mediaspip core
    autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs

  • L’utiliser, en parler, le critiquer

    10 avril 2011

    La première attitude à adopter est d’en parler, soit directement avec les personnes impliquées dans son développement, soit autour de vous pour convaincre de nouvelles personnes à l’utiliser.
    Plus la communauté sera nombreuse et plus les évolutions seront rapides ...
    Une liste de discussion est disponible pour tout échange entre utilisateurs.

  • Contribute to translation

    13 avril 2011

    You can help us to improve the language used in the software interface to make MediaSPIP more accessible and user-friendly. You can also translate the interface into any language that allows it to spread to new linguistic communities.
    To do this, we use the translation interface of SPIP where the all the language modules of MediaSPIP are available. Just subscribe to the mailing list and request further informantion on translation.
    MediaSPIP is currently available in French and English (...)

Sur d’autres sites (9469)

  • avcodec.h and avfiltergraph.h files are not found

    12 avril 2019, par Dries Jans

    I’m testing out a RTSP encoded stream transmitter using mpeg4. I found the code from this topic : FFMPEG to send RTSP encoded stream C++

    I think there is a problem with different build versions. I’m using the
    4.1.1 build.

    I’ve already tried to use the avcodec header in the libavcodec directory, but I have no idea if this is correct because I can’t find a replacement for the avfiltergraph header. I tried replacing it with avfilter header, but this gave an error on the CODEC_ID_H264.

    #include <libavfilter></libavfilter>avfiltergraph.h>
    #include <libavfilter></libavfilter>avcodec.h>

    You also need to execute next command to provide an listening service.

    ffplay -rtsp_flags listen -i rtsp://127.0.0.1:8554/live.sdp
  • Video editing multi customer host in server instances

    1er août 2020, par General Omosco

    I created a multi conference live stream web app using rtc and ffmpeg C api for media stream, videos/images/texts files mixed up together in realtime sending the output to rtmp multiple destinations, but unfortunately my server could not handle more than 2 conference room smoothly.

    &#xA;

    The server which couldn't handle more than two conference room running ffmpeg api

    &#xA;

    It is Comfort plan in OVH&#xA;Type : vps,&#xA;Processor : 4 vCore,&#xA;Ram : 8gb

    &#xA;

    Usage&#xA;CPU : 100% //playing smoothly or not.&#xA;Ram : 3%

    &#xA;

    My question here is that. Is it possible to be creating self isolated instance on fly and automatically deploy the app in the instance for each customer ? And the host provider that can accept that.

    &#xA;

  • 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