Recherche avancée

Médias (1)

Mot : - Tags -/3GS

Autres articles (73)

  • Participer à sa traduction

    10 avril 2011

    Vous pouvez nous aider à améliorer les locutions utilisées dans le logiciel ou à traduire celui-ci dans n’importe qu’elle nouvelle langue permettant sa diffusion à de nouvelles communautés linguistiques.
    Pour ce faire, on utilise l’interface de traduction de SPIP où l’ensemble des modules de langue de MediaSPIP sont à disposition. ll vous suffit de vous inscrire sur la liste de discussion des traducteurs pour demander plus d’informations.
    Actuellement MediaSPIP n’est disponible qu’en français et (...)

  • HTML5 audio and video support

    13 avril 2011, par

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

  • Websites made ​​with MediaSPIP

    2 mai 2011, par

    This page lists some websites based on MediaSPIP.

Sur d’autres sites (11503)

  • How to read remote video on Amazon S3 using ffmpeg

    9 septembre 2024, par virtualize

    I need to create poster frames from videos hosted on Amazon S3 via ffmpeg.

    



    So is there a way to use the remote video file directly in ffmpeg command line like this :
    
ffmpeg -i "http://bucket.s3.amazonaws.com/video.mp4" -ss 00:00:10 -vframes 1 -f image2 "image%03d.jpg"

    



    ffmpeg just returns :
    &#xA;http://bucket.s3.amazonaws.com/video.mp4: I/O error occurred<br />&#xA;Usually that means that input file is truncated and/or corrupted.

    &#xA;&#xA;

    I also tried forcing ffmpeg to use the videos mp4 container for reading :
    &#xA;ffmpeg -f mp4 -i "http://bucket.s3.amazonaws.com/video.mp4" ...
    &#xA;But no luck.

    &#xA;&#xA;

    Wget this video from S3 and processing it locally works fine of course,
    &#xA;as well as reading the file remotely from other 'standard' http servers.
    &#xA;So I know that ffmpeg supports remote file reading, but why not on S3 ?

    &#xA;

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

    20 avril 2024, par Adrien Kaczmarek

    Problem

    &#xA;

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

    &#xA;

    Situation

    &#xA;

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

    &#xA;

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

    &#xA;

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

    • Download and package FFmpeg from John Van Sickle
    • &#xA;

    • Create a Lambda Layer with FFmpeg
    • &#xA;

    &#xA;

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

    &#xA;

    Unsuccessful Trials

    &#xA;

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

    &#xA;

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

    &#xA;

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

    &#xA;

    ffmpeg: /lib64/libm.so.6: version `GLIBC_2.27&#x27; not found (required by ffmpeg)&#xA;ffmpeg: /lib64/libpthread.so.0: version `GLIBC_2.28&#x27; not found (required by ffmpeg)&#xA;ffmpeg: /lib64/libc.so.6: version `GLIBC_2.27&#x27; not found (required by ffmpeg)&#xA;ffmpeg: /lib64/libc.so.6: version `GLIBC_2.28&#x27; not found (required by ffmpeg)&#xA;

    &#xA;

    Any help would be greatly appreciated,

    &#xA;

    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.

    &#xA;

    Thank you

    &#xA;

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

    22 avril 2024, par Adrien Kaczmarek

    Problem

    &#xA;

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

    &#xA;

    Situation

    &#xA;

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

    &#xA;

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

    &#xA;

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

    • Download and package FFmpeg from John Van Sickle
    • &#xA;

    • Create a Lambda Layer with FFmpeg
    • &#xA;

    &#xA;

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

    &#xA;

    Unsuccessful Trials

    &#xA;

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

    &#xA;

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

    &#xA;

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

    &#xA;

    ffmpeg: /lib64/libm.so.6: version `GLIBC_2.27&#x27; not found (required by ffmpeg)&#xA;ffmpeg: /lib64/libpthread.so.0: version `GLIBC_2.28&#x27; not found (required by ffmpeg)&#xA;ffmpeg: /lib64/libc.so.6: version `GLIBC_2.27&#x27; not found (required by ffmpeg)&#xA;ffmpeg: /lib64/libc.so.6: version `GLIBC_2.28&#x27; not found (required by ffmpeg)&#xA;

    &#xA;

    Any help would be greatly appreciated,

    &#xA;

    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.

    &#xA;

    Thank you

    &#xA;