
Recherche avancée
Médias (1)
-
SPIP - plugins - embed code - Exemple
2 septembre 2013, par
Mis à jour : Septembre 2013
Langue : français
Type : Image
Autres articles (39)
-
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 -
MediaSPIP v0.2
21 juin 2013, parMediaSPIP 0.2 is the first MediaSPIP stable release.
Its official release date is June 21, 2013 and is announced here.
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 (...) -
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 (4350)
-
Roadmap #3581 : Nettoyer les fonctions désuettes de ecrire/inc/presentation.php
26 février 2016, par b bJ’ajoute cadre_depliable() à la liste des fonctions à remiser au grenier.
Je n’ai trouvé aucune occurrence des fonctions listées dans les plugins-dist, ça semble clean de côté.
Par contre, cela implique virer d’autres vieilleries comme celle-ci qui est dépréciée :
https://core.spip.net/projects/spip/repository/entry/spip/ecrire/exec/fond_monobloc.php
Et de passer en squelettes certaines pages présentes dans :
https://core.spip.net/projects/spip/repository/show/spip/ecrire/exec
-
node-fluent-ffmpeg Multiple images to video
16 août 2015, par tsurantinoI am trying to stitch multiple .PNG images to a single .MP4 video using Node. I am using
ffmpeg
and specifically, thenode-fluent-ffmpeg
library.I can only get one frame to show up at a time, when I instead intend to show 100+.
var video = ffmpeg();
for (var i = 1; i <= 168; i++) {
//console.log('Adding: ' + path.join(__dirname, 'public', 'tmp', 'frame-' + i.toString() + '.png'));
video.input(path.join(__dirname, 'public', 'tmp', 'frame-' + i.toString() + '.png')).loop(1);
}
video.save(path.join(__dirname, 'public', 'videos', 'test.mp4'))
.on('end', function() {
console.log('file has been converted succesfully');
res.redirect('/');
})
.on('error', function(err) {
console.log('an error happened: ' + err.message);
}) -
ffmpeg outputs that the first frame of a 25fps video shows for only 1ms
13 avril 2019, par ChubaccaI’m using ffmpeg to split up a video by frames. For a video that is 25fps, my expectation would be that it would show frame 0 for 40ms, and then it would show frame 1 for 40ms, etc. However, when I use ffmepg to analyze the video, this is not what I get.
I pulled frames out of the video using the following commands :
ffmpeg -i original.mp4 -ss 00:00:00.000 -vframes 1 0.000.png
ffmpeg -i original.mp4 -ss 00:00:00.001 -vframes 1 0.001.png
ffmpeg -i original.mp4 -ss 00:00:00.040 -vframes 1 0.040.png
ffmpeg -i original.mp4 -ss 00:00:00.041 -vframes 1 0.041.pngIn this, I would expect
0.000.png
and0.001.png
to be the same frame, but the resulting pngs are different. However, on the flipside,0.001.png
and0.040.png
ARE the same frame, while0.040.png
and0.041.png
are different frames. It seems as though the frame at0.000.png
is only showing for 1ms. I’ve tested this on multiple different videos, with consistent results. Can anybody explain why this is or why my expectations are potentially incorrect ?As a side note, when I load the same video into an HTML5 video tag in the browsers, when I play the video the first frame shows for 64 milliseconds, and all other frames show for 40 milliseconds. I can test this by comparing frames for the following commands :
player.currentTime = 0
player.currentTime = .063 // same frame as 0
player.currentTime = .064 // different frame than .063
player.currentTime = .103 // same frame as .064
player.currentTime = .104 // different frame than .103This also defies expectations, and makes matching up frames/times for the video between ffmpeg and html5 video even more annoying. Does anyone know what’s going on here ?
If it’s helpful, here is the metadata from the video :
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'original.mp4':
Metadata:
major_brand : isom
minor_version : 512
compatible_brands: isomiso2avc1mp41
encoder : Lavf58.17.101
Duration: 01:36:16.20, start: 0.000000, bitrate: 2301 kb/s
Stream #0:0(und): Video: h264 (Constrained Baseline) (avc1 / 0x31637661), yuv420p, 1280x720 [SAR 1:1 DAR 16:9], 2200 kb/s, 25 fps, 25 tbr, 12800 tbn, 50 tbc (default)
Metadata:
handler_name : VideoHandler
Stream #0:1(und): Audio: aac (LC) (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 96 kb/s (default)
Metadata:
handler_name : SoundHandler