Recherche avancée

Médias (91)

Autres articles (74)

  • Gestion des droits de création et d’édition des objets

    8 février 2011, par

    Par défaut, beaucoup de fonctionnalités sont limitées aux administrateurs mais restent configurables indépendamment pour modifier leur statut minimal d’utilisation notamment : la rédaction de contenus sur le site modifiables dans la gestion des templates de formulaires ; l’ajout de notes aux articles ; l’ajout de légendes et d’annotations sur les images ;

  • Dépôt de média et thèmes par FTP

    31 mai 2013, par

    L’outil MédiaSPIP traite aussi les média transférés par la voie FTP. Si vous préférez déposer par cette voie, récupérez les identifiants d’accès vers votre site MédiaSPIP et utilisez votre client FTP favori.
    Vous trouverez dès le départ les dossiers suivants dans votre espace FTP : config/ : dossier de configuration du site IMG/ : dossier des média déjà traités et en ligne sur le site local/ : répertoire cache du site web themes/ : les thèmes ou les feuilles de style personnalisées tmp/ : dossier de travail (...)

  • Keeping control of your media in your hands

    13 avril 2011, par

    The vocabulary used on this site and around MediaSPIP in general, aims to avoid reference to Web 2.0 and the companies that profit from media-sharing.
    While using MediaSPIP, you are invited to avoid using words like "Brand", "Cloud" and "Market".
    MediaSPIP is designed to facilitate the sharing of creative media online, while allowing authors to retain complete control of their work.
    MediaSPIP aims to be accessible to as many people as possible and development is based on expanding the (...)

Sur d’autres sites (8935)

  • Android Ndk & FFMPEG - Not able to compile on ubuntu x86

    18 février 2015, par Palak Darji

    I am following this :
    roman10’s android ndk r9d - ffmpeg tutorial
    I am able to run build_android.sh script.. but its not creating that ‘android’ folder in my source/ffmpeg folder !!
    what should I do ? Plz help me.

    Another Doubt : The thing ‘arm’ in that .sh file is supposed to be changed according to machine env ???? If that is the case, can you guide us for x86 ???

    my build_android.sh file :

    #!/bin/bash
    NDK=/home/NDK/android-ndk-r9d
    SYSROOT=$NDK/platforms/android-19/arch-arm/
    TOOLCHAIN=$NDK/toolchains/arm-linux-androideabi-4.8/prebuilt/linux-arm
    function build_one
    {
    sudo ./configure \
       --target-os=linux \
       --prefix=$PREFIX \
       --enable-shared \
       --disable-static \
       --disable-doc \
       --disable-ffmpeg \
       --disable-ffplay \
       --disable-ffprobe \
       --disable-ffserver \
       --disable-avdevice \
       --disable-doc \
       --disable-symver \
       --cross-prefix=$TOOLCHAIN/bin/arm-linux-androideabi- \
       --arch=arm \
       --enable-cross-compile \
       --sysroot=$SYSROOT \
       --extra-cflags="-Os -fpic $ADDI_CFLAGS" \
       --extra-ldflags="$ADDI_LDFLAGS" \
       $ADDITIONAL_CONFIGURE_FLAG
    make clean
    make
    make install
    }
    CPU=i686
    PREFIX=$(pwd)/android/$CPU
    ADDI_CFLAGS="-marm"
    build_one

    I am using Ndk r10, ffmpeg 2.5.4, ubuntu x86.

    Thanks for ur time.

    Palak.

  • wait for node server to start up in php

    22 février 2015, par Ortix92

    I have a php script which does the following :

    1. Start peerflix (node server)
    2. Get PID
    3. FFProbe* the server (http://127.0.0.1:8888)

    All of this is done in PHP but there is a slight issue. It seems that after having received the PID, the server is not fully initialized yet, or so it seems. The problem is that FFProbe cannot probe the server. In other words, it’s not accessible at the time of probing.

    What are some possibilities to probe the server when it is actually initialized ? I don’t want to use the arbitrary sleep() method because waiting for 2 seconds on a slow vagrant machine is now the same as waiting for 2 seconds on a blazing vast server.

    FFProbe throws an exception when it can’t probe the server. Perhaps use a try-catch and return back to the try if an exception is thrown ? How would I implement that ?

    *FFProbe is a companion of FFMpeg to get the information of a video file such as duration and codec.

  • Is it possible to stream netflix in either an embedded version of chromium or using ffmpeg ?

    24 février 2015, par OzBarry

    I’m looking into building an all-in-one media streaming application for my raspberry pi2, since there are currently very few options, and it’s scalable to other systems. The biggest hurdle I’ve found in requirements gathering is being able to stream netflix.

    There have been very few attempts at getting chromium to stream netflix, and even fewer on armv7h systems, so I’m trying to look at alternatives.

    My first thought is using a combination of curl and ffmpeg, and I think this would somehow work, however this doesn’t solve the issue with the DRM.

    Another option would be to stream from another computer into my application. This solves the DRM issue, but encumbers my software setup, burdens users to have at least one computer that can also stream netflix, and will suffer from lag (netflix -> computer a -> computer b). The last point can be sorted out with buffering, but that may not be ideal, since it adds stress to the raspberry pi machine.

    As a side note, I am using SDL2 for rendering, so I would be fine with a binary library that decodes the frames and audio, and sends it directly to a SDL renderer ad audio stream without allowing me to modify/copy it.

    Does anything like these options exist ? I really just want to get a legit stream from netflix if possible, while not interferring with the DRM.