Recherche avancée

Médias (1)

Mot : - Tags -/remix

Autres articles (99)

  • MediaSPIP 0.1 Beta version

    25 avril 2011, par

    MediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
    The zip file provided here only contains the sources of MediaSPIP in its standalone version.
    To get a working installation, you must manually install all-software dependencies on the server.
    If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...)

  • Mise à jour de la version 0.1 vers 0.2

    24 juin 2013, par

    Explications des différents changements notables lors du passage de la version 0.1 de MediaSPIP à la version 0.3. Quelles sont les nouveautés
    Au niveau des dépendances logicielles Utilisation des dernières versions de FFMpeg (>= v1.2.1) ; Installation des dépendances pour Smush ; Installation de MediaInfo et FFprobe pour la récupération des métadonnées ; On n’utilise plus ffmpeg2theora ; On n’installe plus flvtool2 au profit de flvtool++ ; On n’installe plus ffmpeg-php qui n’est plus maintenu au (...)

  • Personnaliser en ajoutant son logo, sa bannière ou son image de fond

    5 septembre 2013, par

    Certains thèmes prennent en compte trois éléments de personnalisation : l’ajout d’un logo ; l’ajout d’une bannière l’ajout d’une image de fond ;

Sur d’autres sites (14485)

  • 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

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

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

Navigation