Recherche avancée

Médias (91)

Autres articles (87)

  • MediaSPIP Player : problèmes potentiels

    22 février 2011, par

    Le lecteur ne fonctionne pas sur Internet Explorer
    Sur Internet Explorer (8 et 7 au moins), le plugin utilise le lecteur Flash flowplayer pour lire vidéos et son. Si le lecteur ne semble pas fonctionner, cela peut venir de la configuration du mod_deflate d’Apache.
    Si dans la configuration de ce module Apache vous avez une ligne qui ressemble à la suivante, essayez de la supprimer ou de la commenter pour voir si le lecteur fonctionne correctement : /** * GeSHi (C) 2004 - 2007 Nigel McNie, (...)

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

  • Création définitive du canal

    12 mars 2010, par

    Lorsque votre demande est validée, vous pouvez alors procéder à la création proprement dite du canal. Chaque canal est un site à part entière placé sous votre responsabilité. Les administrateurs de la plateforme n’y ont aucun accès.
    A la validation, vous recevez un email vous invitant donc à créer votre canal.
    Pour ce faire il vous suffit de vous rendre à son adresse, dans notre exemple "http://votre_sous_domaine.mediaspip.net".
    A ce moment là un mot de passe vous est demandé, il vous suffit d’y (...)

Sur d’autres sites (11851)

  • avcodec/mpeg4videodec : Move use_intra_dc_vlc to stack, fix data race

    26 janvier 2022, par Andreas Rheinhardt
    avcodec/mpeg4videodec : Move use_intra_dc_vlc to stack, fix data race
    

    use_intra_dc_vlc is currently kept in sync between frame threads
    in mpeg4_update_thread_context(), yet it is set when decoding
    blocks, i.e. after ff_thread_finish_setup(). This is a data race
    and therefore undefined behaviour.

    This race can be fixed easily by moving the variable from the context
    to the stack : use_intra_dc_vlc is only read in
    mpeg4_decode_block() and only if one is decoding an intra block.
    There are three callsites for this function : One in
    mpeg4_decode_partitioned_mb() which always sets use_intra_dc_vlc
    before the call and two in mpeg4_decode_mb(). One of these callsites
    is for intra blocks and use_intra_dc_vlc is set before it ;
    the last callsite is for non-intra blocks, where use_intra_dc_vlc
    is ignored. So if it is used, it always uses a new value and can
    therefore be moved to the stack.

    The above also explains why this data race did not lead to
    FATE-test failures.

    Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@outlook.com>

    • [DH] libavcodec/mpeg4video.h
    • [DH] libavcodec/mpeg4videodec.c
  • avcodec/mpegpicture : Don't copy unnecessarily, fix race

    8 août 2022, par Andreas Rheinhardt
    avcodec/mpegpicture : Don't copy unnecessarily, fix race
    

    mpegvideo uses an array of Pictures and when it is done with using
    them, it only unreferences them incompletely : Some buffers are kept
    so that they can be reused lateron if the same slot in the Picture
    array is reused, making this a sort of a bufferpool.
    (Basically, a Picture is considered used if the AVFrame's buf is set.)
    Yet given that other pieces of the decoder may have a reference to
    these buffers, they need not be writable and are made writable using
    av_buffer_make_writable() when preparing a new Picture. This involves
    reading the buffer's data, although the old content of the buffer
    need not be retained.

    Worse, this read can be racy, because the buffer can be used by another
    thread at the same time. This happens for Real Video 3 and 4.

    This commit fixes this race by no longer copying the data ;
    instead the old buffer is replaced by a new, zero-allocated buffer.

    (Here are the details of what happens with three or more decoding threads
    when decoding rv30.rm from the FATE-suite as happens in the rv30 test :
    The first decoding thread uses the first slot of its picture array
    to store its current pic ; update_thread_context copies this for the
    second thread that decodes a P-frame. It uses the second slot in its
    Picture array to store its P-frame. This arrangement is then copied
    to the third decode thread, which decodes a B-frame. It uses the third
    slot in its Picture array for its current frame.
    update_thread_context copies this to the next thread. It unreferences
    the third slot containing the other B-frame and then it reuses this
    slot for its current frame. Because the pic array slots are only
    incompletely unreferenced, the buffers of the previous B-frame are
    still in there and they are not writable ; in fact the previous
    thread is concurrently writing to them, causing races when making
    the buffer writable.)

    Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@outlook.com>

    • [DH] libavcodec/mpegpicture.c
  • avcodec/hevcdec : Check early whether film grain is supported, fix race

    22 août 2022, par Andreas Rheinhardt
    avcodec/hevcdec : Check early whether film grain is supported, fix race
    

    Applying film grain happens after ff_thread_finish_setup(),
    so the parameters synced in hevc_update_thread_context() must not
    be modified. But this is exactly what happens in case applying
    film grain fails. (The likely result is that in case of frame threading
    an uninitialized frame is output.)

    Given that it is actually very easy to know in advance whether
    ff_h274_apply_film_grain() supports a given set of parameters,
    one can check for this before ff_thread_finish_setup()
    and avoid allocating an unused buffer lateron.

    Reviewed-by : Niklas Haas <ffmpeg@haasn.xyz>
    Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@outlook.com>

    • [DH] libavcodec/h274.h
    • [DH] libavcodec/hevcdec.c
    • [DH] libavcodec/hevcdec.h