Recherche avancée

Médias (91)

Autres articles (8)

  • Le profil des utilisateurs

    12 avril 2011, par

    Chaque utilisateur dispose d’une page de profil lui permettant de modifier ses informations personnelle. Dans le menu de haut de page par défaut, un élément de menu est automatiquement créé à l’initialisation de MediaSPIP, visible uniquement si le visiteur est identifié sur le site.
    L’utilisateur a accès à la modification de profil depuis sa page auteur, un lien dans la navigation "Modifier votre profil" est (...)

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

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

  • Revision e6c89a1f9b : Merge "Code cleanup." into experimental

    20 février 2013, par Dmitry Kovalev

    Changed Paths : Modify /vp9/common/vp9_blockd.h Merge "Code cleanup." into experimental

  • Revision 441f24de3d : Merge "Merge lossless experiment" into experimental

    20 février 2013, par Yaowu Xu

    Changed Paths : Modify /vp9/encoder/vp9_bitstream.c Modify /vp9/encoder/vp9_onyx_if.c Merge "Merge lossless experiment" into experimental

  • NDK r8c warning for asm objects regarding "Cortex-A8 erratum" - should I be worried ?

    7 décembre 2012, par Alex Cohn

    Question : What is the meaning of this warning ? If there are no real-life consequences, I can live with it for a while... But I am concerned with what will happen if our program gets loaded on one of the faulty chips.

    Background : With NDK r8c, linking of X264 encoder issues warnings :

    cannot scan executable section 1 of libx264.a(dct-a.o) for Cortex-A8 erratum because it has no mapping symbols

    ... same warning for all assembly files in libx264.

    libx264.a itself was cross-compiled on the same machine with the same 4.6 toolchain taken from NDK.

    Here are the instructions to easily reproduce the problem (Ubuntu or MacOS) :

    1. Download x264-snapshot-20121203-2245 from ftp://ftp.videolan.org/pub/x264/snapshots/last_x264.tar.bz2

    2. Run ./configure --enable-pic --enable-strip --enable-static --cross-prefix=~/android-ndk-r8c/toolchains/arm-linux-androideabi-4.6/prebuilt/linux-x86/bin/arm-linux-androideabi- --sysroot=~/android-ndk-r8c/platforms/android-14/arch-arm --host=arm-linux

    3. Run ~/android-ndk-r8c/prebuilt/linux-x86/bin/make

    It will build the static library, and after that display the Cortex-A8 warning while linking the x265 executable. I am not worried about the compiler warnings, because building libx264.a is done offline, it is not part of our official daily build.

    I have reported this as http://code.google.com/p/android/issues/detail?id=40794.

    I tried to add the mapping symbols manually to dct-a.S following the ARM.com instructions, but this had no effect.

Navigation