Recherche avancée

Médias (0)

Mot : - Tags -/organisation

Aucun média correspondant à vos critères n’est disponible sur le site.

Autres articles (56)

  • L’espace de configuration de MediaSPIP

    29 novembre 2010, par

    L’espace de configuration de MediaSPIP est réservé aux administrateurs. Un lien de menu "administrer" est généralement affiché en haut de la page [1].
    Il permet de configurer finement votre site.
    La navigation de cet espace de configuration est divisé en trois parties : la configuration générale du site qui permet notamment de modifier : les informations principales concernant le site (...)

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

  • Récupération d’informations sur le site maître à l’installation d’une instance

    26 novembre 2010, par

    Utilité
    Sur le site principal, une instance de mutualisation est définie par plusieurs choses : Les données dans la table spip_mutus ; Son logo ; Son auteur principal (id_admin dans la table spip_mutus correspondant à un id_auteur de la table spip_auteurs)qui sera le seul à pouvoir créer définitivement l’instance de mutualisation ;
    Il peut donc être tout à fait judicieux de vouloir récupérer certaines de ces informations afin de compléter l’installation d’une instance pour, par exemple : récupérer le (...)

Sur d’autres sites (5831)

  • lavf : Use wchar functions for filenames on windows for mkdir/rmdir/rename/unlink

    17 novembre 2014, par Martin Storsjö
    lavf : Use wchar functions for filenames on windows for mkdir/rmdir/rename/unlink
    

    This makes sure that the internal utf8 path names are handled
    properly - the normal file handling functions assume path names
    are in the native codepage, which isn’t utf8.

    This assumes that the tools outside of lavf don’t use the mkdir
    definition. (The tools don’t do the same reading of command line
    parameters as wchar either - they probably won’t handle all possible
    unicode file parameters properly, but at least work more predictably
    if no utf8/wchar conversion is involved.)

    This is moved further down in os_support.h, since windows.h shouldn’t
    be included before winsock2.h, while io.h needs to be included before
    the manual defines for lseek functions.

    Signed-off-by : Martin Storsjö <martin@martin.st>

    • [DBH] libavformat/internal.h
    • [DBH] libavformat/os_support.h
  • Can I Config FFMEG-2.4.3 to use in android windows 64 ?

    13 novembre 2014, par Ngo Ky

    I want to build ffmpeg-2.4.3 (lastest c lib) to use it on android for managing video.
    my OS is windows 7 Utimate x64
    cywin64 in directory : C :/cywin64/ have make installed.
    NDK in directory : D :\solfware\Programming\android-ndk-r10c

    i follow toturial form : http://www.roman10.net/how-to-build-ffmpeg-for-android/comment-page-1/
    my project struture like :

    enter image description here

    i create build_android.sh like roman10 as following code :

    # ARMv7+Neon (Cortex-A8)
    # Customizing:
    # 1. Feel free to change ./configure parameters for more features
    # 2. To adapt other ARM variants
    # set $CPU and $OPTIMIZE_CFLAGS
    # call build_one
    ######################################################
    NDK=D:\solfware\Programming\android-ndk-r10c
    PLATFORM=$NDK/platforms/android-8/arch-arm/
    PREBUILT=$NDK/prebuilt/windows-x86_64
    function build_one
    {
    ./configure --target-os=linux \
       --prefix=$PREFIX \
       --enable-cross-compile \
       --extra-libs="-lgcc" \
       --arch=arm \
       --cc=$PREBUILT/bin/arm-linux-androideabi-gcc \
       --cross-prefix=$PREBUILT/bin/arm-linux-androideabi- \
       --nm=$PREBUILT/bin/arm-linux-androideabi-nm \
       --sysroot=$PLATFORM \
       --extra-cflags=" -O3 -fpic -DANDROID -DHAVE_SYS_UIO_H=1 -Dipv6mr_interface=ipv6mr_ifindex -fasm -Wno-psabi -fno-short-enums -fno-strict-aliasing -finline-limit=300 $OPTIMIZE_CFLAGS " \
       --disable-shared \
       --enable-static \
       --extra-ldflags="-Wl,-rpath-link=$PLATFORM/usr/lib -L$PLATFORM/usr/lib -nostdlib -lc -lm -ldl -llog" \
       --disable-everything \
       --enable-demuxer=mov \
       --enable-demuxer=h264 \
       --disable-ffplay \
       --enable-protocol=file \
       --enable-avformat \
       --enable-avcodec \
       --enable-decoder=rawvideo \
       --enable-decoder=mjpeg \
       --enable-decoder=h263 \
       --enable-decoder=mpeg4 \
       --enable-decoder=h264 \
       --enable-parser=h264 \
       --disable-network \
       --enable-zlib \
       --disable-avfilter \
       --disable-avdevice \
       $ADDITIONAL_CONFIGURE_FLAG

    make clean
    make  -j4 install
    $PREBUILT/bin/arm-linux-androideabi-ar d libavcodec/libavcodec.a inverse.o
    $PREBUILT/bin/arm-linux-androideabi-ld -rpath-link=$PLATFORM/usr/lib -L$PLATFORM/usr/lib  -soname libffmpeg.so -shared -nostdlib  -z,noexecstack -Bsymbolic --whole-archive --no-undefined -o $PREFIX/libffmpeg.so libavcodec/libavcodec.a libavformat/libavformat.a libavutil/libavutil.a libswscale/libswscale.a -lc -lm -lz -ldl -llog  --warn-once  --dynamic-linker=/system/bin/linker $PREBUILT/lib/gcc/arm-linux-androideabi/4.4.3/libgcc.a
    }

    #arm v6
    #CPU=armv6
    #OPTIMIZE_CFLAGS="-marm -march=$CPU"
    #PREFIX=./android/$CPU
    #ADDITIONAL_CONFIGURE_FLAG=
    #build_one

    #arm v7vfpv3
    CPU=armv7-a
    OPTIMIZE_CFLAGS="-mfloat-abi=softfp -mfpu=vfpv3-d16 -marm -march=$CPU "
    PREFIX=./android/$CPU
    ADDITIONAL_CONFIGURE_FLAG=
    build_one

    #arm v7vfp
    #CPU=armv7-a
    #OPTIMIZE_CFLAGS="-mfloat-abi=softfp -mfpu=vfp -marm -march=$CPU "
    #PREFIX=./android/$CPU-vfp
    #ADDITIONAL_CONFIGURE_FLAG=
    #build_one

    #arm v7n
    #CPU=armv7-a
    #OPTIMIZE_CFLAGS="-mfloat-abi=softfp -mfpu=neon -marm -march=$CPU -mtune=cortex-a8"
    #PREFIX=./android/$CPU
    #ADDITIONAL_CONFIGURE_FLAG=--enable-neon
    #build_one

    #arm v6+vfp
    #CPU=armv6
    #OPTIMIZE_CFLAGS="-DCMP_HAVE_VFP -mfloat-abi=softfp -mfpu=vfp -marm -march=$CPU"
    #PREFIX=./android/${CPU}_vfp
    #ADDITIONAL_CONFIGURE_FLAG=
    #build_one

    i have set my path like above
    I built it in Eclipse Everything is ok. but when i ran it in Android it crashed Unfortunately.
    I found the errors in Logcat monitor :

    E/AndroidRuntime(1931) : java.lang.UnsatisfiedLinkError : Couldn’t load avcodec-55 from loader dalvik.system.PathClassLoader[DexPathList [1]] : findLibrary returned null

    E/AndroidRuntime(1931) : at java.lang.Runtime.loadLibrary(Runtime.java:358)

    In my activity i just call add Library from C preference like :

    static {
           //System.loadLibrary("avutil-52");
           System.loadLibrary("avcodec-55");
           System.loadLibrary("avformat-55");
           System.loadLibrary("swscale-2");
           System.loadLibrary("tutorial02");
       }

    i check in DDMS in app-lib there is no existing Library in there.

    The question is : Can i can compile the ffmpeg on windows ?
    if ok. how can i config build_android.sh to point to Android $PREBUILT

    PLATFORM=$NDK/platforms/android-8/arch-arm/
       PREBUILT=$NDK/prebuilt/windows-x86_64
       function build_one
       {
       ./configure --target-os=linux \
           --prefix=$PREFIX \
           --enable-cross-compile \
           --extra-libs="-lgcc" \
           --arch=arm \
           --cc=$PREBUILT/bin/arm-linux-androideabi-gcc \
           --cross-prefix=$PREBUILT/bin/arm-linux-androideabi- \
           --nm=$PREBUILT/bin/arm-linux-androideabi-nm \
           --sysroot=$PLATFORM \
           --extra-cflags=" -O3 -fpic -DANDROID -DHAVE_SYS_UIO_H=1 -Dipv6mr_interface=ipv6mr_ifindex -fasm -Wno-psabi -fno-short-enums -fno-strict-aliasing -finline-limit=300 $OPTIMIZE_CFLAGS " \
           --disable-shared \

    i found that in $NDK/prebuilt/windows-x86_64/bin did not exist arm-linux-androideabi-gcc\
    How can i config to be suitable to run on windows ?

    Thank in advanced

  • avcodec/vorbisenc : Use fdsp for applying windows

    30 mai 2017, par Tyler Jones
    avcodec/vorbisenc : Use fdsp for applying windows
    

    Using fdsp improves readability and allows using architecture-specific
    optimizations.

    Signed-off-by : Tyler Jones <tdjones879@gmail.com>

    • [DH] libavcodec/vorbisenc.c