Recherche avancée

Médias (3)

Mot : - Tags -/image

Autres articles (111)

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

  • How we compressed videofile (all format) in android programmatically

    29 mars 2017, par prakash choudhary

    i am stuck with the funtionality for the compressed video before upload to the Amazon s3. i am looking functionality like the whatsup that compressed all the video of the gallery and camera after R&D i got FFmpeg library but that is increasing size of the app apk.Please there is any alternative t ? Any idea about this problem

  • How to use IContainer with frame-by-frame data ?

    12 novembre 2014, par AnilJ

    We have implemented a video client where it captures N number of pictures (from web cam), encodes them and packs them as a block. This block is delivered to the decoder, which then initializes a new IContainer object each time with a buffer containing this received block.

    Although this design works well, by its design it introduces a time delay in the stream delivery. Since we are capturing N frames to build a block for delivery, the delay is N times the frame rate. Also we are not sure what is the cost (time) of creating and initializing IContainer object each time.

    To improve on this, we thinking of sending frame-by-frame encoded data to the receiver. However, creating new IContainer object in this case won’t work since it can not open/initialize with a P or B frame - It always requires an I-frame to initialize else open fails.

    Now my question is, how do we use the IContainer APIs for such a requirement ? We do not want to initialize/open the IContainer object each time. We want to know if it is possible to reuse the same IContainer object while we keep feeding it the received frames one by one in sequence. This way we completely avoid the source buffering as well as receiver buffering (we however will require a de-jitter buffer).

    We are using this APIs.
    http://www.xuggle.com/public/documentation/java/api/com/xuggle/xuggler/IContainer.html

    /anil.

  • rtpdec_hevc : Drop a duplicated, nonstandard entry

    17 septembre 2014, par Vittorio Giovara
    rtpdec_hevc : Drop a duplicated, nonstandard entry

    The RFC spec draft only specifies the "H265" name - there is no
    
specification saying how to interpret "HEVC" (if such a packet
    
format is specified it could be an entirely different format).
    

    Since this is a very new standard (still a draft), there is little
    
need for compatibility with existing, broken implementations. Therefore
    
remove the extra alias, to avoid the risk of encouraging incorrect
    
usage.
    

    Intentionally keeping the ff_hevc_dynamic_handler name for the
    
handler, to use "hevc" consistently as name for the codec instead
    
of "h265" within the library internals as long as there only is one
    
single variant in actual use.
    

    Signed-off-by : Martin Storsjö <martin@martin.st>
    • [DH] libavformat/rtpdec.c
    • [DH] libavformat/rtpdec_formats.h
    • [DH] libavformat/rtpdec_hevc.c

Navigation