Recherche avancée

Médias (1)

Mot : - Tags -/wave

Autres articles (94)

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

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

  • ANNEXE : Les plugins utilisés spécifiquement pour la ferme

    5 mars 2010, par

    Le site central/maître de la ferme a besoin d’utiliser plusieurs plugins supplémentaires vis à vis des canaux pour son bon fonctionnement. le plugin Gestion de la mutualisation ; le plugin inscription3 pour gérer les inscriptions et les demandes de création d’instance de mutualisation dès l’inscription des utilisateurs ; le plugin verifier qui fournit une API de vérification des champs (utilisé par inscription3) ; le plugin champs extras v2 nécessité par inscription3 (...)

Sur d’autres sites (7663)

  • avformat/libsrt : fix race condition with libsrt_network_wait_fd and epoll

    31 janvier 2021, par Marton Balint
    avformat/libsrt : fix race condition with libsrt_network_wait_fd and epoll

    The way SRT's async / epoll-based IO works is that the event status is stored
    
in the epoll containers. That is, if an event occurs on an SRT socket, and that
    
SRT socket isn't part of any epoll container, then that event is lost. If we
    
later add that socket to an epoll container, we still won't receive the event
    
even if it wasn't serviced.
    

    Therefore we create the epoll and put the fd into it right after the connection
    
is established.
    

    See http://lists.ffmpeg.org/pipermail/ffmpeg-devel/2021-January/275334.html
    

    Signed-off-by : Marton Balint <cus@passwd.hu>
    • [DH] libavformat/libsrt.c

  • avcodec/[e]ac3enc : Make encoders init-threadsafe, fix race

    3 décembre 2020, par Andreas Rheinhardt
    avcodec/[e]ac3enc : Make encoders init-threadsafe, fix race

    ff_eac3_exponent_init() set values twice when initializing a static
    
table ; ergo the initialization code must not run concurrently with
    
a running EAC-3 encoder. Yet this code is executed every time an EAC-3
    
encoder is initialized. So use ff_thread_once() for this and also for a
    
similar initialization performed for all AC-3 encoders to make them all
    
init-threadsafe.
    

    Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@gmail.com>
    • [DH] libavcodec/ac3enc.c
    • [DH] libavcodec/ac3enc_fixed.c
    • [DH] libavcodec/ac3enc_float.c
    • [DH] libavcodec/eac3enc.c

  • avcodec/pthread_slice : Don't use static variable, fix race

    28 novembre 2020, par Andreas Rheinhardt
    avcodec/pthread_slice : Don't use static variable, fix race

    ff_slice_thread_init() uses a static variable to hold a function
    
pointer, although the value of said pointer needn't be saved between
    
different runs of this function at all.
    

    The reason for this being so is probably that said pointer points to
    
a static function (if used) ; but storage class specifiers like "static"
    
are not part of the type of an object and so including it in the pointer
    
declaration is wrong (anyway, "static" means different things in both
    
contexts : for the function declaration it affects linkage, for the
    
variable storage duration).
    

    Using a static variable here can lead to races, e.g. when initializing
    
VP9 (for which said function pointer was added) and H.264 with slice
    
threading. The latter has the FF_CODEC_CAP_INIT_THREADSAFE flag set and
    
is therefore unaffected by the lock guarding initializations of
    
decoders.
    

    Reviewed-by : Anton Khirnov <anton@khirnov.net>
    
Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@gmail.com>
    • [DH] libavcodec/pthread_slice.c

Navigation