Recherche avancée

Médias (1)

Mot : - Tags -/école

Autres articles (48)

  • Gestion générale des documents

    13 mai 2011, par

    MédiaSPIP ne modifie jamais le document original mis en ligne.
    Pour chaque document mis en ligne il effectue deux opérations successives : la création d’une version supplémentaire qui peut être facilement consultée en ligne tout en laissant l’original téléchargeable dans le cas où le document original ne peut être lu dans un navigateur Internet ; la récupération des métadonnées du document original pour illustrer textuellement le fichier ;
    Les tableaux ci-dessous expliquent ce que peut faire MédiaSPIP (...)

  • Des sites réalisés avec MediaSPIP

    2 mai 2011, par

    Cette page présente quelques-uns des sites fonctionnant sous MediaSPIP.
    Vous pouvez bien entendu ajouter le votre grâce au formulaire en bas de page.

  • 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 (...)

Sur d’autres sites (8056)

  • osx ffmpeg avfoundation audio not in sync

    29 avril 2015, par Chris Whittington

    I’m trying to record my screen audio and video with ffmpeg. I have installed soundflower successfully and setup the correct audio devices. However, when using ffmpeg the audio is sped up and does not keep in sync with the video.

    ffmpeg -f avfoundation -i "1:0" -y out.avi

    I have also tried the following variations.

    ffmpeg -vsync 2 -f avfoundation -i "1:0" -framerate 30 -y out.avi

    ffmpeg -vsync 2 -f avfoundation -i "1:0" -frame_rate 30 -probesize 10M  -y out.avi

    ffmpeg -async 1 -probesize 10M -f avfoundation -i "1:0" -r 15  -y out.avi

    ffmpeg -async 15 -f avfoundation -i "1:0" -r 15  -y out.avi

    I’m using ffmpeg version 2.6.2 installed via homebrew.

    If someone has a free solution that isn’t ffmpeg that works well from the command line then i will also accept that. Quicktime screen recording produces very large file sizes so it’s not appropriate.

  • Errors while ffmpeg compiling

    10 mai 2012, par iSun

    I trying to compile ffmpeg through the following script, but I got errors while compiling : (Using windows 7 - android ndk 7rb and cygwin)

    s@s-PC /cygdrive/f/export/ffmpeg-0.8.10
    $ ./setup.sh
    F:/Compiler/android-ndk-r7b/toolchains/arm-linux-androideabi-4.4.3/prebuilt/wind                                                                                                    ows/bin/arm-linux-androideabi-gcc is unable to create an executable file.
    C compiler test failed.

    If you think configure made a mistake, make sure you are using the latest
    version from Git.  If the latest version fails, report the problem to the
    ffmpeg-user@ffmpeg.org mailing list or IRC #ffmpeg on irc.freenode.net.
    Include the log file "config.log" produced by configure as this will help
    solving the problem.
    ./setup.sh: line 48: --extra-cflags=: command not found
    ./setup.sh: line 51: --extra-ldflags=: command not found
    ./setup.sh: line 53: --extra-ldflags=: command not found
    Makefile:1: config.mak: No such file or directory
    libavutil/Makefile:1: libavutil/../config.mak: No such file or directory
    libavutil/../subdir.mak:96: warning: overriding recipe for target `libavutil/'
    libavutil/../subdir.mak:26: warning: ignoring old recipe for target `libavutil/'
    libavutil/../subdir.mak:96: warning: overriding recipe for target `libavutil/'
    libavutil/../subdir.mak:96: warning: ignoring old recipe for target `libavutil/'
    Makefile:239: /tests/fate.mak: No such file or directory
    Makefile:240: /tests/fate2.mak: No such file or directory
    Makefile:242: /tests/fate/aac.mak: No such file or directory
    Makefile:243: /tests/fate/als.mak: No such file or directory
    Makefile:244: /tests/fate/fft.mak: No such file or directory
    Makefile:245: /tests/fate/h264.mak: No such file or directory
    Makefile:246: /tests/fate/mp3.mak: No such file or directory
    Makefile:247: /tests/fate/vorbis.mak: No such file or directory
    Makefile:248: /tests/fate/vp8.mak: No such file or directory
    make: *** No rule to make target `/tests/fate/vp8.mak'.  Stop.
    Makefile:1: config.mak: No such file or directory
    libavutil/Makefile:1: libavutil/../config.mak: No such file or directory
    libavutil/../subdir.mak:96: warning: overriding recipe for target `libavutil/'
    libavutil/../subdir.mak:26: warning: ignoring old recipe for target `libavutil/'
    libavutil/../subdir.mak:96: warning: overriding recipe for target `libavutil/'
    libavutil/../subdir.mak:96: warning: ignoring old recipe for target `libavutil/'
    Makefile:239: /tests/fate.mak: No such file or directory
    Makefile:240: /tests/fate2.mak: No such file or directory
    Makefile:242: /tests/fate/aac.mak: No such file or directory
    Makefile:243: /tests/fate/als.mak: No such file or directory
    Makefile:244: /tests/fate/fft.mak: No such file or directory
    Makefile:245: /tests/fate/h264.mak: No such file or directory
    Makefile:246: /tests/fate/mp3.mak: No such file or directory
    Makefile:247: /tests/fate/vorbis.mak: No such file or directory
    Makefile:248: /tests/fate/vp8.mak: No such file or directory
    make: *** No rule to make target `/tests/fate/vp8.mak'.  Stop.

    Here is my script :

       #!/bin/bash

       export TMPDIR=C:/cygwin/tmp

       ANDROID_API=android-8
       export ANDROID_NDK=F:/Compiler/android-ndk-r7b
       export ANDROID_SDK=F:/Compiler/android-sdk
       SYSROOT=$ANDROID_NDK/platforms/$ANDROID_API/arch-arm
       ANDROID_BIN=$ANDROID_NDK/toolchains/arm-linux-androideabi-4.4.3/prebuilt/windows/bin
       CROSS_COMPILE=${ANDROID_BIN}/arm-linux-androideabi-
       export PATH=$PATH:$ANDROID_SDK/tools:$ANDROID_SDK/platform-tools

       export ARM_ROOT=$ANDROID_NDK
       export ARM_INC=$ARM_ROOT/platforms/android-5/arch-arm/usr/include
       export ARM_LIB=$ARM_ROOT/platforms/android-5/arch-arm/usr/lib
       export LIB_INC=${HOME}/include
       export LIB_LIB=${HOME}/lib


       CFLAGS=" -I$ARM_INC -fPIC -DANDROID -fpic -mthumb-interwork -ffunction-sections -funwind-tables -fstack-protector -fno-short-enums -D__ARM_ARCH_5__ -D__ARM_ARCH_5T__ -D__ARM_ARCH_5E__ -D__ARM_ARCH_5TE__  -Wno-psabi -march=armv5te -mtune=xscale -msoft-float -mthumb -Os -fomit-frame-pointer -fno-strict-aliasing -finline-limit=64 -DANDROID  -Wa,--noexecstack -MMD -MP "
       LDFLAGS=" -nostdlib -Bdynamic  -Wl,--no-undefined -Wl,-z,noexecstack  -Wl,-z,nocopyreloc -Wl,-soname,/system/lib/libz.so -Wl,-rpath-link=$ARM_LIB,-dynamic-linker=/system/bin/linker -L$ARM_LIB -nostdlib $ARM_LIB/crtbegin_dynamic.o $ARM_LIB/crtend_android.o -lc -lm -ldl -lgcc "

       FLAGS="--target-os=linux
       --enable-cross-compile
       --cross-prefix=$CROSS_COMPILE
       --arch=arm --prefix=$HOME
       --disable-shared
       --enable-static
       --extra-libs=-static
       --extra-cflags=--static
       --enable-small
       --disable-asm
       --disable-yasm
       --disable-amd3dnow
       --disable-amd3dnowext
       --disable-mmx
       --disable-mmx2
       --disable-sse
       --disable-ssse3
       --disable-indevs"


       export CFLAGS=$EXTRA_CFLAGS
       export LDFLAGS=$EXTRA_LDFLAGS


    ./configure $FLAGS
    --extra-cflags="$CFLAGS"
    --extra-ldflags="$LDFLAGS" \
    --cc="${CROSS_COMPILE}gcc
    --sysroot=${SYSROOT}"
    --extra-ldflags="$LDFLAGS" \
    --cxx="${CROSS_COMPILE}g++ --sysroot=${SYSROOT}" \
    --nm="${CROSS_COMPILE}nm" \
    --ar="${CROSS_COMPILE}ar"


    make clean
    make -j4 || exit 1
    make install || exit 1

    Any ideas ?

  • sws : move the early return for zero-sized slices higher up

    21 mai 2021, par Anton Khirnov
    sws : move the early return for zero-sized slices higher up
    

    Place it right after the input parameter validation. There is no point
    in performing any setup if the sws_scale() call won't do anything.

    • [DH] libswscale/swscale.c