
Recherche avancée
Médias (1)
-
Spitfire Parade - Crisis
15 mai 2011, par
Mis à jour : Septembre 2011
Langue : English
Type : Audio
Autres articles (44)
-
Publier sur MédiaSpip
13 juin 2013Puis-je poster des contenus à partir d’une tablette Ipad ?
Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir -
De l’upload à la vidéo finale [version standalone]
31 janvier 2010, parLe chemin d’un document audio ou vidéo dans SPIPMotion est divisé en trois étapes distinctes.
Upload et récupération d’informations de la vidéo source
Dans un premier temps, il est nécessaire de créer un article SPIP et de lui joindre le document vidéo "source".
Au moment où ce document est joint à l’article, deux actions supplémentaires au comportement normal sont exécutées : La récupération des informations techniques des flux audio et video du fichier ; La génération d’une vignette : extraction d’une (...) -
HTML5 audio and video support
13 avril 2011, parMediaSPIP uses HTML5 video and audio tags to play multimedia files, taking advantage of the latest W3C innovations supported by modern browsers.
The MediaSPIP player used has been created specifically for MediaSPIP and can be easily adapted to fit in with a specific theme.
For older browsers the Flowplayer flash fallback is used.
MediaSPIP allows for media playback on major mobile platforms with the above (...)
Sur d’autres sites (5931)
-
Merge remote-tracking branch ’cehoyos/master’
7 mai 2015, par Michael NiedermayerMerge remote-tracking branch ’cehoyos/master’
* cehoyos/master :
lavf/img2dec : Autodetect qdraw images.
lavc/qdrw : Also support real-world qdraw images.Merged-by : Michael Niedermayer <michaelni@gmx.at>
-
mdct15 : add inverse transform postrotation SIMD
29 juillet 2017, par Rostislav Pehlivanovmdct15 : add inverse transform postrotation SIMD
2.5ms frames :
Before (c) : 2638 decicycles in postrotate, 2097040 runs, 112 skips
After (sse3) : 1467 decicycles in postrotate, 2097083 runs, 69 skips
After (avx2) : 1244 decicycles in postrotate, 2097085 runs, 67 skips5ms frames :
Before (c) : 4987 decicycles in postrotate, 1048371 runs, 205 skips
After (sse3) : 2644 decicycles in postrotate, 1048509 runs, 67 skips
After (avx2) : 2031 decicycles in postrotate, 1048523 runs, 53 skips10ms frames :
Before (c) : 9153 decicycles in postrotate, 523575 runs, 713 skips
After (sse3) : 5110 decicycles in postrotate, 523726 runs, 562 skips
After (avx2) : 3738 decicycles in postrotate, 524223 runs, 65 skips20ms frames :
Before (c) : 17857 decicycles in postrotate, 261866 runs, 278 skips
After (sse3) : 10041 decicycles in postrotate, 261746 runs, 398 skips
After (avx2) : 7050 decicycles in postrotate, 262116 runs, 28 skipsImproves total decoding performance for real world content by 9% with avx2.
Signed-off-by : Rostislav Pehlivanov <atomnuker@gmail.com>
-
Ffmpeg set duration using node-fluent-ffmpeg
23 mai 2013, par VprnlI'm really new to the world of ffmpeg so please excuses me if this is a stupid queston.
I'm using the module Node-fluent-ffmpeg to stream a movie and convert it from avi to webm.
So far so good (it plays the video), but I'm having trouble parsing the duration to the player. My ultimate goal is to be able to skip ahead in the movie. But first the player needs to know how long the video is.my code is as followed :
var stat = fs.statSync(movie);
var start = 0;
var end = 0;
var range = req.header('Range');
if (range != null) {
start = parseInt(range.slice(range.indexOf('bytes=')+6,
range.indexOf('-')));
end = parseInt(range.slice(range.indexOf('-')+1,
range.length));
}
if (isNaN(end) || end == 0) end = stat.size-1;
if (start > end) return;
res.writeHead(206, { // NOTE: a partial http response
'Connection':'close',
'Content-Type':'video/webm',
'Content-Length':end - start,
'Content-Range':'bytes '+start+'-'+end+'/'+stat.size,
'Transfer-Encoding':'chunked'
});
var proc = new ffmpeg({ source: movie, nolog: true, priority: 1, timeout:15000})
.toFormat('webm')
.withVideoBitrate('1024k')
.addOptions(['-probesize 900000', '-analyzeduration 0', '-bufsize 14000'])
.writeToStream(res, function(retcode, error){
if (!error){
console.log('file has been converted succesfully',retcode);
}else{
console.log('file conversion error',error);
}
});I tried to set the header with a start and a end based on this article : http://delog.wordpress.com/2011/04/25/stream-webm-file-to-chrome-using-node-js/
I also looked in the FFmpeg documentation and found -f duration and -ss.
But I don't quite know how to convert the byte range to seconds.I feel like I'm pretty close to a solution but my inexperience with the subject matter prohibits me from getting it to work. If I'm unclear in any way please let me know. (I have a tendency of explaining things fuzzy.)
Thanks in advance !