Recherche avancée

Médias (0)

Mot : - Tags -/navigation

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

Autres articles (45)

  • Publier sur MédiaSpip

    13 juin 2013

    Puis-je poster des contenus à partir d’une tablette Ipad ?
    Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir

  • Ajouter notes et légendes aux images

    7 février 2011, par

    Pour pouvoir ajouter notes et légendes aux images, la première étape est d’installer le plugin "Légendes".
    Une fois le plugin activé, vous pouvez le configurer dans l’espace de configuration afin de modifier les droits de création / modification et de suppression des notes. Par défaut seuls les administrateurs du site peuvent ajouter des notes aux images.
    Modification lors de l’ajout d’un média
    Lors de l’ajout d’un média de type "image" un nouveau bouton apparait au dessus de la prévisualisation (...)

  • HTML5 audio and video support

    13 avril 2011, par

    MediaSPIP 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 (4527)

  • Revision 13930cf569 : Limit mv range to be based on partition size Previous change c4048dbd limits th

    23 août 2013, par Yaowu Xu

    Changed Paths :
     Modify /vp9/common/vp9_enums.h


     Modify /vp9/encoder/vp9_encodeframe.c



    Limit mv range to be based on partition size

    Previous change c4048dbd limits the mv search range assuming max block
    size of 64x64, this commit change the search range using actual block
    size instead.

    Change-Id : Ibe07ab02b62bf64bd9f8675d2b997af20a2c7e11

  • avformat/matroskadec : Improve invalid length error handling

    17 mai 2019, par Andreas Rheinhardt
    avformat/matroskadec : Improve invalid length error handling

    1. Up until now, the error message for EBML numbers whose length exceeds
    
the limits imposed upon them because of the element's type did not
    
distinguish between known-length and unknown-length elements. As a
    
consequence, the numerical value of the define constant
    
EBML_UNKNOWN_LENGTH was emitted as part of the error message which is
    
of course not appropriate. This commit changes this by adding error
    
messages designed for unknown-length elements.
    

    2. We impose some (arbitrary) sanity checks on the lengths of certain
    
element types ; these checks were conducted before the checks depending
    
on whether the element exceeds its containing master element. Now the
    
order has been reversed, because a failure at the (formerly) latter
    
check implies that the file is truly erroneous and not only fails our
    
arbitrary length limit. Moreover, this increases the informativeness of
    
the error messages.
    

    3. Furthermore, the error message in general has been changed by replacing
    
the type of the element (something internal to this demuxer and
    
therefore suitable as debug output at best, not as an error message
    
intended for ordinary users) with the element ID. The element's position
    
has been added, too.
    

    4. Finally, the length limit for EBML_NONE elements has been changed so
    
that all unknown-length elements of EBML_NONE-type trigger an error.
    
This is done because unknown-length elements can't be skipped and need
    
to be parsed, but there is no syntax to parse available for EBML_NONE
    
elements. This is done in preparation for a further patch which allows
    
more unknown-length elements than just clusters and segments.
    

    Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@gmail.com>
    • [DH] libavformat/matroskadec.c

  • lavu/opt : fix range check logic in set_format()

    16 décembre 2013, par Stefano Sabatini
    lavu/opt : fix range check logic in set_format()

    In particular, allow to reject undefined values. Previously the code
    
was only accepting values in the range -1 .. NB_FORMATS-1.
    • [DH] libavutil/opt.c

Navigation