
Recherche avancée
Autres articles (53)
-
Ecrire une actualité
21 juin 2013, parPrésentez les changements dans votre MédiaSPIP ou les actualités de vos projets sur votre MédiaSPIP grâce à la rubrique actualités.
Dans le thème par défaut spipeo de MédiaSPIP, les actualités sont affichées en bas de la page principale sous les éditoriaux.
Vous pouvez personnaliser le formulaire de création d’une actualité.
Formulaire de création d’une actualité Dans le cas d’un document de type actualité, les champs proposés par défaut sont : Date de publication ( personnaliser la date de publication ) (...) -
MediaSPIP 0.1 Beta version
25 avril 2011, parMediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
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 (...) -
Submit bugs and patches
13 avril 2011Unfortunately a software is never perfect.
If you think you have found a bug, report it using our ticket system. Please to help us to fix it by providing the following information : the browser you are using, including the exact version as precise an explanation as possible of the problem if possible, the steps taken resulting in the problem a link to the site / page in question
If you think you have solved the bug, fill in a ticket and attach to it a corrective patch.
You may also (...)
Sur d’autres sites (3763)
-
Changelog : fix project name
12 mars 2013, par Michael NiedermayerChangelog : fix project name
-
How to implement FFMPEG to android studio project [on hold]
3 octobre 2016, par LightHow to Implements FFMPEG to android studio project
help please
-
ffmpeg - Different number of macroblocks per each frame
18 juin 2018, par fabridiguai am studying the MPEG compression, in particular how are "labeled" the macroblocks with ffmpeg, using the command :
ffmpeg -debug mb_type -i input.mp4 out.mp4
From theory, i know that typically a macroblock is a 16x16 (pixels) block.
So if a frame is e.g. 1920x1080 i suppose that the macroblocks are
(1920*1080)/(16*16) = 8100
Now, analysing the ffmpeg report, I’ve seen that for each frame there are many many less macroblocks (labelled with some "characters" indicating their type).
Can you explain me why this happens ?
Is a (mine) theory error ?I’ve seen that "visualizing" macroblocks with -debug vis_mb_type there some gray blocks.. corresponding to the (macro)blocks not satisfying any criteria ffmpeg is looking for.. maybe in my example for each frame there are
8100 - #"gray" macroblocks
Is this possible ? And why ?