Recherche avancée

Médias (91)

Autres articles (34)

  • Contribute to documentation

    13 avril 2011

    Documentation is vital to the development of improved technical capabilities.
    MediaSPIP welcomes documentation by users as well as developers - including : critique of existing features and functions articles contributed by developers, administrators, content producers and editors screenshots to illustrate the above translations of existing documentation into other languages
    To contribute, register to the project users’ mailing (...)

  • Use, discuss, criticize

    13 avril 2011, par

    Talk to people directly involved in MediaSPIP’s development, or to people around you who could use MediaSPIP to share, enhance or develop their creative projects.
    The bigger the community, the more MediaSPIP’s potential will be explored and the faster the software will evolve.
    A discussion list is available for all exchanges between users.

  • Librairies et binaires spécifiques au traitement vidéo et sonore

    31 janvier 2010, par

    Les logiciels et librairies suivantes sont utilisées par SPIPmotion d’une manière ou d’une autre.
    Binaires obligatoires FFMpeg : encodeur principal, permet de transcoder presque tous les types de fichiers vidéo et sonores dans les formats lisibles sur Internet. CF ce tutoriel pour son installation ; Oggz-tools : outils d’inspection de fichiers ogg ; Mediainfo : récupération d’informations depuis la plupart des formats vidéos et sonores ;
    Binaires complémentaires et facultatifs flvtool2 : (...)

Sur d’autres sites (7894)

  • How to build SDL libraries for Android

    4 mars 2013, par Harish

    I am planning to use SDL (Simple DirectMedia Layer) to display video output in my Android application that uses ffmpeg libraries. I have downloaded the sources from http://www.libsdl.org/download-1.2.php and built (./configure, make & make install) on my Ubuntu. But when I use these .so files the Android ndk-build complains that "Could not read symbols. File in wrong Format".

    Can I use the .so files that are built on Ubuntu on Android or do I need to build the SDL for Android in a different way ?

  • Electron, Chromium and ffmpeg licencing confusion [closed]

    12 mars 2021, par Iamisti

    Intro :
Recently I'm working on an electron based application that is free to use but also has subscription based services.
It came to my attention that ffmpeg is shipped with electron, which has GPL/LGPL licence.

    


    My quetion is :

    


      

    • Am I legally able to still distribute the application and be licence-compliant with ffmpeg without owning any proper licence to it ? I thought chromium dealt with the licencing on this topic since so many applications nowadays are shipped with using electron and chromium under the hood.

      • 


    • How do I compile/build electron to make it licence compatible (in case its not ?)

      • 


    


    I did a lot of reseearch and I found out the followings :

    


      


    • ffmpeg is shipped with chromium, they built their own version of ffmpeg and it seems they also have licence for it. Although that might be that they just push the responsibility down on the software developer/company who distributes their application with chromium.
Chromium licence for ffmpeg : https://chromium.googlesource.com/chromium/third_party/ffmpeg/+/703e920bb75053bf6b87d41d198cbbfbce3fb7ad/LICENSE

      


      • 


    • Apparently ffmpeg has a checklist of how to be licence compliant. Does that mean if I do all these steps, I can still distribute the application and can legally use it ? Licence checklist for ffmpeg : http://ffmpeg.org/legal.html

      


      • 


    • checking out some popular electron applications like Discord, Figma, Slack, etc... they ALL have ffmpeg included cause of electron when you install them. I wonder how they made it legal ? I don't see any of these checklists done on any of these popular applications.

      


      • 


    


    I'm know very little regarding licences, so any help would be incredibly huge help for me.

    


  • Trouble compiling x264 on a mac OS X

    26 juin 2013, par Bernt Habermeier

    I'm having trouble compiling x264 (http://www.videolan.org/developers/x264.html) on a Mac with the command line tools from XCode. The following steps don't work :

    git clone git://git.videolan.org/x264.git
    
cd x264
    
./configure
    
make

    That ends up giving you the following error :

    gcc -Wshadow -O3 -ffast-math -m64  -Wall -I. -I. -falign-loops=16 -mdynamic-no-pic -arch x86_64 -std=gnu99 -mpreferred-stack-boundary=5  -I/usr/local/include    -I/usr/local/include   -fomit-frame-pointer -fno-tree-vectorize   -c -o x264.o x264.c
    
In file included from ./extras/cl.h:27,
    
                 from common/opencl.h:31,
    
                 from common/common.h:209,
    
                 from x264.c:33:
    
./extras/cl_platform.h:64:10: warning: #warning This path should never happen outside of internal operating system development. AvailabilityMacros do not function correctly here!
    
In file included from common/opencl.h:31,
    
                 from common/common.h:209,
    
                 from x264.c:33:
    
./extras/cl.h:1165: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘cl_mem’
    
./extras/cl.h:1175: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘cl_mem’
    
./extras/cl.h:1187: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘cl_int’
    
./extras/cl.h:1191: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘cl_int’
    
./extras/cl.h:1196: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘cl_int’
    
./extras/cl.h:1199: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘cl_int’
    
./extras/cl.h:1202: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘void’
    
make: *** [x264.o] Error 1

    How do you compile x264 for Mac OS X with the latest XCode Command Line tools ?

Navigation