Advanced search

Medias (91)

Other articles (105)

  • Multilang : améliorer l’interface pour les blocs multilingues

    18 February 2011, by

    Multilang est un plugin supplémentaire qui n’est pas activé par défaut lors de l’initialisation de MediaSPIP.
    Après son activation, une préconfiguration est mise en place automatiquement par MediaSPIP init permettant à la nouvelle fonctionnalité d’être automatiquement opérationnelle. Il n’est donc pas obligatoire de passer par une étape de configuration pour cela.

  • HTML5 audio and video support

    13 April 2011, by

    MediaSPIP uses HTML5 video and audio tags to play multimedia files, taking advantage of the latest W3C innovations supported by modern browsers.
    The MediaSPIP player used has been created specifically for MediaSPIP and can be easily adapted to fit in with a specific theme.
    For older browsers the Flowplayer flash fallback is used.
    MediaSPIP allows for media playback on major mobile platforms with the above (...)

  • ANNEXE : Les plugins utilisés spécifiquement pour la ferme

    5 March 2010, by

    Le site central/maître de la ferme a besoin d’utiliser plusieurs plugins supplémentaires vis à vis des canaux pour son bon fonctionnement. le plugin Gestion de la mutualisation; le plugin inscription3 pour gérer les inscriptions et les demandes de création d’instance de mutualisation dès l’inscription des utilisateurs; le plugin verifier qui fournit une API de vérification des champs (utilisé par inscription3); le plugin champs extras v2 nécessité par (...)

On other websites (12705)

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

    14 January 2021, by 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

    


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


    


    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.

    


    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.

    


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

    


  • lavc/lpc: do not explode when windowing a 1-length array

    21 September 2022, by Lynne
    lavc/lpc: do not explode when windowing a 1-length array

    Divided by 0.
    • [DH] libavcodec/lpc.c

  • avformat/wavenc: Check umid length

    10 May 2015, by Michael Niedermayer
    avformat/wavenc: Check umid length

    Fixes potential out of array read
    

    Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
    • [DH] libavformat/wavenc.c

Browsing