Recherche avancée

Médias (91)

Autres articles (40)

  • Des sites réalisés avec MediaSPIP

    2 mai 2011, par

    Cette page présente quelques-uns des sites fonctionnant sous MediaSPIP.
    Vous pouvez bien entendu ajouter le votre grâce au formulaire en bas de page.

  • Support audio et vidéo HTML5

    10 avril 2011

    MediaSPIP utilise les balises HTML5 video et audio pour la lecture de documents multimedia en profitant des dernières innovations du W3C supportées par les navigateurs modernes.
    Pour les navigateurs plus anciens, le lecteur flash Flowplayer est utilisé.
    Le lecteur HTML5 utilisé a été spécifiquement créé pour MediaSPIP : il est complètement modifiable graphiquement pour correspondre à un thème choisi.
    Ces technologies permettent de distribuer vidéo et son à la fois sur des ordinateurs conventionnels (...)

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

  • What does the ffmpeg loglevels mean ? [closed]

    2 avril 2013, par naxa

    FFmpeg has several loglevels (see -loglevel). These are, in order : quiet, panic, fatal, error, warning, info, verbose and debug.

    But the documentation is not very verbose with explaining their meanings.

    It's true that all names are self-documenting enough so they give some intuitive sense for when to use them. But when in doubt, from the user as well as the developer's perspective, in decision situations, it would help to have a clear definition of each level.

    I would like to know which one is for what purpose, in order to know when to use them. I couldn't find any more hints on this. Especially on the difference between panic, fatal, error and info, verbose, debug.

    I think I've found the code for these but I still don't know their exact purposeful 'boundaries'. Is there an explanation on this, (perhaps outside the ffmpeg project) ?

  • What do the ffmpeg loglevels mean ? [closed]

    12 juillet 2014, par naxa

    FFmpeg has several loglevels (see -loglevel). These are, in order : quiet, panic, fatal, error, warning, info, verbose and debug.

    But the documentation is not very verbose with explaining their meanings.

    It’s true that all names are self-documenting enough so they give some intuitive sense for when to use them. But when in doubt, from the user as well as the developer’s perspective, in decision situations, it would help to have a clear definition of each level.

    I would like to know which one is for what purpose, in order to know when to use them. I couldn’t find any more hints on this. Especially on the difference between panic, fatal, error and info, verbose, debug.

    I think I’ve found the code for these but I still don’t know their exact purposeful ’boundaries’. Is there an explanation on this, (perhaps outside the ffmpeg project) ?

  • avformat/hlsenc : Fix leak of options when initializing muxing fails

    16 décembre 2019, par Andreas Rheinhardt
    avformat/hlsenc : Fix leak of options when initializing muxing fails

    hls_mux_init() currently leaks an AVDictionary if opening a dynamic
    
buffer fails or if avformat_init_output fails. This has been fixed by
    
moving the initialization resp. the freeing of the dictionary around :
    
In the former case to a place after opening the dynamic buffer, in the
    
latter to a place before the check for initialization failure so that it
    
is done unconditionally.
    

    Furthermore, the dictionary is now only copied and freed if the options
    
in it are actually used (namely when in SEGMENT_TYPE_FMP4 mode).
    

    Finally, a similar situation in hls_start() has been fixed, too.
    

    Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@gmail.com>
    
Reviewed-by : Steven Liu <lq@onvideo.cn>
    • [DH] libavformat/hlsenc.c

Navigation