Recherche avancée

Médias (2)

Mot : - Tags -/media

Autres articles (98)

  • MediaSPIP 0.1 Beta version

    25 avril 2011, par

    MediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
    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 (...)

  • Multilang : améliorer l’interface pour les blocs multilingues

    18 février 2011, par

    Multilang est un plugin supplémentaire qui n’est pas activé par défaut lors de l’initialisation de MediaSPIP.
    Après son activation, une préconfiguration est mise en place automatiquement par MediaSPIP init permettant à la nouvelle fonctionnalité d’être automatiquement opérationnelle. Il n’est donc pas obligatoire de passer par une étape de configuration pour cela.

  • Supporting all media types

    13 avril 2011, par

    Unlike most software and media-sharing platforms, MediaSPIP aims to manage as many different media types as possible. The following are just a few examples from an ever-expanding list of supported formats : images : png, gif, jpg, bmp and more audio : MP3, Ogg, Wav and more video : AVI, MP4, OGV, mpg, mov, wmv and more text, code and other data : OpenOffice, Microsoft Office (Word, PowerPoint, Excel), web (html, CSS), LaTeX, Google Earth and (...)

Sur d’autres sites (13206)

  • Problems linking to FFMPEG library in Visual Studio 2010

    11 décembre 2013, par Dídac Pérez

    I have cross-compiled FFMPEG from Debian using the mingw32 toolchain. The result of the compilation is a set of .a files. When I try to use them in my project I get linker errors, concretely the following ones :

    1>RTSPCapture.obj : error LNK2019: unresolved external symbol _avformat_free_context referenced in function ...
    1>RTSPCapture.obj : error LNK2019: unresolved external symbol _avio_close referenced in function ...
    1>RTSPCapture.obj : error LNK2019: unresolved external symbol _avcodec_close referenced in function ...
    (and much more...)

    I have already included the header files like this :

    extern "C"
    {
       #include <libavcodec></libavcodec>avcodec.h>
       #include <libavformat></libavformat>avformat.h>
       #include <libavformat></libavformat>avio.h>
    }

    And I use the .a files like this :

    #pragma comment(lib, "libavcodec.a")
    #pragma comment(lib, "libavformat.a")
    #pragma comment(lib, "libavutil.a")

    May I know why I am still getting linker errors ? Best regards,

    EDIT : I have realized that this is not possible. So, what should I do to use FFMPEG library in my MSVC2010 project taking into account that I can't compile ffmpeg in Windows ? it seems to be REALLY difficult...

  • 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 ?

  • bfi : Add some very basic sanity checks for input packet sizes

    28 septembre 2013, par Martin Storsjö
    bfi : Add some very basic sanity checks for input packet sizes
    

    CC : libav-stable@libav.org
    Signed-off-by : Martin Storsjö <martin@martin.st>

    • [DH] libavformat/bfi.c