Recherche avancée

Médias (91)

Autres articles (42)

  • Keeping control of your media in your hands

    13 avril 2011, par

    The vocabulary used on this site and around MediaSPIP in general, aims to avoid reference to Web 2.0 and the companies that profit from media-sharing.
    While using MediaSPIP, you are invited to avoid using words like "Brand", "Cloud" and "Market".
    MediaSPIP is designed to facilitate the sharing of creative media online, while allowing authors to retain complete control of their work.
    MediaSPIP aims to be accessible to as many people as possible and development is based on expanding the (...)

  • La file d’attente de SPIPmotion

    28 novembre 2010, par

    Une file d’attente stockée dans la base de donnée
    Lors de son installation, SPIPmotion crée une nouvelle table dans la base de donnée intitulée spip_spipmotion_attentes.
    Cette nouvelle table est constituée des champs suivants : id_spipmotion_attente, l’identifiant numérique unique de la tâche à traiter ; id_document, l’identifiant numérique du document original à encoder ; id_objet l’identifiant unique de l’objet auquel le document encodé devra être attaché automatiquement ; objet, le type d’objet auquel (...)

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

    18 février 2011, par

    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.

Sur d’autres sites (6503)

  • How to use Visual Studio Compiled libs with MSYS pkg-config

    18 août 2017, par maxhap

    First a bit of background.

    I’m trying to compile ffmpeg on windows with the libass extensions/configuration option.

    Using the visual studio project libass-msvc I built libass using Visual Studio as a static lib.

    I then installed MinGW with MSYS and pkg-config. Following the instructions on the ffmpeg MSVC installation guide I configured the environment to build with the MSVC linker and to build in x64.

    When I try to configure libass for compilation using ./configure —enable-libass —toolchain=msvc I get the following error in the log file :

    File not found ass/ass.h
    pkg-config can not find libass

    I have tried the following to fix this.

    1. Create a .pc file for libass and add this to the PKG_CONFIG_PATH environment variable. See file content below. (After doing this pkg-config libass —version prints 0.81, not the right version number but at least something.)

    2. Copy libass .h files into a MinGW/include/ass folder and the .lib file into the MinGW/libs folder.

    3. Add libass include and bin folders to PATH environment variable

    4. Download libass and dependencies source then try to build it using MSYS with MSVC compiler. My aim here was to be able to use "make install" and let MinGW install libass to the correct locations. After hours of trying to fix linker errors, I abandoned this idea as some of the libass dependencies make files only work with the GCC GNU compiler.

    5. Compile libass with GCC GNU using MinGW make/make install then try and install libass using the GNU libs. Again this led to linker errors (I know this was a bad idea but was worth a try).

    6. Tried using extra lib and include build configuration options —extra-cflags="ffmpeg-dir/extra/include" \
      — extra-ldflags="ffmped-dir/extra/ffmpeg_build/lib" then adding the libs and .h files into those locations

    .pc file

    libass.pc:
    prefix=/MinGW
    includedir=libass-directory/include
    libdir=libass-director/x64/bin/

    Name: libass
    Description: Libass project
    Version: 0.13.7

    I am now completely stuck and out of ideas if anyone could give any insight or suggestions into what I’m doing wrong that would be fantastic.

    Thanks in advanced !

  • config.h : No such file or directory after importing eclipse ndk project in android studio

    25 mai 2016, par Alin

    I have a working project in eclipse that uses ffmpeg. The implementation is like in this tutorial : http://enoent.fr/blog/2014/06/20/compile-ffmpeg-for-android/

    After importing the project into Android Studio 2.1 the only error I got was related to

    android.useDeprecatedNdk=true in my gradle.properties

    When I try to run the project I get the following error :

    config.h: No such file or directory

    on ffmpeg.h

    #ifndef FFMPEG_H
    #define FFMPEG_H

    #include "config.h"

    #include
    #include
    #include
    ....

    My build.gradle has :

    ndk {
               moduleName "videokit"
           }

    What should I do to fix the problem ?

    LE : Possible solution :
    - I created the jniLibs folder and added the .so file from eclipse lib’s folder and it seem to work...

  • avcodec/ituh263dec : Make the condition for the studio slice start code match between...

    14 septembre 2019, par Michael Niedermayer
    avcodec/ituh263dec : Make the condition for the studio slice start code match between ff_h263_resync() and ff_mpeg4_decode_studio_slice_header()
    

    If they mismatch an infinite loop can occur
    Fixes : Timeout (infinite loop)
    Fixes : 17043/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_MPEG4_fuzzer-5695051748868096

    Found-by : continuous fuzzing process https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
    Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>

    • [DH] libavcodec/ituh263dec.c