Recherche avancée

Médias (1)

Mot : - Tags -/bug

Autres articles (62)

  • Websites made ​​with MediaSPIP

    2 mai 2011, par

    This page lists some websites based on MediaSPIP.

  • Creating farms of unique websites

    13 avril 2011, par

    MediaSPIP platforms can be installed as a farm, with a single "core" hosted on a dedicated server and used by multiple websites.
    This allows (among other things) : implementation costs to be shared between several different projects / individuals rapid deployment of multiple unique sites creation of groups of like-minded sites, making it possible to browse media in a more controlled and selective environment than the major "open" (...)

  • Contribute to a better visual interface

    13 avril 2011

    MediaSPIP is based on a system of themes and templates. Templates define the placement of information on the page, and can be adapted to a wide range of uses. Themes define the overall graphic appearance of the site.
    Anyone can submit a new graphic theme or template and make it available to the MediaSPIP community.

Sur d’autres sites (10268)

  • Révision 19531 : Protéger var_ajax_ancre à la reinjection dans le HTML (Boris - Avatam Studio)

    5 juin 2012, par cedric -

  • Revision e727bcf7ce : Merge "vp9_mcomp.c visual studio warnings resolved"

    14 février 2014, par Jim Bankoski

    Changed Paths :
     Modify /vp9/encoder/vp9_mcomp.c



    Merge "vp9_mcomp.c visual studio warnings resolved"

  • ffmpeg - Different number of macroblocks per each frame

    18 juin 2018, par fabridigua

    i 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 ?

Navigation