Recherche avancée

Médias (3)

Mot : - Tags -/pdf

Autres articles (58)

  • MediaSPIP 0.1 Beta version

    25 avril 2011, par

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

  • MediaSPIP version 0.1 Beta

    16 avril 2011, par

    MediaSPIP 0.1 beta est la première version de MediaSPIP décrétée comme "utilisable".
    Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
    Pour avoir une installation fonctionnelle, il est nécessaire d’installer manuellement l’ensemble des dépendances logicielles sur le serveur.
    Si vous souhaitez utiliser cette archive pour une installation en mode ferme, il vous faudra également procéder à d’autres modifications (...)

  • Amélioration de la version de base

    13 septembre 2013

    Jolie 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 (...)

Sur d’autres sites (8502)

  • 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

  • lavu/tx : do not unconditionally free subcontexts if initialization fails

    29 janvier 2022, par Lynne
    lavu/tx : do not unconditionally free subcontexts if initialization fails

    If a codelet initializes 2 subtransforms, and the second one fails,
    
the failure would free all subcontexts.
    
Instead, if there are subcontexts still left, don't free the array.
    
If all initializations fail, the init() function will return,
    
and reset_ctx() from the previous step will clean up all contained
    
subtransforms.
    • [DH] libavutil/tx.c

Navigation