Recherche avancée

Médias (91)

Autres articles (97)

  • Encoding and processing into web-friendly formats

    13 avril 2011, par

    MediaSPIP automatically converts uploaded files to internet-compatible formats.
    Video files are encoded in MP4, Ogv and WebM (supported by HTML5) and MP4 (supported by Flash).
    Audio files are encoded in MP3 and Ogg (supported by HTML5) and MP3 (supported by Flash).
    Where possible, text is analyzed in order to retrieve the data needed for search engine detection, and then exported as a series of image files.
    All uploaded files are stored online in their original format, so you can (...)

  • Installation en mode ferme

    4 février 2011, par

    Le mode ferme permet d’héberger plusieurs sites de type MediaSPIP en n’installant qu’une seule fois son noyau fonctionnel.
    C’est la méthode que nous utilisons sur cette même plateforme.
    L’utilisation en mode ferme nécessite de connaïtre un peu le mécanisme de SPIP contrairement à la version standalone qui ne nécessite pas réellement de connaissances spécifique puisque l’espace privé habituel de SPIP n’est plus utilisé.
    Dans un premier temps, vous devez avoir installé les mêmes fichiers que l’installation (...)

  • Installation en mode standalone

    4 février 2011, par

    L’installation de la distribution MediaSPIP se fait en plusieurs étapes : la récupération des fichiers nécessaires. À ce moment là deux méthodes sont possibles : en installant l’archive ZIP contenant l’ensemble de la distribution ; via SVN en récupérant les sources de chaque modules séparément ; la préconfiguration ; l’installation définitive ;
    [mediaspip_zip]Installation de l’archive ZIP de MediaSPIP
    Ce mode d’installation est la méthode la plus simple afin d’installer l’ensemble de la distribution (...)

Sur d’autres sites (7756)

  • How to run FFMPEG with —enable-libfontconfig on Amazon Lambda

    20 avril 2024, par Adrien Kaczmarek

    Problem

    


    I want to run FFmpeg on AWS Lambda (Amazon Linux 2) with the configuration --enable-libfontconfig enable.

    


    Situation

    


    I already have FFmpeg running on AWS Lambda without the configuration --enable-libfontconfig.

    


    Here is the step I took to run FFmpeg on AWS Lambda (see official guide) :

    


      

    • Connect to Amazon EC2 running on AL2 (environment used by Lambda for Python 3.11)
    • 


    • Download and package FFmpeg from John Van Sickle
    • 


    • Create a Lambda Layer with FFmpeg
    • 


    


    Unfortunately, the version built by John Van Sickle doesn't have the configuration --enable-libfontconfig enabled.

    


    Unsuccessful Trials

    


    I tried to rebuilt it from scratch following the installation guide but without success (and the guide doesn't install font related dependencies)

    


    I tried to install it with brew but the command brew install ffmpeg didn't succeed on AL2.

    


    I tried to install ffmpeg from ffmpeg-master-latest-linux64-gpl.tar.xz. Unfortunately, this build of ffmpeg doesn't run on AL2 :

    


    ffmpeg: /lib64/libm.so.6: version `GLIBC_2.27' not found (required by ffmpeg)
ffmpeg: /lib64/libpthread.so.0: version `GLIBC_2.28' not found (required by ffmpeg)
ffmpeg: /lib64/libc.so.6: version `GLIBC_2.27' not found (required by ffmpeg)
ffmpeg: /lib64/libc.so.6: version `GLIBC_2.28' not found (required by ffmpeg)


    


    Any help would be greatly appreciated,

    


    Please make sure your answer is up to date and tested. Too many answers out there are auto-generated, too generic, or simple redirect without context.

    


    Thank you

    


  • fate/webp : add test for webp lossless decoding (rgb and rgba)

    25 juin 2016, par Martin Vignali
    fate/webp : add test for webp lossless decoding (rgb and rgba)
    

    output have been compared with official decoding tool output (dwebp)

    Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>

    • [DH] tests/fate/image.mak
    • [DH] tests/ref/fate/webp-rgb-lossless
    • [DH] tests/ref/fate/webp-rgba-lossless
  • avr32 : remove explicit support

    9 juin 2024, par Rémi Denis-Courmont
    avr32 : remove explicit support
    

    The vendor has long since switched to Arm, with the last product
    reaching their official end-of-life over 11 years ago. Linux support for
    the ISA was dropped 7 years ago. More importantly, this architecture was
    never supported by upstream GCC, and the vendor fork is stuck at version
    4.2, which FFmpeg no longer supports (as per C11 requirement).

    Presumably, this is still the case given the lack of vendor support.
    Indeed all of the code being removed here consisted of inline assembler
    scalar optimisations. A sane C compiler should be able to perform those
    automatically nowadays (with the sole exception of fast CLZ detection),
    but this is moot as this architecture is evidently dead.

    • [DH] configure
    • [DH] libavcodec/avr32/mathops.h
    • [DH] libavcodec/mathops.h
    • [DH] libavutil/avr32/intreadwrite.h
    • [DH] libavutil/intreadwrite.h