Recherche avancée

Médias (91)

Autres articles (40)

  • Des sites réalisés avec MediaSPIP

    2 mai 2011, par

    Cette page présente quelques-uns des sites fonctionnant sous MediaSPIP.
    Vous pouvez bien entendu ajouter le votre grâce au formulaire en bas de page.

  • Use, discuss, criticize

    13 avril 2011, par

    Talk to people directly involved in MediaSPIP’s development, or to people around you who could use MediaSPIP to share, enhance or develop their creative projects.
    The bigger the community, the more MediaSPIP’s potential will be explored and the faster the software will evolve.
    A discussion list is available for all exchanges between users.

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

  • Android built in Camera encoder VS FFMPEG --- Speed

    3 novembre 2015, par user3903275

    How does recording a 1080P, H264 encoded video in android camera application is realtime fast but encoding a video in android using FFMPEG is slow at the same video size ?

    I know FFMPEG is a software level encoder and it wont support any hardware features.

    I know camera applications directly get buffer data from camera driver.

    But actually where the difference happens ??

    Why camera application is Realtime fast ???

    Does it use GPU and OpenGL features of the phone to encode the video so that its so realtime fast ??

    Because both Camera Application and FFMPEG runs on same mobile but still camera encodes H264 realtime ???

  • Revision 62c6411820 : Remove neon version of vp8 extend borders The code fails the unit test. Speed c

    24 juillet 2014, par Johann

    Changed Paths :
     Modify /test/scale_border_test.cc


     Delete /vpx_scale/arm/neon/vp8_vpxyv12_extendframeborders_neon.asm


     Modify /vpx_scale/arm/neon/yv12extend_arm.c


     Modify /vpx_scale/vpx_scale.mk


     Modify /vpx_scale/vpx_scale_rtcd.pl



    Remove neon version of vp8 extend borders

    The code fails the unit test. Speed comparisons to the C are invalid
    because the code frequently didn’t correctly extend the right and
    bottom portions of the frame.

    Reduce maximum frame size on ARM devices to avoid OOM

    Change-Id : Ia664c86406f0bb8120fd7ad401f32d0bd44994fb

  • Revision 51c60a891e : make default_interp_filter choice a speed feature This commit changed the hard-

    16 juillet 2014, par Yaowu Xu

    Changed Paths :
     Modify /vp9/encoder/vp9_encoder.c


     Modify /vp9/encoder/vp9_speed_features.c


     Modify /vp9/encoder/vp9_speed_features.h



    make default_interp_filter choice a speed feature

    This commit changed the hard-coded DEFAULT_INTERP_FILTER to a speed
    feature with the same default value : SWITCHABLE.

    Change-Id : I7f54f40f1bd3f5277841d04b85db7a84e47313f1

Navigation