Recherche avancée

Médias (91)

Autres articles (111)

  • Les formats acceptés

    28 janvier 2010, par

    Les commandes suivantes permettent d’avoir des informations sur les formats et codecs gérés par l’installation local de ffmpeg :
    ffmpeg -codecs ffmpeg -formats
    Les format videos acceptés en entrée
    Cette liste est non exhaustive, elle met en exergue les principaux formats utilisés : h264 : H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 m4v : raw MPEG-4 video format flv : Flash Video (FLV) / Sorenson Spark / Sorenson H.263 Theora wmv :
    Les formats vidéos de sortie possibles
    Dans un premier temps on (...)

  • Ajouter notes et légendes aux images

    7 février 2011, par

    Pour pouvoir ajouter notes et légendes aux images, la première étape est d’installer le plugin "Légendes".
    Une fois le plugin activé, vous pouvez le configurer dans l’espace de configuration afin de modifier les droits de création / modification et de suppression des notes. Par défaut seuls les administrateurs du site peuvent ajouter des notes aux images.
    Modification lors de l’ajout d’un média
    Lors de l’ajout d’un média de type "image" un nouveau bouton apparait au dessus de la prévisualisation (...)

  • Script d’installation automatique de MediaSPIP

    25 avril 2011, par

    Afin de palier aux difficultés d’installation dues principalement aux dépendances logicielles coté serveur, un script d’installation "tout en un" en bash a été créé afin de faciliter cette étape sur un serveur doté d’une distribution Linux compatible.
    Vous devez bénéficier d’un accès SSH à votre serveur et d’un compte "root" afin de l’utiliser, ce qui permettra d’installer les dépendances. Contactez votre hébergeur si vous ne disposez pas de cela.
    La documentation de l’utilisation du script d’installation (...)

Sur d’autres sites (4269)

  • Android FFMPEG Build with librtmp

    20 décembre 2013, par Dan Turner

    I have been pulling my hair out trying to compile FFMPEG for Android with librtmp enabled. I have successfully built FFMPEG using the Guardian Project here, but it doesn't have librtmp support. The only answer I have found to this issue is on a previous Stack Overflow question (HERE), but it doesn't want to work for me.

    At the moment, I have the cross-compiled librtmp.so.0 file from the official rtmpdump android build in an rtmpdump/librtmp folder sitting in the android-ffmpeg folder. An extract from my configure_ffmpeg.sh file reads as follows :

    ./configure \
    $DEBUG_FLAG \
    --arch=arm \
    --cpu=cortex-a8 \
    --target-os=linux \
    --enable-runtime-cpudetect \
    --prefix=$prefix \
    --enable-pic \
    --disable-shared \
    --enable-static \
    --cross-prefix=$NDK_TOOLCHAIN_BASE/bin/$NDK_ABI-linux-androideabi- \
    --sysroot="$NDK_SYSROOT" \
    --extra-cflags="-I../x264 -mfloat-abi=softfp -mfpu=neon" \
    --extra-ldflags="-L../x264" \
    --extra-cflags="-I/home/dan/android-ffmpeg/rtmpdump" \
    --extra-ldflags="-L/home/dan/android-ffmpeg/rtmpdump -lrtmp"
    \

    --enable-version3 \
    --enable-gpl \
    \
    --disable-doc \
    --enable-yasm \
    \
    --enable-decoders \
    --enable-encoders \
    --enable-muxers \
    --enable-demuxers \
    --enable-parsers \
    --enable-protocols \
    --enable-filters \
    --enable-avresample \
    --enable-libfreetype \
    \
    --disable-indevs \
    --enable-indev=lavfi \
    --disable-outdevs \
    \
    --enable-hwaccels \
    \
    --enable-ffmpeg \
    --disable-ffplay \
    --disable-ffprobe \
    --enable-ffserver \
    --enable-network \
    \
    --enable-libx264 \
    --enable-zlib \
    --enable-librtmp \

    When I try to compile this, it eventually displays an error and my FFMPEG config.log file tells me that it can't find -lrtmp. I'm positive I'm directing it to the right directory... does anyone have any ideas ?

    Regards

    Dan

  • Is it okay to execute ffmpeg and do not use their library ?

    18 juillet 2017, par Michael Pravilov

    I need to extract audio from video and save it. FFmpeg has command for this purpose. I wonder if it is a right way to execute ffmpeg from my code and not to write code with their API functions.

    The lack of this approach is that I use Qt Framework and need cross-platform application. Sometimes (especially in windows, because PATH variable doesn’t set up automatically so call ffmpeg won’t work) a user will need to indicate path to executable file to run in command line.

    So both variants are possible to realize, but which is the best and correct one ?

    I don’t really want to use their API because it is not so easy to understand and will take time to write my own code.

    Thanks for any advice !

  • How to solve bad instruction `vadd.i16 q0,q0,q0' when attempting to check gcc for neon instruction

    6 juillet 2012, par newentry
    Checking  gcc supports failed for neon instruction vadd.i16 q0,q0,q0
       test.c

       int main ()
       {
        __asm__("vadd.i16 q0, q0, q0"); return 0;
       }

       arm-linux-androideabi-gcc test.c
       /tmp/ccfc8m0G.s: Assembler messages:
       /tmp/ccfc8m0G.s:24: Error: bad instruction `vadd.i16 q0,q0,q0'

    Tried with flags -mcpu=cortex-a8 -mfpu=neon but stil no success

    Above code was used to test gcc support for neon instruction.

    Actually i am trying to build x264 with NEON support for ARM platformAfter running configure script
    x264 config log file contains

    Command line options : "—cross-prefix=arm-linux-androideabi-" "—enable-pic" "—extra- cflags=-mcpu=cortex-a8" "—host=arm-linux"

    checking whether arm-linux-androideabi-gcc works... yes
    checking whether arm-linux-androideabi-gcc supports for( int i = 0; i < 9; i++ ); with -std=gnu99... yes
    checking whether arm-linux-androideabi-gcc supports __asm__("rev ip, ip");... yes
    checking whether arm-linux-androideabi-gcc supports __asm__("movt r0, #0");... yes
    checking whether arm-linux-androideabi-gcc supports __asm__("vadd.i16 q0, q0, q0");... no

    arm-linux-androideabi-gcc conftest.c  -Wall -I. -I$(SRCPATH) -mcpu=cortex-a8 -std=gnu99    -lm -o conftest
    E:\cygwin\tmp\ccVtVI1i.s: Assembler messages:
    E:\cygwin\tmp\ccVtVI1i.s:24: Error: bad instruction `vadd.i16 q0,q0,q0'
    --------------------------------------------------
    Failed program was:
    --------------------------------------------------
    int main () { __asm__("vadd.i16 q0, q0, q0"); return 0; }
    --------------------------------------------------


    config.h contains

    #define HAVE_MALLOC_H 1
    #define HAVE_ARMV6 1
    #define HAVE_ARMV6T2 1
    #define ARCH_ARM 1
    #define SYS_LINUX 1
    #define HAVE_VECTOREXT 1
    #define fseek fseeko
    #define ftell ftello
    #define HAVE_GPL 1
    #define HAVE_INTERLACED 1
    #define HAVE_ALTIVEC 0
    #define HAVE_ALTIVEC_H 0
    #define HAVE_MMX 0
    #define HAVE_NEON 0
    #define HAVE_BEOSTHREAD 0
    #define HAVE_POSIXTHREAD 0
    #define HAVE_WIN32THREAD 0
    #define HAVE_THREAD 0
    #define HAVE_LOG2F 0
    #define HAVE_VISUALIZE 0
    #define HAVE_SWSCALE 0
    #define HAVE_LAVF 0
    #define HAVE_FFMS 0
    #define HAVE_GPAC 0
    #define HAVE_GF_MALLOC 0
    #define HAVE_AVS 0
    #define HAVE_CPU_COUNT 0


    Running make command build x264 static lib  based on above config.h which contains HAVE_NEON 0


    **Compiler Version**



    arm-linux-androideabi-gcc -v
    Using built-in specs.
    Target: arm-linux-androideabi
    Configured with: /tmp/ndk-digit/src/build/../gcc/gcc-4.4.3/configure --prefix=/usr/local/google/digit/repo/opensource/ndk/toolchains/arm-linux-androideabi-4.4.3/prebuilt/windows --target=arm-linux-androideabi --host=i586-mingw32msvc --build=x86_64-linux-gnu --with-gnu-as --with-gnu-ld --enable-languages=c,c++ --with-gmp=/tmp/ndk-digit/build/toolchain/temp-install --with-mpfr=/tmp/ndk-digit/build/toolchain/temp-install --disable-libssp --enable-threads --disable-nls --disable-libmudflap --disable
    -libgomp --disable-libstdc__-v3 --disable-sjlj-exceptions --disable-shared --disable-tls --with-float=soft --with-fpu=vfp --with-arch=armv5te --enable-target-optspace --enable-initfini-array --disable-nls --prefix=/usr/local/google/digit/repo/opensource/ndk/toolchains/arm-linux-androideabi-4.4.3/prebuilt/windows --with-sysroot=/usr/local/google/digit/repo/opensource/ndk/toolchains/arm-linux-androideabi-4.4.3/prebuilt/windows/sysroot --with-binutils-version=2.20.1 --with-mpfr-version=2.4.1 --with
    -gmp-version=4.2.4 --with-gcc-version=4.4.3 --with-gdb-version=6.6 --with-arch=armv5te --program-transform-name='s,^,arm-linux-androideabi-,'
    Thread model: posix
    gcc version 4.4.3 (GCC)    

    Goal is to utilize neon enabled ARM processor to boost x264 encoder performance...