
Recherche avancée
Autres articles (96)
-
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 (...) -
ANNEXE : Les plugins utilisés spécifiquement pour la ferme
5 mars 2010, parLe site central/maître de la ferme a besoin d’utiliser plusieurs plugins supplémentaires vis à vis des canaux pour son bon fonctionnement. le plugin Gestion de la mutualisation ; le plugin inscription3 pour gérer les inscriptions et les demandes de création d’instance de mutualisation dès l’inscription des utilisateurs ; le plugin verifier qui fournit une API de vérification des champs (utilisé par inscription3) ; le plugin champs extras v2 nécessité par inscription3 (...)
-
Installation en mode standalone
4 février 2011, parL’installation de la distribution MediaSPIP se fait en plusieurs étapes : la récupération des fichiers nécessaires. À ce moment là deux méthodes sont possibles : en installant l’archive ZIP contenant l’ensemble de la distribution ; via SVN en récupérant les sources de chaque modules séparément ; la préconfiguration ; l’installation définitive ;
[mediaspip_zip]Installation de l’archive ZIP de MediaSPIP
Ce mode d’installation est la méthode la plus simple afin d’installer l’ensemble de la distribution (...)
Sur d’autres sites (5161)
-
Video conversion with ffmpeg to target Android and iOS mobile devices
17 novembre 2017, par Lee BrindleyI’m building a react native app for both Android and IOS, the back-end API is written with NodeJS.
Users may upload video from their phones, once uploaded the user and their friends will be able to view the video - so the videos need to be stored in a format which is playable on both Android & IOS.
My question relates to the conversion of video, uploaded by the user. I developed a similar app a couple of years ago ; I used the repo node-fluent-ffmpeg which provides a nice API to interact with FFmpeg.
In the previous project (which was a web app), I converted the uploaded videos into two files, one .mp4 and one .webm - if a user uploaded an mp4, then I would skip the mp4 step, likewise if they uploaded a .webm.
This was kind of slow. Now I’ve come across the same requirement years later, after some research I think I was wrong to convert the videos to the last project.
I’ve read that I can simply use FFmpeg to change the container format of the videos, which is a much faster process than converting them from scratch.
The video conversion code I used last time went something along the lines of :
var convertVideo = function (source, format, output, success, failure, progress) {
var converter = ffmpeg(source);
var audioCodec = "libvorbis";
if (format.indexOf("mp4") != -1) {
audioCodec = "aac";
}
converter.format(format)
.withVideoBitrate(1024)
.withAudioCodec(audioCodec)
.on('end', success)
.on('progress', progress)
.on('error', failure);
converter.save(output);
};Usage :
Convert to mp4 :
convertVideo("PATH_TO_VIDEO", "mp4", "foo.mp4", () => {console.log("success");});
Convert to webm :
convertVideo("PATH_TO_VIDEO", "webm", "foo.webm", () => {console.log("success");});
Can anyone point out a code smell here regarding the performance of this operation ? Is this code doing a lot more than it should achieve cross-platform compatibility between IOS and Android ?
Might be worth mentioning that support for older OS versions is not such a big deal in this project.
-
Video Conversion ? with ffmpeg
10 août 2017, par Lee BrindleyI’m building a react native app for both Android and IOS, the back-end API is written with NodeJS.
Users may upload video from their phones, once uploaded the user and their friends will be able to view the video - so the videos need to be stored in a format which is playable on both Android & IOS.
My question relates to the conversion of video, uploaded by the user. I have developed a similar app a couple of years ago, I used the repo node-fluent-ffmpeg which provides a nice API to interact with ffmpeg.
In the previous project (which was a web app), I converted the uploaded videos into two files, one .mp4 and one .webm - if a user uploaded a mp4, then I would skip the mp4 step, likewise if they uploaded a .webm.
This was kind of slow. Now i’ve come across the same requirement years later, after some research I think I was wrong to convert the videos in the last project.
I’ve read that I can simply use ffmpeg to change the container format of the videos, which is a much faster process than converting them from scratch.
The video conversion code I used last time went something along the lines of :
var convertVideo = function (source, format, output, success, failure, progress) {
var converter = ffmpeg(source);
var audioCodec = "libvorbis";
if (format.indexOf("mp4") != -1) {
audioCodec = "aac";
}
converter.format(format)
.withVideoBitrate(1024)
.withAudioCodec(audioCodec)
.on('end', success)
.on('progress', progress)
.on('error', failure);
converter.save(output);
};Usage :
Convert to mp4 :
convertVideo("PATH_TO_VIDEO", "mp4", "foo.mp4", () => {console.log("success");});
Convert to webm :
convertVideo("PATH_TO_VIDEO", "webm", "foo.webm", () => {console.log("success");});
Can anyone point out a code smell here regarding performance of this operation ? Is this code doing a lot more than it should to achieve cross platform compatibility between IOS and Android ?
Might be worth mentioning that support for older OS versions is not such a big deal in this project.
-
ffmpeg-php module fails in linux
26 juillet 2017, par SwatiI’ve been trying this for a couple of days now. I am trying to install ffmpeg-php on my CentOS server.
OS : CentOS 6
PHP : 5.5
ffmpeg : 1.2.1
ffmpeg-php : 0.6.0
The ffmpeg installation went on without a hitch and I am able to convert files back and forth via the CLI.While installing ffmpeg-php, I encountered errors while making (after configuring) due to time.h references which was corrected by renaming the files creating with an extension .loT to .lo (as rightly pointed out here)
Once this was done, the make process went on smoothly and the make install went through without a hitch. However, after specifying the extension=ffmpeg.so in the php.ini file and after restarting Apache, the module doesn’t load or show up in phpinfo().
The Apache error log shows only "PHP Warning : PHP Startup : Invalid library (maybe not a PHP library) ’ffmpeg.so’ in Unknown on line 0" and nothing else.
make test also shows the same error and FAILS the associated tests. I’ve checked here which wasn’t very helpful. Also, I read somewhere that it may be the issue with permissions but the permissions for the ffmpeg.so file is 755.
Any help is appreciated.
Thanks in advance.