Recherche avancée

Médias (1)

Mot : - Tags -/censure

Autres articles (98)

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

  • Multilang : améliorer l’interface pour les blocs multilingues

    18 février 2011, par

    Multilang est un plugin supplémentaire qui n’est pas activé par défaut lors de l’initialisation de MediaSPIP.
    Après son activation, une préconfiguration est mise en place automatiquement par MediaSPIP init permettant à la nouvelle fonctionnalité d’être automatiquement opérationnelle. Il n’est donc pas obligatoire de passer par une étape de configuration pour cela.

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

  • avcodec/h264dec : apply H.274 film grain

    17 août 2021, par Niklas Haas
    avcodec/h264dec : apply H.274 film grain

    Because we need access to ref frames without film grain applied, we have
    
to add an extra AVFrame to H264Picture to avoid messing with the
    
original. This requires some amount of overhead to make the reference
    
moves work out, but it allows us to benefit from frame multithreading
    
for film grain application "for free".
    

    Unfortunately, this approach requires twice as much RAM to be constantly
    
allocated for ref frames, due to the need for an extra buffer per
    
H264Picture. In theory, we could get away with freeing up this memory as
    
soon as it's no longer needed (since ref frames do not need film grain
    
buffers any longer), but trying to call ff_thread_release_buffer() from
    
output_frame() conflicts with possible later accesses to that same frame
    
and I'm not sure how to synchronize that well.
    

    Tested on all three cases of (no fg), (fg present but exported) and (fg
    
present and not exported), with and without threading.
    

    Co-authored-by : James Almer <jamrial@gmail.com>
    
Signed-off-by : Niklas Haas <git@haasn.dev>
    
Signed-off-by : James Almer <jamrial@gmail.com>
    • [DH] libavcodec/h264_picture.c
    • [DH] libavcodec/h264_slice.c
    • [DH] libavcodec/h264dec.c
    • [DH] libavcodec/h264dec.h

  • avcodec/h264_picture : don't assume Film Grain Params side data will be present

    17 octobre 2021, par James Almer
    avcodec/h264_picture : don't assume Film Grain Params side data will be present

    If a decoding error happens before frame side data is allocated, this assert may be
    
triggered. And since applying film grain is not enforced (we just warn it wasn't
    
applied and move on), we can just do that in such scenarios.
    

    Fixes : Assertion failure
    
Fixes : clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_H264_fuzzer-5528650032742400
    

    Signed-off-by : James Almer <jamrial@gmail.com>
    • [DH] libavcodec/h264_picture.c

  • Evolution #4103 (En cours) : Autoriser /local/cache-gd2/ et /local/cache-vignette/ dans robots.txt

    16 février 2021, par RastaPopoulos ♥

    On rouvre, le temps d’être sûr d’avoir une explication/trace/lien de où ça a été traité ?

Navigation