
Recherche avancée
Médias (1)
-
Bug de détection d’ogg
22 mars 2013, par
Mis à jour : Avril 2013
Langue : français
Type : Video
Autres articles (11)
-
Publier sur MédiaSpip
13 juin 2013Puis-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 -
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 (...)
-
Participer à sa traduction
10 avril 2011Vous pouvez nous aider à améliorer les locutions utilisées dans le logiciel ou à traduire celui-ci dans n’importe qu’elle nouvelle langue permettant sa diffusion à de nouvelles communautés linguistiques.
Pour ce faire, on utilise l’interface de traduction de SPIP où l’ensemble des modules de langue de MediaSPIP sont à disposition. ll vous suffit de vous inscrire sur la liste de discussion des traducteurs pour demander plus d’informations.
Actuellement MediaSPIP n’est disponible qu’en français et (...)
Sur d’autres sites (2949)
-
Rendering video by ffmpeg.wasm in browser occured an error
15 septembre 2022, par James BorWhen a local video renderer uses the ffmpeg.wasm library in the Chrome browser, very often an error with the SBOX_FATAL_MEMORY_EXCEEDED code occurs during the rendering process. The standard command set is used. The code below is half fake because it is very long, but describes an approximate action algorithm. Computer performance and RAM capacity do not affect the video, files used - minimal size. Has anyone experienced this and how can we solve it ?
Error screen


const videoGenerate = async (project) => {
 const ffmpeg = createFFmpeg({
 corePath: 'ffmpeg/ffmpeg-core.js',
 workerPath: 'ffmpeg/ffmpeg-core.worker.js'
 });
 await loadFfmpeg(ffmpeg);
 project.projectName = "Default";
 project.fileType = "video/mp4";

 const resultVideo = {
 title: `${project.projectName}ConcatenatedVideo.mp4`,
 };
 // *For fetchFile method and ffmpeg.FS('writeFile', title, file);
 await uploadObjects(project.projectName, ffmpeg);
 // *
 const command = ['-i', project.video, resultVideo.title];
 await ffmpeg.run(...command);
 await ffmpeg.FS("unlink", resultVideo.title);
 resultVideo["blob"] = ffmpeg.FS('readFile', title);
 return resultVideo.blob;
};



These dependencies are used : "@ffmpeg/core" : " 0.8.5", "@ffmpeg/ffmpeg" : " 0.9.7". Upgrading the library to the latest version does not work either.


-
avformat : add format_probesize to allow tuning the maximum amount of bytes to identif...
27 janvier 2014, par Michael Niedermayeravformat : add format_probesize to allow tuning the maximum amount of bytes to identify the filetype
Currently probesize is cliped at 1mb before being used for format detection.
Alternatively this cliping could be removed but this would then tie various
things like stream analysis to the file detection.Signed-off-by : Michael Niedermayer <michaelni@gmx.at>
-
Revert "avfilter/vf_idet : reduce noisyness if the filter has been auto inserted"
7 octobre 2021, par Andreas RheinhardtRevert "avfilter/vf_idet : reduce noisyness if the filter has been auto inserted"
This reverts commit 723c37d3b7b5555f23bfdfe3e5c3599543c06332.
Said commit was in preparation for auto-inserting the idet filter.
This has never happened ; even if it did, the code is wrong, because
it segfaults if the filter instance doesn't have a name (having one
is not mandatory). Furthermore, it is documented for libavfilter to
not assign any semantics to the name, which this check violates.Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@outlook.com>