
Recherche avancée
Médias (1)
-
1 000 000 (wav version)
26 septembre 2011, par
Mis à jour : Avril 2013
Langue : English
Type : Audio
Autres articles (58)
-
Contribute to translation
13 avril 2011You can help us to improve the language used in the software interface to make MediaSPIP more accessible and user-friendly. You can also translate the interface into any language that allows it to spread to new linguistic communities.
To do this, we use the translation interface of SPIP where the all the language modules of MediaSPIP are available. Just subscribe to the mailing list and request further informantion on translation.
MediaSPIP is currently available in French and English (...) -
Des sites réalisés avec MediaSPIP
2 mai 2011, parCette page présente quelques-uns des sites fonctionnant sous MediaSPIP.
Vous pouvez bien entendu ajouter le votre grâce au formulaire en bas de page. -
Les autorisations surchargées par les plugins
27 avril 2010, parMediaspip core
autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs
Sur d’autres sites (9816)
-
lavu : remove comma at final enumeration items to fix pedantic warnings
20 octobre 2016, par Michael Behrisch -
Version 1.3.1 final.
27 novembre 2014, par Erik de Castro LopoVersion 1.3.1 final.
- [DH] README
- [DH] build/config.mk
- [DH] configure.ac
- [DH] doc/Doxyfile.in
- [DH] doc/html/documentation_bugs.html
- [DH] doc/html/index.html
- [DH] src/libFLAC/libFLAC_dynamic.vcproj
- [DH] src/libFLAC/libFLAC_dynamic.vcxproj
- [DH] src/libFLAC/libFLAC_static.vcproj
- [DH] src/libFLAC/libFLAC_static.vcxproj
- [DH] test/metaflac-test-files/case07-expect.meta
-
How can I get the final size after transcripting a video to stream it with fluent-ffmpeg ?
5 avril 2018, par G. ManukyanI am trying to stream a video using
createReadStream
and usingpipe(res)
in node.js and it works fine if the file doesn’t need transcoding (mp4, webm).With mkv files I am using fluent-ffmpeg to transcode it on the fly, but the problem is that I can’t go back and forward in the html video player.
download = function(file, req, res) {
const range = req.headers.range
const parts = range.replace(/bytes=/, "").split("-")
const start = parseInt(parts[0], 10);
const end = parts[1] ? parseInt(parts[1], 10) : file.length - 1
res.setHeader('Content-Type', 'video/webm')
res.setHeader('Accept-Ranges', 'bytes');
res.setHeader('Content-Length', 1 + end - start);
res.setHeader('Content-Range', `bytes ${start}-${end}/${file.length}`);
res.statusCode = 206;
var stream = file.createReadStream({start, end})
ffmpeg(stream)
.videoCodec('libvpx')
.audioCodec('libvorbis')
.videoBitrate('512k')
.format('webm')
.on('start', () => {
console.log('transcoding...')
})
.on('error', (err, stdout, stderr) => {
console.log(err.message, err, stderr);
})
.on('progress', function(progress) {
console.log(progress);
})
.on('end', function(filenames) {
console.log("Finished transcoding.");
})
.pipe(res);
}I think that comes from the fact that we don’t know in advance the size of the final transcoded file so the range we send in the headers is wrong and somehow make the video player "limited".
What can be a workaround to this problem ?