Recherche avancée

Médias (1)

Mot : - Tags -/copyleft

Autres articles (96)

  • Keeping control of your media in your hands

    13 avril 2011, par

    The vocabulary used on this site and around MediaSPIP in general, aims to avoid reference to Web 2.0 and the companies that profit from media-sharing.
    While using MediaSPIP, you are invited to avoid using words like "Brand", "Cloud" and "Market".
    MediaSPIP is designed to facilitate the sharing of creative media online, while allowing authors to retain complete control of their work.
    MediaSPIP aims to be accessible to as many people as possible and development is based on expanding the (...)

  • Personnaliser en ajoutant son logo, sa bannière ou son image de fond

    5 septembre 2013, par

    Certains thèmes prennent en compte trois éléments de personnalisation : l’ajout d’un logo ; l’ajout d’une bannière l’ajout d’une image de fond ;

  • Ecrire une actualité

    21 juin 2013, par

    Pré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 ) (...)

Sur d’autres sites (7440)

  • tls : Hide backend implementation details from users

    23 mai 2017, par Diego Biurrun
    tls : Hide backend implementation details from users

    TLS is currently implemented over either OpenSSL or GnuTLS, with more
    
backends likely to appear in the future. Currently, those backend libraries
    
are part of the protocol names used during e.g. the configure stage of a
    
build. Hide those details behind a generically-named declaration for the
    
TLS protocol to avoid leaking those details into the configuration stage.
    • [DBH] configure
    • [DBH] libavformat/Makefile
    • [DBH] libavformat/network.c
    • [DBH] libavformat/protocols.c
    • [DBH] libavformat/tls.h
    • [DBH] libavformat/tls_gnutls.c
    • [DBH] libavformat/tls_openssl.c

  • avio : Allow custom IO users to get labels for the output bytestream

    4 mai 2016, par Martin Storsjö
    avio : Allow custom IO users to get labels for the output bytestream

    This allows callers with avio write callbacks to get the bytestream
    
positions that correspond to keyframes, suitable for live streaming.
    

    In the simplest form, a caller could expect that a header is written
    
to the bytestream during the avformat_write_header, and the data
    
output to the avio context during e.g. av_write_frame corresponds
    
exactly to the current packet passed in.
    

    When combined with av_interleaved_write_frame, and with muxers that
    
do buffering (most muxers that do some sort of fragmenting or
    
clustering), the mapping from input data to bytestream positions
    
is nontrivial.
    

    This allows callers to get directly information about what part
    
of the bytestream is what, without having to resort to assumptions
    
about the muxer behaviour.
    

    One keyframe/fragment/block can still be split into multiple (if
    
they are larger than the aviocontext buffer), which would call
    
the callback with e.g. AVIO_DATA_MARKER_SYNC_POINT, followed by
    
AVIO_DATA_MARKER_UNKNOWN for the second time it is called with
    
the following data.
    

    Signed-off-by : Martin Storsjö <martin@martin.st>
    • [DBH] doc/APIchanges
    • [DBH] libavformat/avio.h
    • [DBH] libavformat/aviobuf.c
    • [DBH] libavformat/mux.c
    • [DBH] libavformat/version.h

  • ffv1 : change w/h asserts to check as the condition can likely happen

    6 octobre 2012, par Michael Niedermayer

    ffv1 : change w/h asserts to check as the condition can likely happen

Navigation