Recherche avancée

Médias (91)

Autres articles (72)

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

  • Pas question de marché, de cloud etc...

    10 avril 2011

    Le vocabulaire utilisé sur ce site essaie d’éviter toute référence à la mode qui fleurit allègrement
    sur le web 2.0 et dans les entreprises qui en vivent.
    Vous êtes donc invité à bannir l’utilisation des termes "Brand", "Cloud", "Marché" etc...
    Notre motivation est avant tout de créer un outil simple, accessible à pour tout le monde, favorisant
    le partage de créations sur Internet et permettant aux auteurs de garder une autonomie optimale.
    Aucun "contrat Gold ou Premium" n’est donc prévu, aucun (...)

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

Sur d’autres sites (10798)

  • Révision 118691 : cas particulier des cases a cocher, style minimal mais quand meme

    18 novembre 2019, par cerdic -
  • avcodec/pixlet : consider minimum plane header in the minimal packet size

    30 avril 2022, par Michael Niedermayer
    avcodec/pixlet : consider minimum plane header in the minimal packet size
    

    Fixes : Timeout
    Fixes : 46956/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_PIXLET_fuzzer-5698161106092032

    Found-by : continuous fuzzing process https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
    Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>

    • [DH] libavcodec/pixlet.c
  • Finding a minimal configuration for ffmpeg

    28 novembre 2022, par Clemens3000

    i am currently developing a video player for Windows and Mac using JUCE and FFmpeg. For this i want to include FFmpeg as a shared library and compile it myself in a minimal configuration to get rid of features and dependencies i don't need. This turns out to be quite difficult, since FFmpeg has a HUGE load of dependencies. And i am pretty new to this compiling game.

    &#xA;

    Of course i checked all the options for configuration, but there is so many and don't have much knowledge about what all the options actually do. Some are obvious, but many are not.

    &#xA;

    The minimal configuration i am looking for should enable to playback videofiles encoded with h.264 and it should be LGPL compliant. So just decoding, no encoding.

    &#xA;

    What i did :

    &#xA;

      &#xA;
    • i installed some of the dependencies i might need via macports (under /opt/local)
    • &#xA;

    • i downloaded ffmpeg source code, played around with the configure options and compiled it
    • &#xA;

    • i managed to build my app and it even runs
    • &#xA;

    • i created a configuration with "—disable_everything" and then tried to add features one after another until i build something that works. But that's like finding a needle in the haystack.
    • &#xA;

    &#xA;

    For Mac my first attempt for this is :&#xA;./configure --disable-everything --prefix=&#x27;../../osx_arm&#x27; --install-name-dir=&#x27;@executable_path/../libs&#x27; --extra-ldflags=-Wl,-rpath,&#x27;@executable_path/../libs&#x27; --enable-version3 --enable-shared --disable-static --enable-swscale --enable-avfilter --enable-libfdk-aac --enable-audiotoolbox --enable-videotoolbox --enable-pthreads --cc=/usr/bin/clang --extra-ldflags=-L/opt/local/lib

    &#xA;

    I can compile and link my program and as i expected I cannot do much more, which is totally fine for now.

    &#xA;

    My questions are now :

    &#xA;

      &#xA;
    1. How can i find out which configure options are essential to enable simple playback ? How do i find out which options can be discarded ?

      &#xA;

    2. &#xA;

    3. If i run otool on the resulting libs in my current minimal build i still get some dependencies :

      &#xA;

    4. &#xA;

    &#xA;

    otool -L ../../osx_arm/lib/libavcodec.59.37.100.dylib  ../../osx_arm/lib/libavcodec.59.37.100.dylib: @executable_path/../libs/libavcodec.59.dylib (compatibility version 59.0.0, current version 59.37.100) @executable_path/../libs/libavutil.57.dylib (compatibility version 57.0.0, current version 57.28.100) /opt/local/lib/libiconv.2.dylib (compatibility version 9.0.0, current version 9.1.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1292.100.5) /System/Library/Frameworks/VideoToolbox.framework/Versions/A/VideoToolbox (compatibility version 1.0.0, current version 1.0.0) /opt/local/lib/libX11.6.dylib (compatibility version 11.0.0, current version 11.0.0) /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 1775.118.101) /System/Library/Frameworks/CoreMedia.framework/Versions/A/CoreMedia (compatibility version 1.0.0, current version 1.0.0) /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo (compatibility version 1.2.0, current version 1.5.0) /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices (compatibility version 1.0.0, current version 1122.33.0)

    &#xA;

    Why does FFmpeg actually need libiconv or libX11 ? I believe those don't have to do much with video/audio, right ? Well, I guess FFmpeg needs them anyway...So do i need to compile them myself to and add them to my Application ? I guess later i'll have even more dependencies.

    &#xA;

      &#xA;
    1. Any other tips on how to accomplish what i want ?
    2. &#xA;

    &#xA;