Recherche avancée

Médias (39)

Mot : - Tags -/audio

Autres articles (68)

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

  • De l’upload à la vidéo finale [version standalone]

    31 janvier 2010, par

    Le chemin d’un document audio ou vidéo dans SPIPMotion est divisé en trois étapes distinctes.
    Upload et récupération d’informations de la vidéo source
    Dans un premier temps, il est nécessaire de créer un article SPIP et de lui joindre le document vidéo "source".
    Au moment où ce document est joint à l’article, deux actions supplémentaires au comportement normal sont exécutées : La récupération des informations techniques des flux audio et video du fichier ; La génération d’une vignette : extraction d’une (...)

  • Librairies et binaires spécifiques au traitement vidéo et sonore

    31 janvier 2010, par

    Les logiciels et librairies suivantes sont utilisées par SPIPmotion d’une manière ou d’une autre.
    Binaires obligatoires FFMpeg : encodeur principal, permet de transcoder presque tous les types de fichiers vidéo et sonores dans les formats lisibles sur Internet. CF ce tutoriel pour son installation ; Oggz-tools : outils d’inspection de fichiers ogg ; Mediainfo : récupération d’informations depuis la plupart des formats vidéos et sonores ;
    Binaires complémentaires et facultatifs flvtool2 : (...)

Sur d’autres sites (11454)

  • Mingw-w64 - printf does not work

    27 décembre 2013, par Gosha U.

    First I wanted to modificate ffplay according to my requirments. Then I noticed that original ffplay from my build can't play some video files, but it didn't write any message to console. Then I noticed that ffmpeg also don't write any usage message when I run it without params. But it works. If I run it from terminal it's like running asynchronously ! The terminal just shows next row. I mean it asks for a next command. But the ffmpeg process is visible in task manager and it writes the output video file what I had requested !

    I created following souce file. I have modified the Makefile. So it have built the exe-file works just the same way. I have no idea how it can be.

    #include
    #include "cmdutils.h"

    const char program_name[] = "hello";
    const int program_birth_year = 2013;

    void show_help_default(const char *opt, const char *arg)
    {
       printf("zxcvbnm\n");
    }

    int main(int argc, char **argv)
    {
       printf("1234567890\n");
       return 0;
    }

    And after that I created real hello world app with MinGW-w64 and qmake without eny extra libs. And its printf does not work.

    I want to prevent this behavior.

    I want to make printf working in traditional manner.

    How I build FFmpeg :

    PKG_CONFIG_PATH=/home/developer/workspace/MinGW32fs/lib/pkgconfig/ \
    SDL_CONFIG=/home/developer/workspace/MinGW32fs/bin/sdl-config \
    ./configure \
     --prefix=/home/developer/workspace/MinGW32fs \
     --extra-ldflags="-L/home/developer/workspace/MinGW32fs/lib" \
     --extra-cflags="-I/home/developer/workspace/MinGW32fs/include" \
     --arch=x86 --target-os=mingw32 --cross-prefix=i686-w64-mingw32-  \
     --pkg-config=pkg-config   --enable-libtheora --enable-libvorbis --enable-libvpx \
     --enable-outdev=sdl --enable-shared --disable-static \
     --disable-doc --disable-manpages --disable-podpages

    make
  • Mingw-w64 builded FFmpeg doesn't show any usage information

    26 octobre 2013, par user1240328

    First I wanted to modificate ffplay according to my requirments. Then I noticed that original ffplay from my build can't play some video files, but it didn't write any message to console. Then I noticed that ffmpeg also don't write any usage message when I run it without params. But it works. If I run it from terminal it's like running asynchronously ! The terminal just shows next row. I mean it asks for a next command. But the ffmpeg process is visible in task manager and it writes the output video file what I had requested !

    I created following souce file. I have modified the Makefile. So it have built the exe-file works just the same way. I have no idea how it can be.

    #include
    #include "cmdutils.h"

    const char program_name[] = "hello";
    const int program_birth_year = 2013;

    void show_help_default(const char *opt, const char *arg)
    {
       printf("zxcvbnm\n");
    }

    int main(int argc, char **argv)
    {
       printf("1234567890\n");
       return 0;
    }

    I want to prevent this behavior.

    I want to make printf working in traditional manner.

    How I build FFmpeg :

    PKG_CONFIG_PATH=/home/developer/workspace/MinGW32fs/lib/pkgconfig/ \
    SDL_CONFIG=/home/developer/workspace/MinGW32fs/bin/sdl-config \
    ./configure \
     --prefix=/home/developer/workspace/MinGW32fs \
     --extra-ldflags="-L/home/developer/workspace/MinGW32fs/lib" \
     --extra-cflags="-I/home/developer/workspace/MinGW32fs/include" \
     --arch=x86 --target-os=mingw32 --cross-prefix=i686-w64-mingw32-  \
     --pkg-config=pkg-config   --enable-libtheora --enable-libvorbis --enable-libvpx \
     --enable-outdev=sdl --enable-shared --disable-static \
     --disable-doc --disable-manpages --disable-podpages

    make
  • About image opacity

    23 octobre 2013, par Mikko Koppanen — Imagick

    There is a common misconception that Imagick::setImageOpacity() would work to reduce the opacity of the image. However, as the name says the method actually sets the opacity throughout the image and thus affects also transparent areas.

    To demonstrate let’s first look at this image of a red circle on a transparent background :

    Now, let’s apply setImageOpacity on the image :

    1. < ?php
    2. $im = new Imagick (’red-circle.png’) ;
    3. $im->setImageOpacity (0.5) ;
    4. $im->writeImage (’red-circle-setopacity.png’) ;
    5.  ?>

    As we can see from the resulting image the transparent background is affected as well.

    In order to actually reduce the opacity of the opaque parts Imagick::evaluateImage can be used instead :

    1. < ?php
    2. $im = new Imagick (’red-circle.png’) ;
    3.  
    4. /* Divide the alpha channel value by 2 */
    5. $im->evaluateImage(Imagick: :EVALUATE_DIVIDE, 2, Imagick: :CHANNEL_ALPHA) ;
    6. $im->writeImage (’red-circle-divide.png’) ;
    7.  ?>

    And here are the results :

    As the background is already fully transparent so the divide operation causes no changes to it.

    Similar example is available in the PHP manual http://php.net/imagick.evaluateimage and I added a note to setImageOpacity page as well (at the time of writing it has not synced to documentation mirrors yet).