
Recherche avancée
Autres articles (111)
-
Script d’installation automatique de MediaSPIP
25 avril 2011, parAfin de palier aux difficultés d’installation dues principalement aux dépendances logicielles coté serveur, un script d’installation "tout en un" en bash a été créé afin de faciliter cette étape sur un serveur doté d’une distribution Linux compatible.
Vous devez bénéficier d’un accès SSH à votre serveur et d’un compte "root" afin de l’utiliser, ce qui permettra d’installer les dépendances. Contactez votre hébergeur si vous ne disposez pas de cela.
La documentation de l’utilisation du script d’installation (...) -
Que fait exactement ce script ?
18 janvier 2011, parCe script est écrit en bash. Il est donc facilement utilisable sur n’importe quel serveur.
Il n’est compatible qu’avec une liste de distributions précises (voir Liste des distributions compatibles).
Installation de dépendances de MediaSPIP
Son rôle principal est d’installer l’ensemble des dépendances logicielles nécessaires coté serveur à savoir :
Les outils de base pour pouvoir installer le reste des dépendances Les outils de développements : build-essential (via APT depuis les dépôts officiels) ; (...) -
Automated installation script of MediaSPIP
25 avril 2011, parTo overcome the difficulties mainly due to the installation of server side software dependencies, an "all-in-one" installation script written in bash was created to facilitate this step on a server with a compatible Linux distribution.
You must have access to your server via SSH and a root account to use it, which will install the dependencies. Contact your provider if you do not have that.
The documentation of the use of this installation script is available here.
The code of this (...)
Sur d’autres sites (9055)
-
Converting a H.264-Stream with node.js using fluent-ffmpeg
10 novembre 2014, par Andreas LacknerI want to convert a H.264 stream (provided by a foscam via RTSP) into a ogg-stream (via HTTP) using node.js and ffmpeg.
So far I tried it with VLC, wich works fine. But VLC needs too much CPU power.I’ve tried the following :
var ffmpeg = require('fluent-ffmpeg');
var http = require('http');
http.createServer(function (req, res) {
var command = ffmpeg();
command.input('rtsp://user:password@foscam.example.com:88/videoMain');
command.inputFormat('rtsp');
command.videoCodec('libtheora');
command.audioCodec('libvorbis');
command.toFormat('ogg');
console.log('New Request');
res.writeHead('200', {
'Content-Type' : 'video/ogg',
'Connection' : 'keep-alive',
"Accept-Ranges" : "bytes"
});
command.on('error', function(err, stdout, stderr) {
console.log("error:"+err);
console.log('ffmpeg stdout: ' + stdout);
console.log('ffmpeg stderr: ' + stderr);
});
command.output(res);
}).listen(8080, 'localhost');If I try to open the stream with VLC, I don’t get any response.
Does anybody know what’s wrong ? -
Thread count option in FFmpeg for FASTEST conversion to h264 ?
9 février, par S BI need to maximize speed while converting videos using FFmpeg to h264



- 

- Any input format of source videos
- User's machine can have any number of cores
- Power and memory consumption are non-issues









Of course, there are a whole bunch of options that can be tweaked but this question is particularly about choosing the best
-thread <count></count>
option. I am trying to find an ideal thread count as a function of


- 

- no. of cores
- input video format
- h264-friendly values maybe ?
- anything else missed above ?











I am aware the default
-thread 0
follows one-thread-per-core approach which is supposed to be optimal. But I am not sure if this is time or space-optimized. Also, on certain testcases, I've seen more threads (say 4 threads on my dual core test machine) finishes quicker than the default.


Any other direction, say configure options w.r.t. threads, worth pursuing ?


-
Thread count option in FFmpeg for FASTEST conversion to h264 ?
5 septembre 2013, par Saptarshi BiswasI need to maximize speed while converting videos using FFmpeg to h264
- Any input format of source videos
- User's machine can have any number of cores
- Power and memory consumption are non-issues
Of course, there are a whole bunch of options that can be tweaked but this question is particularly about choosing the best
-thread <count></count>
option. I am trying to find an ideal thread count as a function of- no. of cores
- input video format
- h264-friendly values maybe ?
- anything else missed above ?
I am aware the default
-thread 0
follows one-thread-per-core approach which is supposed to be optimal. But I am not sure if this is time or space-optimized. Also, on certain testcases, I've seen more threads (say 4 threads on my dual core test machine) finishes quicker than the default.Any other direction, say configure options w.r.t. threads, worth pursuing ?