Recherche avancée

Médias (3)

Mot : - Tags -/plugin

Autres articles (34)

  • 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

  • Contribute to a better visual interface

    13 avril 2011

    MediaSPIP is based on a system of themes and templates. Templates define the placement of information on the page, and can be adapted to a wide range of uses. Themes define the overall graphic appearance of the site.
    Anyone can submit a new graphic theme or template and make it available to the MediaSPIP community.

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

  • avfilter/vf_extractplanes : tag alpha plane as full range

    27 octobre 2023, par Niklas Haas
    avfilter/vf_extractplanes : tag alpha plane as full range

    Alpha planes are explicitly full range, even for limited range YUVA
    
formats. Mark them as such.
    • [DH] libavfilter/vf_extractplanes.c

  • How can I combine two audios into one, but using the length of the first audio ?

    21 avril 2021, par vaginatorZalupi

    There are two audios. I need to connect them to each other (two channels), but with the same length as the first. I found a command on Stack Overflow that partially solves my problem : ffmpeg -i AgAD3RMAAvgr.ogg -i audio.mp3 -filter_complex amix=inputs=2:duration=longest output.mp3.

    


  • AVOptions : do not range check flag options.

    26 octobre 2013, par Anton Khirnov
    AVOptions : do not range check flag options.

    It does not make sense in the vast majority of use cases, no currently
    
defined AV_OPT_TYPE_FLAGS options in Libav set the range to anything
    
nontrivial, and many of those get it wrong (the "correct" range is
    
INT_MIN to INT_MAX so that the builtin constant "all" works).
    • [DBH] libavutil/opt.c

Navigation