Recherche avancée

Médias (1)

Mot : - Tags -/MediaSPIP 0.2

Autres articles (49)

  • Supporting all media types

    13 avril 2011, par

    Unlike most software and media-sharing platforms, MediaSPIP aims to manage as many different media types as possible. The following are just a few examples from an ever-expanding list of supported formats : images : png, gif, jpg, bmp and more audio : MP3, Ogg, Wav and more video : AVI, MP4, OGV, mpg, mov, wmv and more text, code and other data : OpenOffice, Microsoft Office (Word, PowerPoint, Excel), web (html, CSS), LaTeX, Google Earth and (...)

  • Les formats acceptés

    28 janvier 2010, par

    Les commandes suivantes permettent d’avoir des informations sur les formats et codecs gérés par l’installation local de ffmpeg :
    ffmpeg -codecs ffmpeg -formats
    Les format videos acceptés en entrée
    Cette liste est non exhaustive, elle met en exergue les principaux formats utilisés : h264 : H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 m4v : raw MPEG-4 video format flv : Flash Video (FLV) / Sorenson Spark / Sorenson H.263 Theora wmv :
    Les formats vidéos de sortie possibles
    Dans un premier temps on (...)

  • Contribute to a better visual interface

    13 avril 2011

    MediaSPIP is based on a system of themes and templates. Templates define the placement of information on the page, and can be adapted to a wide range of uses. Themes define the overall graphic appearance of the site.
    Anyone can submit a new graphic theme or template and make it available to the MediaSPIP community.

Sur d’autres sites (7656)

  • configure : Don’t add -fPIC on windows targets

    5 juin 2013, par Martin Storsjö
    configure : Don’t add -fPIC on windows targets

    This avoids warnings about this option not having any effect on
    
this platform.
    

    We still want to enable the pic configure item for these platforms
    
(if detected via the compiler builtin define __PIC__) to get proper
    
inline assembly workarounds.
    

    Signed-off-by : Martin Storsjö <martin@martin.st>
    • [DBH] configure

  • FFMPEG giving error on compiling on Windows

    1er août 2014, par user2384410

    Hi I am trying to build FFMPEG following :http://www.roman10.net/how-to-build-ffmpeg-with-ndk-r9/
    I have set up all the things including changes in configure file and preparing build_android.sh but when I am trying to compile this using cygwin on my Windows machine,I get following error :-

    d :/android-ndk/android-ndk-r10/toolchains/arm-linux-androideabi-4.8/prebuilt/windows-x86_64/bin/../lib/gcc/arm-linux-androideabi/4.8/../../../../arm-linux-androideabi/bin/ld.exe : error : libavutil/libavutil.so:1:1 : syntax error, unexpected ’ !’, expecting $end

    I am using NDK-r10 and Windows-7(64-bit).

  • FFMPEG on Windows faststart command line with or without a +

    24 juillet 2014, par C0nw0nk

    So on the following wiki page i see ffmpeg tells us when using faststart for HTML5 compatibility we should use a + symbol.

    https://trac.ffmpeg.org/wiki/Encode/H.264#faststartforwebvideo

    -movflags +faststart

    But looking at command line examples on here and other sites everyone puts it in their command line like this.

    ffmpeg -i C:\vidtests\Wildlife.mp4 -movflags faststart C:\vidtests\Wildlife_fs.mp4

    So my question is should it matter if the + symbol is there or not ?

Navigation