Recherche avancée

Médias (1)

Mot : - Tags -/MediaSPIP 0.2

Autres articles (70)

  • Emballe médias : à quoi cela sert ?

    4 février 2011, par

    Ce plugin vise à gérer des sites de mise en ligne de documents de tous types.
    Il crée des "médias", à savoir : un "média" est un article au sens SPIP créé automatiquement lors du téléversement d’un document qu’il soit audio, vidéo, image ou textuel ; un seul document ne peut être lié à un article dit "média" ;

  • Contribute to a better visual interface

    13 avril 2011

    MediaSPIP is based on a system of themes and templates. Templates define the placement of information on the page, and can be adapted to a wide range of uses. Themes define the overall graphic appearance of the site.
    Anyone can submit a new graphic theme or template and make it available to the MediaSPIP community.

  • Creating farms of unique websites

    13 avril 2011, par

    MediaSPIP platforms can be installed as a farm, with a single "core" hosted on a dedicated server and used by multiple websites.
    This allows (among other things) : implementation costs to be shared between several different projects / individuals rapid deployment of multiple unique sites creation of groups of like-minded sites, making it possible to browse media in a more controlled and selective environment than the major "open" (...)

Sur d’autres sites (7158)

  • Fixed grammar error in german range validator message. Fixes #315

    29 mars 2012, par fbuchinger

    m localization/messages_de.js Fixed grammar error in german range validator message. Fixes #315

  • avfilter/avf_abitscope : Correct range for framerate

    23 mars 2017, par Gyan Doshi
    avfilter/avf_abitscope : Correct range for framerate

    Signed-off-by : Gyan Doshi <gyandoshi@gmail.com>
    
Signed-off-by : Paul B Mahol <onemda@gmail.com> (via IRC)
    • [DH] libavfilter/avf_abitscope.c

  • ffmpeg output file size grows faster than linearly with movie length

    14 janvier 2021, par Jakob Filser

    I'm using ffmpeg to string together some .bmp images into a movie. In total, there are 1001 frames, amounting to 0:40 length. The command I'm using is

    &#xA;

    ffmpeg -f image2 -i render.%05d.bmp -c:v libx264 -s 512:268 render.mp4&#xA;

    &#xA;

    The output file is 33,2 MB large, which is about twice the size of a full HD (about 16 times the pixels !) video of the same length. Apart from the file size being unreasonably large, I realized it grows faster than linearly (can't tell exactly if it is quadratic, exponential etc.) with the number of frames. After 100 frames it is about 1536 KB large (which is already too large), after 500 frames it is already 15104 KB, and after 1001 it finally arrives at 34085 KB.

    &#xA;

    My educated guess would be that for each frame it stores some information about all of the previous frames again, which makes absolutely no sense.

    &#xA;

    What am I doing wrong ? Before you recommend libx265 to me : It turns the entire video green.

    &#xA;

Navigation