Recherche avancée

Médias (91)

Autres articles (56)

  • Gestion des droits de création et d’édition des objets

    8 février 2011, par

    Par défaut, beaucoup de fonctionnalités sont limitées aux administrateurs mais restent configurables indépendamment pour modifier leur statut minimal d’utilisation notamment : la rédaction de contenus sur le site modifiables dans la gestion des templates de formulaires ; l’ajout de notes aux articles ; l’ajout de légendes et d’annotations sur les images ;

  • Dépôt de média et thèmes par FTP

    31 mai 2013, par

    L’outil MédiaSPIP traite aussi les média transférés par la voie FTP. Si vous préférez déposer par cette voie, récupérez les identifiants d’accès vers votre site MédiaSPIP et utilisez votre client FTP favori.
    Vous trouverez dès le départ les dossiers suivants dans votre espace FTP : config/ : dossier de configuration du site IMG/ : dossier des média déjà traités et en ligne sur le site local/ : répertoire cache du site web themes/ : les thèmes ou les feuilles de style personnalisées tmp/ : dossier de travail (...)

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

Sur d’autres sites (7851)

  • lavf/dashenc : Add DASH segment type auto and make it the default

    17 novembre 2018, par Andrey Semashev
    lavf/dashenc : Add DASH segment type auto and make it the default

    This commit restores the ability to create DASH streams with codecs
    
that require different containers that was lost after commit
    
2efdbf7367989cf9d296c25fa3d2aff8d6e25fdd. It adds a new "auto" value for
    
the dash_segment_type option and makes it the default. When in this mode,
    
the segment format will be chosen based on the codec used in the stream :
    
webm for Vorbis, Opus, VP8 or VP9, mp4 otherwise.
    • [DH] doc/muxers.texi
    • [DH] libavformat/dashenc.c

  • avfilter/buffersrc : promote unspecified color metadata

    12 janvier 2024, par Niklas Haas
    avfilter/buffersrc : promote unspecified color metadata

    Currently, this only affects untagged RGB/XYZ/Gray, which get forced to
    
their corresponding metadata before entering the filter graph. The main
    
justification for this change, however, is the planned ability to add
    
automatic promotion of unspecified yuv to mpeg range yuv.
    

    Notably, this change will never allow accidentally cross-promoting
    
unspecified to jpeg or to a specific YUV matrix, since that is still
    
bound by the constraints of YUV range negotiation as set up by
    
query_formats.
    • [DH] libavfilter/buffersrc.c
    • [DH] tests/ref/fate/rgb24-mkv

  • FFmpeg support for repeating last audiosample and videoframe when input stream stops or delivers corrupt data ?

    14 novembre 2017, par Vemund Kvam

    Our goal is to deliver on-the-fly packaged Live HLS and Mpeg DASH from a mpeg-ts multicast source.

    We use ffmpeg to transcode/mux the mpeg-ts input to ISMV (smooth streaming format) and transfer via http to Unified Origin running Apache.

    What we want to achieve is a constant ISMV stream to Unified Origin regardless of input stability.

    We have tried separating decoding and encoding by having two FFMPEG processes :

    1. Decodes "rawvideo" and "s16be" (audio) and sends to two python developed buffers that have the ability to repeat the last frame/sample if no input is provided.
    2. Uses the two buffer as input (over tcp) and encode/mux to ISMV.

    This solution seems to solve the stability issue, but synchronising a/v and knowing when to provide repeated frames instead of live frames seems to be impossible. We have so far assumed that ffmpeg requires a continuous input stream to produce any output if the input is not or can not be provided, output stops.

    Does FFmpeg have built in functionality for repeating a/v when the input stream either stops delivering data or delivers corrupt data ?

    Is there any industry standard way to deal with unstable input ?

Navigation