Recherche avancée

Médias (0)

Mot : - Tags -/serveur

Aucun média correspondant à vos critères n’est disponible sur le site.

Autres articles (65)

  • 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" (...)

  • Submit enhancements and plugins

    13 avril 2011

    If you have developed a new extension to add one or more useful features to MediaSPIP, let us know and its integration into the core MedisSPIP functionality will be considered.
    You can use the development discussion list to request for help with creating a plugin. As MediaSPIP is based on SPIP - or you can use the SPIP discussion list SPIP-Zone.

Sur d’autres sites (5932)

  • movenc : Set tfhd default sample flags based on actual samples, if possible

    6 mars 2015, par Martin Storsjö
    movenc : Set tfhd default sample flags based on actual samples, if possible
    

    This avoids assuming that e.g. audio samples are marked as
    sync samples.

    This allows omitting the sample flags from trun, if the default
    flags happen to be right for all the samples.

    Signed-off-by : Martin Storsjö <martin@martin.st>

    • [DH] libavformat/movenc.c
  • libavcodec/libx264 : fix reference frame computation based on level

    16 avril 2020, par Josh Brewster
    libavcodec/libx264 : fix reference frame computation based on level
    

    The current implementation allows passing levels to libavcodec as
    integers (such as "31" instead of "3.1").

    However, in this case, the maximum reference frame value per level was
    ignored because libavcodec converted the string to 310 instead of 31.

    Since libx264 has correctly parsed the level to int
    (x4->params.i_level_idc), we should rely on this value instead of
    attempting to parse the level string on our own.

    Signed-off-by : Josh Brewster <josh.brewster@protonmail.com>
    Signed-off-by : Josh de Kock <josh@itanimul.li>

    • [DH] libavcodec/libx264.c
  • Revision be3b08da3e : [svc] Temporal svc with two pass rate control It's built based on current spati

    2 septembre 2014, par Minghai Shang

    Changed Paths :
     Modify /examples/vp9_spatial_svc_encoder.c


     Modify /test/svc_test.cc


     Modify /vp9/encoder/vp9_bitstream.c


     Modify /vp9/encoder/vp9_bitstream.h


     Modify /vp9/encoder/vp9_encoder.c


     Modify /vp9/encoder/vp9_encoder.h


     Modify /vp9/encoder/vp9_firstpass.c


     Modify /vp9/encoder/vp9_ratectrl.c


     Modify /vp9/encoder/vp9_svc_layercontext.c


     Modify /vp9/encoder/vp9_svc_layercontext.h


     Modify /vp9/encoder/vp9_temporal_filter.c


     Modify /vp9/vp9_cx_iface.c


     Modify /vpx/src/svc_encodeframe.c


     Modify /vpx/svc_context.h



    [svc] Temporal svc with two pass rate control

    It’s built based on current spatial svc code.
    We only support one spatial two temporal layers at this time.
    Change-Id : I1fdc8584354b910331e626bfae60473b3b701ba1