Recherche avancée

Médias (2)

Mot : - Tags -/documentation

Autres articles (33)

  • Contribute to translation

    13 avril 2011

    You can help us to improve the language used in the software interface to make MediaSPIP more accessible and user-friendly. You can also translate the interface into any language that allows it to spread to new linguistic communities.
    To do this, we use the translation interface of SPIP where the all the language modules of MediaSPIP are available. Just subscribe to the mailing list and request further informantion on translation.
    MediaSPIP is currently available in French and English (...)

  • Les tâches Cron régulières de la ferme

    1er décembre 2010, par

    La gestion de la ferme passe par l’exécution à intervalle régulier de plusieurs tâches répétitives dites Cron.
    Le super Cron (gestion_mutu_super_cron)
    Cette tâche, planifiée chaque minute, a pour simple effet d’appeler le Cron de l’ensemble des instances de la mutualisation régulièrement. Couplée avec un Cron système sur le site central de la mutualisation, cela permet de simplement générer des visites régulières sur les différents sites et éviter que les tâches des sites peu visités soient trop (...)

  • (Dés)Activation de fonctionnalités (plugins)

    18 février 2011, par

    Pour gérer l’ajout et la suppression de fonctionnalités supplémentaires (ou plugins), MediaSPIP utilise à partir de la version 0.2 SVP.
    SVP permet l’activation facile de plugins depuis l’espace de configuration de MediaSPIP.
    Pour y accéder, il suffit de se rendre dans l’espace de configuration puis de se rendre sur la page "Gestion des plugins".
    MediaSPIP est fourni par défaut avec l’ensemble des plugins dits "compatibles", ils ont été testés et intégrés afin de fonctionner parfaitement avec chaque (...)

Sur d’autres sites (7950)

  • What is the difference between ffmpeg -thread and ffmpeg-mt ?

    7 novembre 2018, par S B

    Post ffmpeg-mt’s merge with ffmpeg...

    March 21, 2011

    Today FFmpeg-mt, the multithreaded decoding branch, has been merged into FFmpeg. This has been a long awaited merge, and we would like to thank Alexander Strange for his patience and hard work.

    ... what is to be expected of ffmpeg -thread usage ? Is this an under-the-hood transition or are ffmpeg users supposed to move their code to ffmpeg-mt to leverage multi-cores ?

  • On ALAC’s Open Sourcing

    1er novembre 2011, par Multimedia Mike — Codec Technology

    Apple open sourced their lossless audio codec last week. Pretty awesome ! I have a theory that, given enough time, absolutely every codec will be open source in one way or another.

    I know I shouldn’t bother reading internet conversation around any news related to multimedia technology. And if I do read it, I shouldn’t waste any effort getting annoyed about them. But here are some general corrections :

    • ALAC is not in the same league as — nor is it a suitable replacement for — MP3/AAC/Vorbis or any other commonly used perceptual audio codec. It’s not a matter of better or worse ; they’re just different families of codecs designed for different purposes.
    • Apple open sourced ALAC, not AAC– easy mistake, though there’s nothing to ‘open source’ about AAC (though people can, and will, argue about its absolute ‘open-ness’).
    • There’s not much technical room to argue between ALAC and FLAC, the leading open source lossless audio compressor. Both perform similarly in terms of codec speeds (screamingly fast) and compression efficiency (results vary slightly depending on source material).
    • Perhaps the most frustrating facet is the blithe ignorance about ALAC’s current open source status. While this event simply added an official “open source” status to the codec, ALAC has effectively been open source for a very long time. According to my notes, the ALAC decoding algorithm was reverse engineered in 2005 and added into FFmpeg in March of the same year. Then in 2008, Google — through their Summer of Code program — sponsored an open source ALAC encoder.

    From the multimedia-savvy who are versed in these concepts, the conversation revolves around which would win in a fight, ALAC or FLAC ? And who between Apple and FFmpeg/Libav has a faster ALAC decoder ? The faster and more efficient ALAC encoder ? I contend that these issues don’t really matter. If you have any experience working with lossless audio encoders, you know that they tend to be ridiculously fast to both encode and decode and that many different lossless codecs compress at roughly the same ratios.

    As for which encoder is the fastest : use whatever encoder is handiest and most familiar, either iTunes or FFmpeg/Libav.

    As for whether to use FLAC or ALAC — if you’ve already been using one or the other for years, keep on using it. Support isn’t going to vanish. If you’re deciding which to use for a new project, again, perhaps choose based on software you’re already familiar with. Also, consider hardware support– ALAC enjoys iPod support, FLAC is probably better supported in a variety of non-iPod devices, though that may change going forward due to this open sourcing event.

    For my part, I’m just ecstatic that the question of moral superiority based on open source status has been removed from the equation.

    Code-wise, I’m interested in studying the official ALAC code to see if it has any corner-case modes that the existing open source decoders don’t yet account for. The source makes mention of multichannel (i.e., greater than stereo) configurations, but I don’t know if that’s in FFmpeg/Libav.

  • Android-NDK building using the Bambuser source

    13 juillet 2015, par Kenny910

    I am trying to use the FFmpeg source provided by the Bambuser.

    However, I am fail to build the files

    I get the following error :

    arm-linux-androideabi-gcc is unable to create an executable file.
    C compiler test failed.

    I have already set the NDK path to /home/android-ndk but still get this error

    And I am using Android-NDK-r5b

    can anyone help ? THX

    Here is my build.sh

    #!/bin/bash

    if [ "$NDK" = "" ]; then
       echo NDK variable not set, assuming ${HOME}/android-ndk
       export NDK=${HOME}/android-ndk
    fi

    SYSROOT=$NDK/platforms/android-3/arch-arm
    # Expand the prebuilt/* path into the correct one
    TOOLCHAIN=`echo $NDK/toolchains/arm-linux-androideabi-4.4.3/prebuilt/windows`
    export PATH=$TOOLCHAIN/bin:$PATH

    rm -rf build/ffmpeg
    mkdir -p build/ffmpeg
    cd ffmpeg

    # Don't build any neon version for now
    for version in armv5te armv7a; do

       DEST=../build/ffmpeg
       FLAGS="--target-os=linux --cross-prefix=arm-linux-androideabi- --arch=arm"
       FLAGS="$FLAGS --sysroot=$SYSROOT"
       FLAGS="$FLAGS --soname-prefix=/data/data/com.streaming.realive/lib/"
       FLAGS="$FLAGS --enable-shared --disable-symver"
       FLAGS="$FLAGS --enable-small --optimization-flags=-O2"
       FLAGS="$FLAGS --enable-encoder=mpeg4 --enable-decoder=mpeg4"
       FLAGS="$FLAGS --enable-encoder=mpeg2video --enable-encoder=nellymoser"
       FLAGS="$FLAGS --enable-protocol=rtp --enable-protocol=rtmp"
       FLAGS="$FLAGS --enable-protocol=http --enable-protocol=tcp --enable-protocol=udp"
       FLAGS="$FLAGS --enable-protocol=file"

       case "$version" in
           neon)
               EXTRA_CFLAGS="-march=armv7-a -mfloat-abi=softfp -mfpu=neon"
               EXTRA_LDFLAGS="-Wl,--fix-cortex-a8"
               # Runtime choosing neon vs non-neon requires
               # renamed files
               ABI="armeabi-v7a"
               ;;
           armv7a)
               EXTRA_CFLAGS="-march=armv7-a -mfloat-abi=softfp"
               EXTRA_LDFLAGS=""
               ABI="armeabi-v7a"
               ;;
           *)
               EXTRA_CFLAGS=""
               EXTRA_LDFLAGS=""
               ABI="armeabi"
               ;;
       esac
       DEST="$DEST/$ABI"
       FLAGS="$FLAGS --prefix=$DEST"

       mkdir -p $DEST
       echo $FLAGS --extra-cflags="$EXTRA_CFLAGS" --extra-ldflags="$EXTRA_LDFLAGS" > $DEST/info.txt
       ./configure $FLAGS --extra-cflags="$EXTRA_CFLAGS" --extra-ldflags="$EXTRA_LDFLAGS" | tee $DEST/configuration.txt
       [ $PIPESTATUS == 0 ] || exit 1
       make clean
       make -j4 || exit 1
       make install || exit 1

    done