
Recherche avancée
Médias (1)
-
Somos millones 1
21 juillet 2014, par
Mis à jour : Juin 2015
Langue : français
Type : Video
Autres articles (64)
-
Amélioration de la version de base
13 septembre 2013Jolie sélection multiple
Le plugin Chosen permet d’améliorer l’ergonomie des champs de sélection multiple. Voir les deux images suivantes pour comparer.
Il suffit pour cela d’activer le plugin Chosen (Configuration générale du site > Gestion des plugins), puis de configurer le plugin (Les squelettes > Chosen) en activant l’utilisation de Chosen dans le site public et en spécifiant les éléments de formulaires à améliorer, par exemple select[multiple] pour les listes à sélection multiple (...) -
Emballe médias : à quoi cela sert ?
4 février 2011, parCe plugin vise à gérer des sites de mise en ligne de documents de tous types.
Il crée des "médias", à savoir : un "média" est un article au sens SPIP créé automatiquement lors du téléversement d’un document qu’il soit audio, vidéo, image ou textuel ; un seul document ne peut être lié à un article dit "média" ; -
Menus personnalisés
14 novembre 2010, parMediaSPIP utilise le plugin Menus pour gérer plusieurs menus configurables pour la navigation.
Cela permet de laisser aux administrateurs de canaux la possibilité de configurer finement ces menus.
Menus créés à l’initialisation du site
Par défaut trois menus sont créés automatiquement à l’initialisation du site : Le menu principal ; Identifiant : barrenav ; Ce menu s’insère en général en haut de la page après le bloc d’entête, son identifiant le rend compatible avec les squelettes basés sur Zpip ; (...)
Sur d’autres sites (3284)
-
fluent-ffmpeg generating incorrect framerate
25 novembre 2013, par ZakThompsonI'm having a strange issue converting images to a video. I am using the excellent fluent-ffmpeg module for a node.js server. I have 179 jpg images which I wish to convert to a 30fps video (should be about 6s). I have successfully done so using the following ffmpeg command :
ffmpeg -r 30 -i frame%03d.jpg -c:v libx264 out.mp4
This outputs the following when inspected by ffmpeg :
ffmpeg -i out.mp4
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'out.mp4':
Metadata:
major_brand : isom
minor_version : 512
compatible_brands: isomiso2avc1mp41
encoder : Lavf54.63.104
Duration: 00:00:06.00, start: 0.000000, bitrate: 1631 kb/s
Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuvj420p, 640x480 [SAR 1:1 DAR 4:3], 1627 kb/s, 30 fps, 30 tbr, 15360 tbn, 60 tbc
Metadata:
handler_name : VideoHandlerNow, I am attempting to do the same thing with fluent-ffmpeg :
var proc = new ffmpeg({ source: 'frame%03d.jpg', nolog: true })
.addOptions(['-c:v libx264','-r 30'])
.saveToFile('test.mp4', function(retcode, error){
console.log('file has been converted succesfully');
});Should be exactly the same, right ? But here is what I'm getting :
ffmpeg -i test.mp4
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'test.mp4':
Metadata:
major_brand : isom
minor_version : 512
compatible_brands: isomiso2avc1mp41
encoder : Lavf54.63.104
Duration: 00:00:07.20, start: 0.000000, bitrate: 1556 kb/s
Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuvj420p, 640x480 [SAR 1:1 DAR 4:3], 1553 kb/s, 30 fps, 30 tbr, 15360 tbn, 60 tbc
Metadata:
handler_name : VideoHandlerNow what's most interesting here is that although both were made from the same set of images and both supposedly have the same frame rate, the one made with fluent-ffmpeg has a duration of 7.20s, a full 1.20 longer than the first one. Upon comparing the two videos, it seems the fluent-ffmpeg one is actually at 25fps even though it reports 30.
Note that I have tried properly adding the two flags using the methods (
.withVideoCodec, .withFps
) with the same result, I merely resorted to adding the arguments manually in an attempt to make it exactly the same as my original command.If anybody here has experience with this module and/or has any suggestions, it would be greatly appreciated !
-
Revision 01a37177d1 : Refactor rd_pick_partition for parameter control This commit changes the partit
20 août 2013, par Jingning HanChanged Paths :
Modify /vp9/encoder/vp9_encodeframe.c
Modify /vp9/encoder/vp9_onyx_if.c
Refactor rd_pick_partition for parameter controlThis commit changes the partition search order of superblocks from
SPLIT, NONE, HORZ, VERT to NONE, SPLIT, HORZ, VERT for
consistency with that of sub8x8 partition search. It enable the use
of early termination in partition search for all block sizes.For ped_area_1080p 50 frames coded at 4000 kbps, it makes the runtime
goes down from 844305ms -> 818003ms (3% speed-up) at speed 0.This will further move towards making the in-search partition types
configurable, hence unifying various speed-up approaches.Some speed 1 and 2 features are turned off during the refactoring
process, including :
disable_split_var_thresh
using_small_partition_infoStricter constraints are applied to use_square_partition_only for
right/bottom boundary blocks. Will bring back/refine these features
subsequently. At this point, it makes derf set at speed 1 about
0.45% higher in compression performance, and 9% down in run-time.Change-Id : I3db9f9d1d1a0d6cbe2e50e49bd9eda1cf705f37c
-
What would be the best strategy to take a RTP stream and send it to an RTMP server ?
27 novembre 2014, par matiasinsaurraldeI’m receiving a RTP/UDP from a hardware encoder, I have tried ffmpeg, so it takes this input and outputs the stream as FLV (it’s being sent to NGINX, nginx-rtmp-module). However I’m not able to play the stream smoothly once it’s received by nginx, some frames are broken or lost, etc.
I think that my CPU is too slow for this format change (FLV) and/or ffmpeg is missing a lot of RTP packets. Any ideas ?