Recherche avancée

Médias (0)

Mot : - Tags -/serveur

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

Autres articles (34)

  • HTML5 audio and video support

    13 avril 2011, par

    MediaSPIP uses HTML5 video and audio tags to play multimedia files, taking advantage of the latest W3C innovations supported by modern browsers.
    The MediaSPIP player used has been created specifically for MediaSPIP and can be easily adapted to fit in with a specific theme.
    For older browsers the Flowplayer flash fallback is used.
    MediaSPIP allows for media playback on major mobile platforms with the above (...)

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

  • De l’upload à la vidéo finale [version standalone]

    31 janvier 2010, par

    Le chemin d’un document audio ou vidéo dans SPIPMotion est divisé en trois étapes distinctes.
    Upload et récupération d’informations de la vidéo source
    Dans un premier temps, il est nécessaire de créer un article SPIP et de lui joindre le document vidéo "source".
    Au moment où ce document est joint à l’article, deux actions supplémentaires au comportement normal sont exécutées : La récupération des informations techniques des flux audio et video du fichier ; La génération d’une vignette : extraction d’une (...)

Sur d’autres sites (3519)

  • avformat/bethsoftvid : Check image dimensions before use

    17 octobre 2020, par Michael Niedermayer
    avformat/bethsoftvid : Check image dimensions before use
    

    Fixes : signed integer overflow : 55255 * 53207 cannot be represented in type 'int'
    Fixes : 26387/clusterfuzz-testcase-minimized-ffmpeg_dem_AVS2_fuzzer-5684222226071552

    Found-by : continuous fuzzing process https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
    Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>

    • [DH] libavformat/bethsoftvid.c
  • eacmv : clear references on frame dimensions change

    28 novembre 2013, par Anton Khirnov
    eacmv : clear references on frame dimensions change
    

    Fixes invalid reads.

    Found-by : Mateusz "j00ru" Jurczyk and Gynvael Coldwind
    CC:libav-stable@libav.org

    • [DH] libavcodec/eacmv.c
  • I'm attempting to retrieve the dimensions of in-memory video buffer objects in Node.js without writing to disk

    23 mars 2021, par undefined

    All right, so I have a Node.js server where media files can be uploaded by the user. It's important for displaying the media in the client later on that I can retrieve and store the width and height dimensions of the video in advance.

    &#xA;

    For performance reasons, disk space limitations, and a few other reasons, I'm attempting to do so without saving the video buffer object (retrieved via Multer) to disk as it has terrible performance on the server I am using.

    &#xA;

    I have FFmpeg and ffprobe, as well as the nom get-video-dimensions module, but I can't find a way to get media statistics without writing the file. For example, get-video-dimensions only allows you to enter a file path.

    &#xA;

    Is there a way to either feed the buffer into one of these utilities using either a stream/pipe to simulate the source coming from disk, or is there an rpm module I've overlooked that could achieve this task ?

    &#xA;

    if (imageBufferObject.media_type == "video") {&#xA;  // Get resolution&#xA;&#xA;  // Save to disk&#xA;  let write_response = await writeFile(imageBufferObject)&#xA;  // Use utility&#xA;  let dim = await dimensions(path.join(__dirname, &#x27;tmp&#x27;, newName))&#xA;  // Delete file&#xA;  let delete_response = await deleteFile(imageBufferObject)&#xA;&#xA;&#xA;   async function writeFile(file){&#xA;     return new Promise((resolve, reject)=>{&#xA;       fs.writeFile(path.join(__dirname, &#x27;tmp&#x27;, file.newName), file.buffer, (err)=>{&#xA;         resolve(200)&#xA;        })&#xA;     })&#xA;   }&#xA;   async function deleteFile(file){&#xA;     return new Promise((resolve, reject)=>{&#xA;       fs.unlink(path.join(__dirname, &#x27;tmp&#x27;, file.newName), (err)=>{&#xA;         resolve(200)&#xA;       })&#xA;     })&#xA;   }&#xA;

    &#xA;

    I desperately want to avoid using the hard disk !

    &#xA;