
Recherche avancée
Autres articles (34)
-
HTML5 audio and video support
13 avril 2011, parMediaSPIP 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, parUnlike 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, parLe 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 Niedermayeravformat/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-5684222226071552Found-by : continuous fuzzing process https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
Signed-off-by : Michael Niedermayer <michael@niedermayer.cc> -
eacmv : clear references on frame dimensions change
28 novembre 2013, par Anton Khirnov -
I'm attempting to retrieve the dimensions of in-memory video buffer objects in Node.js without writing to disk
23 mars 2021, par undefinedAll 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.


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.


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.


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 ?


if (imageBufferObject.media_type == "video") {
 // Get resolution

 // Save to disk
 let write_response = await writeFile(imageBufferObject)
 // Use utility
 let dim = await dimensions(path.join(__dirname, 'tmp', newName))
 // Delete file
 let delete_response = await deleteFile(imageBufferObject)


 async function writeFile(file){
 return new Promise((resolve, reject)=>{
 fs.writeFile(path.join(__dirname, 'tmp', file.newName), file.buffer, (err)=>{
 resolve(200)
 })
 })
 }
 async function deleteFile(file){
 return new Promise((resolve, reject)=>{
 fs.unlink(path.join(__dirname, 'tmp', file.newName), (err)=>{
 resolve(200)
 })
 })
 }



I desperately want to avoid using the hard disk !