Recherche avancée

Médias (91)

Autres articles (62)

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

  • Les autorisations surchargées par les plugins

    27 avril 2010, par

    Mediaspip core
    autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs

  • 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

Sur d’autres sites (12012)

  • ffv1enc_vulkan : support default range coder tables

    19 janvier, par Lynne
    ffv1enc_vulkan : support default range coder tables

    This adds support for default range coder tables, rather than
    
only custom ones. Its two lines, as the same code can be used
    
for both thanks to ffv1enc.c setting f->state_transition properly.
    • [DH] libavcodec/ffv1enc_vulkan.c

  • avfilter/vf_tinterlace : support full-range YUV

    9 décembre 2022, par Niklas Haas
    avfilter/vf_tinterlace : support full-range YUV

    This filter, when used in the "pad" mode, currently makes the
    
distinction between limited and full range solely by testing for YUVJ
    
pixel formats at link setup time. This is deprecated and should be
    
improved to perform the detection based on the per-frame metadata.
    

    In order to make this distinction based on color range metadata, which
    
is only known at the time of filtering frames, for simplicity, we simply
    
allocate two copies of the "black" frame - one for limited range and the
    
other for full range metadata. This could be done more dynamically (e.g.
    
as-needed or simply by blitting the appropriate pixel value directly),
    
but this change is relatively simple and preserves the structure of the
    
existing code.
    

    This commit actually fixes a bug in FATE - the new output is correct for
    
the first time. The previous md5 ref was of a frame that incorrectly
    
combined full-range pixel data with limited-range black fields. The
    
corresponding result has been updated.
    

    Signed-off-by : Niklas Haas <git@haasn.dev>
    • [DH] libavfilter/tinterlace.h
    • [DH] libavfilter/vf_tinterlace.c
    • [DH] tests/ref/fate/filter-pixfmts-tinterlace_pad

  • avcodec/pnm : explicitly tag color range

    25 octobre 2023, par Niklas Haas
    avcodec/pnm : explicitly tag color range

    PGMYUV seems to be always limited range. This was a format originally
    
invented by FFmpeg at a time when YUVJ distinguished limited from full
    
range YUV, and this codec never appeared to output YUVJ in any
    
circumstance, so hard-coding limited range preserves the status quo.
    

    The other formats are explicitly documented to be full range RGB/gray
    
formats. That said, don't tag them yet, due to outstanding bugs w.r.t
    
grayscale formats and color range handling.
    

    This change in behavior updates a bunch of FATE tests in trivial ways
    
(added tagging being the only difference).
    • [DH] libavcodec/pnm.c
    • [DH] tests/ref/lavf/mkv
    • [DH] tests/ref/lavf/mkv_attachment
    • [DH] tests/ref/lavf/mxf
    • [DH] tests/ref/lavf/y4m
    • [DH] tests/ref/seek/lavf-mkv
    • [DH] tests/ref/seek/lavf-y4m

Navigation