Recherche avancée

Médias (0)

Mot : - Tags -/navigation

Aucun média correspondant à vos critères n’est disponible sur le site.

Autres articles (79)

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

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

  • De l’upload à la vidéo finale [version standalone]

    31 janvier 2010, par

    Le chemin d’un document audio ou vidéo dans SPIPMotion est divisé en trois étapes distinctes.
    Upload et récupération d’informations de la vidéo source
    Dans un premier temps, il est nécessaire de créer un article SPIP et de lui joindre le document vidéo "source".
    Au moment où ce document est joint à l’article, deux actions supplémentaires au comportement normal sont exécutées : La récupération des informations techniques des flux audio et video du fichier ; La génération d’une vignette : extraction d’une (...)

Sur d’autres sites (8279)

  • avformat/webm_chunk : Use API functions for child muxer

    29 février 2020, par Andreas Rheinhardt
    avformat/webm_chunk : Use API functions for child muxer

    instead of calling the write_header/packet/trailer functions directly
    
via the function pointers. Also, use distinct AVStreams for the child
    
AVFormatContext (up until now the two AVFormatContexts shared their
    
AVStreams because allocating their own was deemed too onerous).
    

    Using the function pointers directly meant that the Matroska muxer's
    
init-function was never called, because init-functions were only
    
introduced a few months after webm_chunk has been added and no one
    
thought of/bothered to adapt webm_chunk for this (when the init-function
    
was added in b287d7ea, the code setting the timebase was moved to it,
    
so that the timebases were no longer set to ms-precision when using
    
the webm_chunk muxer ; this has been fixed after some time in 42a635dd
    
by setting the timebases direcly (instead of calling the init-function)).
    

    And when 982a98a0 added a deinit-function for the Matroska muxer, it
    
introduced memleaks in webm_chunk, because the child muxer's internal
    
structures were no longer freed when calling write_trailer directly.
    
(Given that the init function has never ever been called, the child
    
muxer has never ever been properly initialized, so that the
    
deinit-function was not called when freeing the child context.)
    

    This commit stops calling the function pointers directly and instead
    
uses the standard API functions for muxers. This fixes the above
    
mentioned memleaks. (Memleaks are still possible on error. This will be
    
fixed in a future commit that adds a deinit-function to webm_chunk
    
itself.)
    

    Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@gmail.com>
    • [DH] libavformat/webm_chunk.c

  • avformat/webm_chunk : Copy more information to the child AVFormatContext

    29 février 2020, par Andreas Rheinhardt
    avformat/webm_chunk : Copy more information to the child AVFormatContext

    In particular the flags are important so that AVFMT_FLAG_BITEXACT can be
    
honoured by the child muxer.
    

    Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@gmail.com>
    • [DH] libavformat/webm_chunk.c

  • avcodec/options_table : make AVCodecContext->profile search for child constants

    10 mai 2020, par Marton Balint
    avcodec/options_table : make AVCodecContext->profile search for child constants

    This change makes it possible for child encoders to define custom profile
    
option names which can be used for setting the AVCodecContext->profile.
    

    Also rename unit name to something rather unique, so it won't be used elsewhere.
    

    Signed-off-by : Marton Balint <cus@passwd.hu>
    • [DH] doc/codecs.texi
    • [DH] libavcodec/options_table.h

Navigation