
Recherche avancée
Autres articles (38)
-
Keeping control of your media in your hands
13 avril 2011, parThe vocabulary used on this site and around MediaSPIP in general, aims to avoid reference to Web 2.0 and the companies that profit from media-sharing.
While using MediaSPIP, you are invited to avoid using words like "Brand", "Cloud" and "Market".
MediaSPIP is designed to facilitate the sharing of creative media online, while allowing authors to retain complete control of their work.
MediaSPIP aims to be accessible to as many people as possible and development is based on expanding the (...) -
Le plugin : Podcasts.
14 juillet 2010, parLe problème du podcasting est à nouveau un problème révélateur de la normalisation des transports de données sur Internet.
Deux formats intéressants existent : Celui développé par Apple, très axé sur l’utilisation d’iTunes dont la SPEC est ici ; Le format "Media RSS Module" qui est plus "libre" notamment soutenu par Yahoo et le logiciel Miro ;
Types de fichiers supportés dans les flux
Le format d’Apple n’autorise que les formats suivants dans ses flux : .mp3 audio/mpeg .m4a audio/x-m4a .mp4 (...) -
Les images
15 mai 2013
Sur d’autres sites (4219)
-
Prendre en compte smush (scripts init)
28 avril 2013Il faudrait installer les binaires nécessaires au plugin smush :
- ImageMagick ;
- optipng ;
- pngnq ;
- gifscycle ;
- libjpeg-progs ;
Il faut aussi ajouter le checkout du plugin.
-
svn co svn ://zone.spip.org/spip-zone/_plugins_/smush_images/trunk plugins/smush
-
using node-fluent-ffmpeg to transcode with ffmpeg on windows not working
25 juillet 2015, par jansmolders86I’m trying to use the module node-fluent-ffmpeg (https://github.com/schaermu/node-fluent-ffmpeg) to transcode and stream a videofile. Since I’m on a Windows machine, I first downloaded FFMpeg from the official site (http://ffmpeg.zeranoe.com/builds/). Then I extracted the files in the folder C :/FFmpeg and added the path to the system path (to the bin folder to be precise). I checked if FFmpeg worked by typing in the command prompt : ffmpeg -version. And it gave a successful response.
After that I went ahead and copied/altered the following code from the module (https://github.com/schaermu/node-fluent-ffmpeg/blob/master/examples/express-stream.js) :
app.get('/video/:filename', function(req, res) {
res.contentType('avi');
console.log('Setting up stream')
var stream = 'c:/temp/' + req.params.filename
var proc = new ffmpeg({ source: configfileResults.moviepath + req.params.filename, nolog: true, timeout: 120, })
.usingPreset('divx')
.withAspect('4:3')
.withSize('640x480')
.writeToStream(res, function(retcode, error){
if (!error){
console.log('file has been converted succesfully',retcode);
}else{
console.log('file conversion error',error);
}
});
});I’ve properly setup the client with flowplayer and tried to get it running but
nothing happens. I checked the console and it said :file conversion error timeout
After that I increased the timeout but somehow, It only starts when I reload the page. But of course immediately stops because of the page reload. Do I need to make a separate node server just for the transcoding of files ? Or is there some sort of event I need to trigger ?
I’m probably missing something simple but I can’t seem to get it to work.
Hopefully someone can point out what I’ve missed.Thanks
-
What is wrong with this code ? Not working on Windows 10 / Ubuntu 14
3 avril 2017, par SomenameTrying to convert a
.gif
to.mp4
:var express = require('express');
var bodyParser = require('body-parser');
var app = express();
var ffmpeg = require('fluent-ffmpeg');
var proc = new ffmpeg({ source: 'myfile.gif' })
.withAspect('4:3')
.withSize('640x480')
.applyAutopadding(true, 'white')
.saveToFile('myfile.avi', function(stdout, stderr) {
console.log('file has been converted succesfully');
});
app.listen(3000, function() {
console.log("Server Running on 3000");
});Getting the same error on Windows 10 and Ubuntu 14 :
Error: Cannot find ffmpeg
.What is wrong with the code ? Please help.