Recherche avancée

Médias (3)

Mot : - Tags -/collection

Autres articles (67)

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

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

  • Publier sur MédiaSpip

    13 juin 2013

    Puis-je poster des contenus à partir d’une tablette Ipad ?
    Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir

Sur d’autres sites (10593)

  • MP4 - get current subtitle text

    20 février 2019, par murrdpirate

    I’m trying to find a way to grab the current subtitle in an MP4 file. I see that ffmpeg can extract all subtitles into an .srt file, but it would be useful for me to just grab the current subtitle based on the current timestamp of a video being played. Especially useful if it can be done with python. This would be akin to opencv and moviepy, where I can extract the current frame as an image based on the current timestamp of the video.

    I see a lot of libraries that work with subtitle .srt files (e.g. pysrt) but none that access individual subtitles from a playng mp4 file.

  • Manually feeding x264 with my own motion data ?

    6 septembre 2011, par ldoogy

    I am trying to encode a stream using x264 (by feeding individual images), but what's unusual is that I already have some motion information for my frames. I know exactly which areas have been modified in each frame, and I know where motion has occurred in the frame.

    Is there a way to feed x264 my own motion information ? I'd like to give it motion vectors for given areas in the frame, and somehow tell it that certain areas in the frame are guaranteed to not have had any motion in them.

    I think this might significantly improve the performance of the encoding (because I'm allowing the codec to completely skip the motion estimation phase), and should also somewhat increase quality in cases where the encoder's motion estimation algos might have missed the motion that actually occurred.

    Do I need to modify the encoder in order to do this, or is this supported in the existing API ?

  • Revision 096eaba728 : Remove VP8 save_reg_neon function This patch did a cleanup following the commit

    29 avril 2014, par Yunqing Wang

    Changed Paths :
     Delete /vp8/common/arm/neon/save_reg_neon.asm


     Modify /vp8/decoder/onyxd_if.c


     Modify /vp8/encoder/onyx_if.c


     Modify /vp8/vp8_common.mk



    Remove VP8 save_reg_neon function

    This patch did a cleanup following the commit "Save NEON registers
    in VP8 NEON functions". The pushing/poping of callee-saved NEON
    registers was moved into individual NEON functions. Therefore,
    we don’t need to save those registers at the beginning of codec.
    The related code was removed.

    Change-Id : I5648166514fc9beffb780aa138495597731f49ea

Navigation