Recherche avancée

Médias (1)

Mot : - Tags -/artwork

Autres articles (64)

  • Soumettre améliorations et plugins supplémentaires

    10 avril 2011

    Si vous avez développé une nouvelle extension permettant d’ajouter une ou plusieurs fonctionnalités utiles à MediaSPIP, faites le nous savoir et son intégration dans la distribution officielle sera envisagée.
    Vous pouvez utiliser la liste de discussion de développement afin de le faire savoir ou demander de l’aide quant à la réalisation de ce plugin. MediaSPIP étant basé sur SPIP, il est également possible d’utiliser le liste de discussion SPIP-zone de SPIP pour (...)

  • HTML5 audio and video support

    13 avril 2011, par

    MediaSPIP uses HTML5 video and audio tags to play multimedia files, taking advantage of the latest W3C innovations supported by modern browsers.
    The MediaSPIP player used has been created specifically for MediaSPIP and can be easily adapted to fit in with a specific theme.
    For older browsers the Flowplayer flash fallback is used.
    MediaSPIP allows for media playback on major mobile platforms with the above (...)

  • Support audio et vidéo HTML5

    10 avril 2011

    MediaSPIP utilise les balises HTML5 video et audio pour la lecture de documents multimedia en profitant des dernières innovations du W3C supportées par les navigateurs modernes.
    Pour les navigateurs plus anciens, le lecteur flash Flowplayer est utilisé.
    Le lecteur HTML5 utilisé a été spécifiquement créé pour MediaSPIP : il est complètement modifiable graphiquement pour correspondre à un thème choisi.
    Ces technologies permettent de distribuer vidéo et son à la fois sur des ordinateurs conventionnels (...)

Sur d’autres sites (7412)

  • Unable to execute command prompt command from python

    30 octobre 2023, par StudentProgrammer

    Unable to execute a ffmpeg command directly from python, however it works fine if used within the command prompt.

    


     os.system("cmd /c ffmpeg -i video.mp4 -i sound.mp3 -c:v copy -filter_complex '[1:a] adelay=3000|2000 [delayed]; [0:a] [delayed] amix [out]' -map 0:v -map '[out]' video2.mp4")



 '2000' is not recognized as an internal or external command,
 operable program or batch file.


    


    I know it has something to do with the pipe |. I've looked at documentation to make subprocess work with pipes but without success.

    


  • Building x264 on a Mac for android “No working C compiler found”

    20 novembre 2015, par LostPuppy

    I am trying to build x264 and eventually use it to build ffmpeg the following is my script :

    #!/bin/bash

    NDK="/Users/account/Documents/FFmpeg/android-ndk-r10e"
    TOOL_DIR_ARM="/Users/account/Documents/FFmpeg/android-ndk-r10e/sources/ffmpeg-2.8.2/my-android-toolchain"
    SYSROOT=$NDK/platforms/platforms/android-21/arch-arm
    echo "removing tool chain directory if it exists"
    rm -r $TOOL_DIR_ARM

    $NDK/build/tools/make-standalone-toolchain.sh \
       --platform=android-21 \
       --arch=arm \
       --install-dir=$TOOL_DIR_ARM \
       --toolchain=arm-linux-androideabi-clang3.6\
       --llvm-version=3.6 \
       --system=darwin-x86_64

    if [ -d $SYSROOT ]; then
       echo "$SYSROOT is a valid directory"
    fi

    function build_x264
    {
    cd x264

    # another build for phone
    ./configure \
    --cross-prefix=arm-linux-androideabi- \
    --sysroot=$SYSROOT \
    --host=arm-linux \
    --enable-static \
    --enable-pic \
    --disable-cli

    make -j4
    make install

    cd ../
    }


    function build_one
    {
    cd

    # another build for phone
    ./configure \
    --sysroot=$SYSROOT \
    --target-os=linux \
    --arch=arm \
    --cross-prefix=$TOOL_DIR_ARM/bin/arm-linux-androideabi- \
    --cc=$TOOL_DIR_ARM/bin/clang \
    --enable-cross-compile \
    --enable-encoder=mpeg4 \
    --enable-pthreads \
    --enable-gpl \
    --enable-libx264 \
    --enable-pic \
    --extra-cflags='-I/usr/local/include' \
    --extra-ldflags='-L/usr/local/lib'

    make clean
    make -j4
    make install

    }
    echo "Building x_264 library"
    build_x264
    echo "Building FFmpeg"
    build_one

    I get an error saying

    No working C compiler found.
    Makefile:3: config.mak: No such file or directory

    The following is the output from the config.log file

    checking for -mdynamic-no-pic... yes
    checking for -arch x86_64... yes
    x264 configure script

    checking whether gcc works... yes
    checking whether gcc supports for( int i = 0; i < 9; i++ ); with -std=gnu99... yes
    checking for -mpreferred-stack-boundary=5... no
    Failed commandline was:
    --------------------------------------------------
    gcc conftest.c -m64 -Qunused-arguments -Wall -I. -I$(SRCPATH) -mdynamic-no-pic -arch x86_64 -std=gnu99  -mpreferred-stack-boundary=5  -m64  -lm -arch x86_64$
    clang: error: unknown argument: '-mpreferred-stack-boundary=5'
    --------------------------------------------------
    Failed program was:
    --------------------------------------------------
    int main (void) {  return 0; }
    --------------------------------------------------
    checking whether yasm supports vpmovzxwd ymm0, xmm0... yes

    Solutions that I tried :

    I made sure I have a working GCC

    I have the update to date version of clang

    I have the update to date version of LLVM

  • Building x264 on a Mac for android “No working C compiler found”

    20 novembre 2015, par LostPuppy

    I am trying to build x264 and eventually use it to build ffmpeg the following is my script :

    #!/bin/bash

    NDK="/Users/account/Documents/FFmpeg/android-ndk-r10e"
    TOOL_DIR_ARM="/Users/account/Documents/FFmpeg/android-ndk-r10e/sources/ffmpeg-2.8.2/my-android-toolchain"
    SYSROOT=$NDK/platforms/platforms/android-21/arch-arm
    echo "removing tool chain directory if it exists"
    rm -r $TOOL_DIR_ARM

    $NDK/build/tools/make-standalone-toolchain.sh \
       --platform=android-21 \
       --arch=arm \
       --install-dir=$TOOL_DIR_ARM \
       --toolchain=arm-linux-androideabi-clang3.6\
       --llvm-version=3.6 \
       --system=darwin-x86_64

    if [ -d $SYSROOT ]; then
       echo "$SYSROOT is a valid directory"
    fi

    function build_x264
    {
    cd x264

    # another build for phone
    ./configure \
    --cross-prefix=arm-linux-androideabi- \
    --sysroot=$SYSROOT \
    --host=arm-linux \
    --enable-static \
    --enable-pic \
    --disable-cli

    make -j4
    make install

    cd ../
    }


    function build_one
    {
    cd

    # another build for phone
    ./configure \
    --sysroot=$SYSROOT \
    --target-os=linux \
    --arch=arm \
    --cross-prefix=$TOOL_DIR_ARM/bin/arm-linux-androideabi- \
    --cc=$TOOL_DIR_ARM/bin/clang \
    --enable-cross-compile \
    --enable-encoder=mpeg4 \
    --enable-pthreads \
    --enable-gpl \
    --enable-libx264 \
    --enable-pic \
    --extra-cflags='-I/usr/local/include' \
    --extra-ldflags='-L/usr/local/lib'

    make clean
    make -j4
    make install

    }
    echo "Building x_264 library"
    build_x264
    echo "Building FFmpeg"
    build_one

    I get an error saying

    No working C compiler found.
    Makefile:3: config.mak: No such file or directory

    The following is the output from the config.log file

    checking for -mdynamic-no-pic... yes
    checking for -arch x86_64... yes
    x264 configure script

    checking whether gcc works... yes
    checking whether gcc supports for( int i = 0; i < 9; i++ ); with -std=gnu99... yes
    checking for -mpreferred-stack-boundary=5... no
    Failed commandline was:
    --------------------------------------------------
    gcc conftest.c -m64 -Qunused-arguments -Wall -I. -I$(SRCPATH) -mdynamic-no-pic -arch x86_64 -std=gnu99  -mpreferred-stack-boundary=5  -m64  -lm -arch x86_64$
    clang: error: unknown argument: '-mpreferred-stack-boundary=5'
    --------------------------------------------------
    Failed program was:
    --------------------------------------------------
    int main (void) {  return 0; }
    --------------------------------------------------
    checking whether yasm supports vpmovzxwd ymm0, xmm0... yes

    Solutions that I tried :

    I made sure I have a working GCC

    I have the update to date version of clang

    I have the update to date version of LLVM