Recherche avancée

Médias (1)

Mot : - Tags -/MediaSPIP

Autres articles (22)

  • Initialisation de MediaSPIP (préconfiguration)

    20 février 2010, par

    Lors de l’installation de MediaSPIP, celui-ci est préconfiguré pour les usages les plus fréquents.
    Cette préconfiguration est réalisée par un plugin activé par défaut et non désactivable appelé MediaSPIP Init.
    Ce plugin sert à préconfigurer de manière correcte chaque instance de MediaSPIP. Il doit donc être placé dans le dossier plugins-dist/ du site ou de la ferme pour être installé par défaut avant de pouvoir utiliser le site.
    Dans un premier temps il active ou désactive des options de SPIP qui ne le (...)

  • Contribute to documentation

    13 avril 2011

    Documentation is vital to the development of improved technical capabilities.
    MediaSPIP welcomes documentation by users as well as developers - including : critique of existing features and functions articles contributed by developers, administrators, content producers and editors screenshots to illustrate the above translations of existing documentation into other languages
    To contribute, register to the project users’ mailing (...)

  • Liste des distributions compatibles

    26 avril 2011, par

    Le tableau ci-dessous correspond à la liste des distributions Linux compatible avec le script d’installation automatique de MediaSPIP. Nom de la distributionNom de la versionNuméro de version Debian Squeeze 6.x.x Debian Weezy 7.x.x Debian Jessie 8.x.x Ubuntu The Precise Pangolin 12.04 LTS Ubuntu The Trusty Tahr 14.04
    Si vous souhaitez nous aider à améliorer cette liste, vous pouvez nous fournir un accès à une machine dont la distribution n’est pas citée ci-dessus ou nous envoyer le (...)

Sur d’autres sites (3707)

  • Node.js FFMPEG Reporting Progress Architecture

    11 septembre 2018, par munkee

    I’m running a node.js HTTP server which has a video conversion API built using ffmpeg. I am wondering how best to report on the progress of the file conversion to a separate front end. The HTTP server is going to be standalone as its own service, so I would like to be able to render the percentage complete of the conversion to another server with a simple front end. Upon completion of the conversion the file is downloaded automatically.

    My current end point /convert takes a file URL with a .mov extension, downloads the file and runs it through the conversion process to only output Audio. Using response headers I force the browser to download the file once the conversion has ended, I also delete the temporary file once download has completed.

    A full request would look like

    https://www.someurl.com/convert?file=https://www.filetodownload.com/Skating.mov

    I am using the fluent-ffmpeg npm package : https://github.com/fluent-ffmpeg/node-fluent-ffmpeg which serves a "progress" event :

    ffmpeg('/path/to/file.avi')
     .on('progress', function(progress) {
       console.log('Processing: ' + progress.percent + '% done');
     });

    I am thinking of emitting the progress.percent information on to a separate endpoint maybe along the lines of :

    https://www.someurl.com/progress

    Which will simply be my http server sending the percentage back to the browser. I feel as though I am going about the architecture incorrectly and there must be a better way of architecting the final outcome.

  • How to build FFMPEG for all architecture of android device ?

    13 juillet 2017, par Prakash U

    I am trying to build ffmpeg for android in windows 8.1 using CYGWIN

    I am following This question & How to compile FFMPEG under Cygwin . I succsessfully compile but it is not generate FFMPEG.so but it generate ffmpeg.exe file

    I don’t want any prebuild ffmpeg library . I want to build it for my requirement.

    I perform this steps In CYGWIN BASE

    1. git clone git ://source.ffmpeg.org/ffmpeg.git ffmpeg
    2. dos2unix configure
    3. dos2unix build_ffmpeg.sh
    4. make distclean
    5. ./configure –enable-static –disable-shared
    6. make
    7. make install

    my build_ffmpeg.sh is

    # !/bin/bash

    NDK=/cygdrive/e/android/sdk/ndk-bundle
    PLATFORM=$NDK/platforms/android-24/arch-arm
    TOOLCHAIN=$NDK/toolchains/arm-linux-androideabi-4.9/prebuilt/windows
    CPU=arm
    PREFIX=$(pwd)/android/$CPU
    ADDI_CFLAGS="-marm"

    pushd ffmpeg
    # Configure
    ./configure \
    —target-os=android \
    —prefix=$PREFIX \
    —enable-cross-compile \
    —enable-runtime-cpudetect \
    —disable-asm \
    —arch=arm \
    —cc=$TOOLCHAIN/bin/arm-linux-androideabi-gcc \
    —cross-prefix=$TOOLCHAIN/bin/arm-linux-androideabi- \
    —disable-stripping \
    —nm=$TOOLCHAIN/bin/arm-linux-androideabi-nm \
    —sysroot=$PLATFORM \
    —disable-programs \
    —disable-doc \
    —enable-protocol=file \
    —disable-avresample \
    —enable-gpl \
    —enable-version3 \
    —enable-nonfree \
    —disable-ffplay \
    —disable-ffserver \
    —disable-ffmpeg \
    —disable-ffprobe \
    —extra-cflags="-fPIC -DANDROID -D__thumb__ -mthumb -Wfatal-errors -Wno-deprecated $ADDI_CFLAGS" \
    —extra-libs="-lgcc" \
    —extra-ldflags="-L$PLATFORM/usr/lib -nostdlib -lc -lm -ldl -llog"
    # Make
    make clean
    make -j5
    make -j5 install

    popd

    My LOG file is here

    My question is how to build ffmpeg for all architecture of android device ?

  • avutil/mem : Add DECLARE_ASM_ALIGNED macro for DJGPP architecture.

    14 novembre 2017, par Thomas Köppe
    avutil/mem : Add DECLARE_ASM_ALIGNED macro for DJGPP architecture.
    

    The macro was added in 43171a2a738f5114768d34a7278e56e5fde714bc, but I forgot to add it to the DJGPP architecture in that change.

    Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>

    • [DH] libavutil/mem.h