Recherche avancée

Médias (91)

Autres articles (30)

  • Websites made ​​with MediaSPIP

    2 mai 2011, par

    This page lists some websites based on MediaSPIP.

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

  • Publier sur MédiaSpip

    13 juin 2013

    Puis-je poster des contenus à partir d’une tablette Ipad ?
    Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir

Sur d’autres sites (6845)

  • 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

    


  • Swift framework project with internal C module - Undefined symbols for architecture arm64

    29 mars 2020, par Phạm Phi Phúc

    I’m creating Swift framework project using FFmpeg module internally.

    Steps are :

    1. Download source of FFmpeg from official website.
    2. Build it by build script here : https://github.com/kewlbear/FFmpeg-iOS-build-script
    3. Copy built file to project
    4. Create file module.modulemap, it’s content is :
    module FFmpeg [system][extern_c] {

       header "include/libavcodec/avcodec.h"
       header "include/libavdevice/avdevice.h"
       header "include/libavfilter/avfilter.h"
       header "include/libavformat/avformat.h"
       header "include/libavutil/avutil.h"
       header "include/libswresample/swresample.h"
       header "include/libswscale/swscale.h"

       export *
    }

    Project tree is :

    enter image description here

    1. Set Import paths for both project settings and target settings to
      $(SRCROOT)/MediaToolkit/Libraries/FFmpeg/**
    2. My source code is :
    import Foundation
    import FFmpeg

    public class MediaToolkit {
       public init(){}

       public func hello() {
           print("AVFMT_NOFILE: \(AVFMT_NOFILE)")
           avformat_network_init()
       }
    }

    When I build it, I received error

    Undefined symbols for architecture arm64:
     "_avformat_network_init", referenced from:
         MediaToolkit.MediaToolkit.hello(Swift.String) -> () in MediaToolkit.o
    ld: symbol(s) not found for architecture arm64
    clang: error: linker command failed with exit code 1 (use -v to see invocation)

    If I remove line avformat_network_init(), it will print AVFMT_NOFILE: 1

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

    22 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