
Recherche avancée
Médias (1)
-
Rennes Emotion Map 2010-11
19 octobre 2011, par
Mis à jour : Juillet 2013
Langue : français
Type : Texte
Autres articles (100)
-
MediaSPIP 0.1 Beta version
25 avril 2011, parMediaSPIP 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, parMultilang 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. -
Websites made with MediaSPIP
2 mai 2011, parThis page lists some websites based on MediaSPIP.
Sur d’autres sites (10225)
-
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>
-
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.


-
Revision 30147 : corrections orthographiques
24 juillet 2009, par denisb@… — Logcorrections orthographiques