
Recherche avancée
Autres articles (92)
-
MediaSPIP version 0.1 Beta
16 avril 2011, parMediaSPIP 0.1 beta est la première version de MediaSPIP décrétée comme "utilisable".
Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
Pour avoir une installation fonctionnelle, il est nécessaire d’installer manuellement l’ensemble des dépendances logicielles sur le serveur.
Si vous souhaitez utiliser cette archive pour une installation en mode ferme, il vous faudra également procéder à d’autres modifications (...) -
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 (...) -
Amélioration de la version de base
13 septembre 2013Jolie sélection multiple
Le plugin Chosen permet d’améliorer l’ergonomie des champs de sélection multiple. Voir les deux images suivantes pour comparer.
Il suffit pour cela d’activer le plugin Chosen (Configuration générale du site > Gestion des plugins), puis de configurer le plugin (Les squelettes > Chosen) en activant l’utilisation de Chosen dans le site public et en spécifiant les éléments de formulaires à améliorer, par exemple select[multiple] pour les listes à sélection multiple (...)
Sur d’autres sites (10009)
-
Amazon S3 : how to combine all images into a video ?
17 mars 2015, par scientifficI’m in my Rails app, I enable users to upload images, which get processed using ffmpeg to create a video slideshow.
I have this working locally, but am wondering how to do this when deploying the app using Heroku. In particular, I know Heroku has limited storage and has a read-only filesystem, so using Carrierwave without S3 or an external storage option doesn’t seem like an option.
But how would I run a task like the following using S3, where I combine all images into a video ?
The ffmpeg command is
ffmpeg -r 5 -i https://s3.amazonaws.com/[]/uploads/image/image_file/26/img%03d.jpg output.mp4 -y
And the AWS "folder" contains the following :
https://s3.amazonaws.com/[]/uploads/image/image_file/26/img001.jpg
https://s3.amazonaws.com/[]/uploads/image/image_file/26/img002.jpg
https://s3.amazonaws.com/[]/uploads/image/image_file/26/img003.jpgWhen I try to do the following, I get an error with ffmpeg not knowing what to do with :
https://s3.amazonaws.com/[]/uploads/image/image_file/26/img%03d.jpg
Note, this whole video compilation process works fine for me locally, so I know in theory it should work.
-
fluent-ffmpeg sometimes crashes entire amazon ec2 instance
24 octobre 2020, par Mick MarsdenI have a nodejs application where I'm using fluent-ffmpeg to convert captured video files via the html
<input file="file" />
tag to mp4 format. I'm also using ffmpeg-static to provide static binaries for fluent-ffmpeg's file path. But in order for the conversion to happen, I upload the captured video file via multer, and when that completes, multer passes the video url to fluent-ffmpeg. The code looks like this :

app.post("/upload-and-convert", async function(req, res) {

 var filepath;
 var path;

 try {

 const upload = util.promisify(uploadVideo());

 await upload(req, res);

 console.log(req.file);
 console.log("Success");
 filepath = req.file.filename;
 console.log(filepath);
 path = './public/uploads/' + filepath;
 console.log(path);

 } catch (e) {
 let response_json = {
 success: false,
 };
 res.setHeader("content-type", "application/json");
 res.send(response_json);
 }

 if(path != undefined)
 {

 console.log("Path not undefined, going to start FFMPEG");
 ffmpeg(path)
 .format('mp4')
 .size('720x720').autopad()
 .on('end', function() {
 console.log('file has been converted successfully');
 })
 .on('error', function(err) {
 console.log('an error happened: ' + err.message);
 let response_json = {
 success: false,
 };
 res.setHeader("content-type", "application/json");
 res.send(response_json);
 })
 .save('./public/uploads/video.mp4')
 .on('end', function() {
 console.log('file has been saved successfully');
 let response_json = {
 success: true,
 fileURL: 'https://websiteurl/uploads/video.mp4'
 };
 res.setHeader("content-type", "application/json");
 res.send(response_json);
 })

 } else
 {
 let response_json = {
 success: false,
 };
 res.setHeader("content-type", "application/json");
 res.send(response_json);
 }
});



Most times, the code runs fine and returns the fileURL as intended. Sometimes however, it completely crashes the amazon ec2 instance, and requires the instance be rebooted before it works again. I've checked the logs, and the server-error logs output no issues. The server-out logs when it crashes outputs the final console log before ffmpeg starts :


console.log("Path not undefined, going to start FFMPEG");



The moment it reaches the
ffmpeg(path)
, it goes down. It doesn't log any error, even though I have included error handling on the operation.

This has stumped me for days. I cannot figure out the commonality to explain why sometimes it crashes, and sometimes it does not. Note that this even happened before I started using the ffmpeg-static package. My node version is 12.19.0, and ffmpeg-static currently installs ffmpeg at version 4.3.1 if I recall correctly.


If anyone could help that would be great.


-
Install gstreamer on EC2 Amazon Linux AMI ?
6 décembre 2015, par vy32I’m trying to install QT5.5 on Amazon EC2 Linux, which apparently requires that I install some kind of multimedia support. It looks like that comes from gstreamer.
yum search gstreamer
turns up :[ec2-user@ip-172-30-1-58 ~]$ yum search gstreamer
Loaded plugins: priorities, update-motd, upgrade-helper
23 packages excluded due to repository priority protections
============================================== N/S matched: gstreamer ==============================================
gstreamer-ffmpeg.x86_64 : GStreamer FFmpeg-based plug-ins
gstreamer-ffmpeg-debuginfo.x86_64 : Debug information for package gstreamer-ffmpeg
gstreamer-plugins-bad.x86_64 : GStreamer streaming media framework "bad" plug-ins
gstreamer-plugins-bad-debuginfo.x86_64 : Debug information for package gstreamer-plugins-bad
gstreamer-plugins-bad-nonfree.x86_64 : Non Free GStreamer streaming media framework "bad" plug-ins
gstreamer-plugins-bad-nonfree-debuginfo.x86_64 : Debug information for package gstreamer-plugins-bad-nonfree
gstreamer-plugins-ugly.x86_64 : GStreamer streaming media framework "ugly" plug-ins
gstreamer-plugins-ugly-debuginfo.x86_64 : Debug information for package gstreamer-plugins-ugly
gstreamer-plugins-ugly-devel-docs.noarch : Development documentation for the GStreamer "ugly" plug-ins
gstreamer1-libav.x86_64 : GStreamer 1.0 libav-based plug-ins
gstreamer1-libav-debuginfo.x86_64 : Debug information for package gstreamer1-libav
gstreamer1-plugins-bad-freeworld.x86_64 : GStreamer 1.0 streaming media framework "bad" plug-ins
gstreamer1-plugins-bad-freeworld-debuginfo.x86_64 : Debug information for package gstreamer1-plugins-bad-freeworld
gstreamer1-plugins-ugly.x86_64 : GStreamer 1.0 streaming media framework "ugly" plug-ins
gstreamer1-plugins-ugly-debuginfo.x86_64 : Debug information for package gstreamer1-plugins-ugly
gstreamer1-plugins-ugly-devel-docs.noarch : Development documentation for the GStreamer "ugly" plug-ins
gstreamer1-vaapi.x86_64 : GStreamer plugins to use VA API video acceleration
gstreamer1-vaapi-debuginfo.x86_64 : Debug information for package gstreamer1-vaapi
gstreamer1-vaapi-devel.x86_64 : Development files for gstreamer1-vaapi
qt-gstreamer.x86_64 : C++ bindings for GStreamer with a Qt-style API
qt-gstreamer-debuginfo.x86_64 : Debug information for package qt-gstreamer
qt-gstreamer-devel.x86_64 : Header files and development documentation for qt-gstreamer
Name and summary matches only, use "search all" for everything.
[ec2-user@ip-172-30-1-58 ~]$ %However, when I try to install one of these, I get this error :
$ sudo yum install -y gstreamer-ffmpeg
Loaded plugins: priorities, update-motd, upgrade-helper
23 packages excluded due to repository priority protections
Resolving Dependencies
--> Running transaction check
---> Package gstreamer-ffmpeg.x86_64 0:0.10.13-15.el7.nux will be installed
--> Processing Dependency: liborc-0.4.so.0()(64bit) for package: gstreamer-ffmpeg-0.10.13-15.el7.nux.x86_64
--> Processing Dependency: libgstvideo-0.10.so.0()(64bit) for package: gstreamer-ffmpeg-0.10.13-15.el7.nux.x86_64
--> Processing Dependency: libgstreamer-0.10.so.0()(64bit) for package: gstreamer-ffmpeg-0.10.13-15.el7.nux.x86_64
--> Processing Dependency: libgstpbutils-0.10.so.0()(64bit) for package: gstreamer-ffmpeg-0.10.13-15.el7.nux.x86_64
--> Processing Dependency: libgstbase-0.10.so.0()(64bit) for package: gstreamer-ffmpeg-0.10.13-15.el7.nux.x86_64
--> Processing Dependency: libgstaudio-0.10.so.0()(64bit) for package: gstreamer-ffmpeg-0.10.13-15.el7.nux.x86_64
--> Finished Dependency Resolution
Error: Package: gstreamer-ffmpeg-0.10.13-15.el7.nux.x86_64 (nux-dextop)
Requires: liborc-0.4.so.0()(64bit)
Error: Package: gstreamer-ffmpeg-0.10.13-15.el7.nux.x86_64 (nux-dextop)
Requires: libgstreamer-0.10.so.0()(64bit)
Error: Package: gstreamer-ffmpeg-0.10.13-15.el7.nux.x86_64 (nux-dextop)
Requires: libgstbase-0.10.so.0()(64bit)
Error: Package: gstreamer-ffmpeg-0.10.13-15.el7.nux.x86_64 (nux-dextop)
Requires: libgstaudio-0.10.so.0()(64bit)
Error: Package: gstreamer-ffmpeg-0.10.13-15.el7.nux.x86_64 (nux-dextop)
Requires: libgstpbutils-0.10.so.0()(64bit)
Error: Package: gstreamer-ffmpeg-0.10.13-15.el7.nux.x86_64 (nux-dextop)
Requires: libgstvideo-0.10.so.0()(64bit)
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
[ec2-user@ip-172-30-1-58 ~]$Supplying the suggested
--skip-broken
doesn’t help :[ec2-user@ip-172-30-1-58 ~]$ sudo yum install -y gstreamer-ffmpeg --skip-broken
Loaded plugins: priorities, update-motd, upgrade-helper
23 packages excluded due to repository priority protections
Resolving Dependencies
--> Running transaction check
---> Package gstreamer-ffmpeg.x86_64 0:0.10.13-15.el7.nux will be installed
--> Processing Dependency: liborc-0.4.so.0()(64bit) for package: gstreamer-ffmpeg-0.10.13-15.el7.nux.x86_64
--> Processing Dependency: libgstvideo-0.10.so.0()(64bit) for package: gstreamer-ffmpeg-0.10.13-15.el7.nux.x86_64
--> Processing Dependency: libgstreamer-0.10.so.0()(64bit) for package: gstreamer-ffmpeg-0.10.13-15.el7.nux.x86_64
--> Processing Dependency: libgstpbutils-0.10.so.0()(64bit) for package: gstreamer-ffmpeg-0.10.13-15.el7.nux.x86_64
--> Processing Dependency: libgstbase-0.10.so.0()(64bit) for package: gstreamer-ffmpeg-0.10.13-15.el7.nux.x86_64
--> Processing Dependency: libgstaudio-0.10.so.0()(64bit) for package: gstreamer-ffmpeg-0.10.13-15.el7.nux.x86_64
Packages skipped because of dependency problems:
gstreamer-ffmpeg-0.10.13-15.el7.nux.x86_64 from nux-dextop
[ec2-user@ip-172-30-1-58 ~]$So how do I install
gstreamer-ffmpeg
? Why aren’t the dependencies automatically being followed ?