Recherche avancée

Médias (91)

Autres articles (38)

  • Personnaliser les catégories

    21 juin 2013, par

    Formulaire de création d’une catégorie
    Pour ceux qui connaissent bien SPIP, une catégorie peut être assimilée à une rubrique.
    Dans le cas d’un document de type catégorie, les champs proposés par défaut sont : Texte
    On peut modifier ce formulaire dans la partie :
    Administration > Configuration des masques de formulaire.
    Dans le cas d’un document de type média, les champs non affichés par défaut sont : Descriptif rapide
    Par ailleurs, c’est dans cette partie configuration qu’on peut indiquer le (...)

  • Publier sur MédiaSpip

    13 juin 2013

    Puis-je poster des contenus à partir d’une tablette Ipad ?
    Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir

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

  • Upload FFmpeg output directly to Amazon S3

    26 octobre 2017, par user1790300

    I am using the fluent-ffmpeg library with node.js to transcode videos originally in a flash movie format to the mp3 format with multiple resolutions, 1080p, etc.. Once the transcoding is complete, I would like to move the transcoded video to an s3 bucket.

    I pull the original .flv file from a source s3 bucket and pass the stream to the ffmpeg constructor function. The issue is after the transcoding completes, how do I then get the stream of the mp4 data to send to s3.

    Here is the code I have so far :

           var params = {
               Bucket: process.env.SOURCE_BUCKET,
               Key: fileName
           };
           s3.getObject(params, function(err, data) {
               if (err) console.log(err, err.stack); // an error occurred

               var format = ffmpeg(data)
               .size('854x480')
               .videoCodec('libx264')
               .format('flv')
               .toFormat('mp4');
               .on('end', function () {
                   //Ideally, I would like to do the uploading here

                   var params = {
                      Body: //{This is my confusion, how do I get the stream to add here?},
                      Bucket: process.env.TRANSCODED_BUCKET,
                      Key: fileName
                   };
                   s3.putObject(params, function (err, data) {

                  });
               })
               .on('error', function (err) {
                   console.log('an error happened: ' + err.message);
               });

           });

    For the code above, where can I get the transcoded stream to add to the "Body" property of the params object ?

    Update :

    Here is a revision of what I am trying to do :

    var outputStream: MemoryStream = new MemoryStream();

           var proc = ffmpeg(currentStream)
               .size('1920x1080')
               .videoCodec('libx264')
               .format('avi')
               .toFormat('mp4')
               .output(outputStream)
               // setup event handlers
               .on('end', function () {
                   uploadFile(outputStream, "").then(function(){
                       resolve();
                   })
               })
               .on('error', function (err) {
                   console.log('an error happened: ' + err.message);
               });

    I would like to avoid copying the file to the local filesystem from s3, rather I would prefer to process the file in memory and upload back to s3 when finished. Would fluent-ffmpeg allow this scenario ?

  • What is the right command to convert an mp3 file to the required codec version (MPEG version 2) and bit rate (48 kbps) for Amazon Alexa SSML ?

    1er février 2019, par Asimov4

    I am trying to convert an mp3 file to the format expected by the audio tag in the Amazon Alexa SSML markup language as described here : https://developer.amazon.com/public/solutions/alexa/alexa-skills-kit/docs/speech-synthesis-markup-language-ssml-reference

    The documentation recommends using https://www.ffmpeg.org/ffmpeg.html

    I tried this command but can’t find the right codec to use :
    ffmpeg -y -i input.mp3 -ar 44100 -ab 48k -codec:a mpeg2 -ac 1 output.mp3

    I know I need to convert the file because Alexa fails with the following error : The audio is not of a supported MPEG version

  • Amazon Elastic Transcoder vs FFMPEG [closed]

    7 juillet 2017, par KiranD

    I’m developing a website (php based) and there is a provision to upload videos in different formats. I’m using HTML5 player for the front end presentation. So, as the ideal format that is supported by most of the browsers is mp4, I tried using ffmpeg and it works fine.

    I would like to know which transcoder (Amazon Elastic Transcoder or FFMPEG) would be best for handling conversions parallely when there is a huge traffic.

    There could me approximately thousands of users watching the videos and may be hundreds uploading the videos at the same time. I’m using Amazon EC2 for deployment and the traffic is mostly spiky (not flat).

    I’m not sure about the acceptable speed. But, I need the one which can transcode the videos much faster.