Recherche avancée

Médias (21)

Mot : - Tags -/Nine Inch Nails

Autres articles (67)

  • Publier sur MédiaSpip

    13 juin 2013

    Puis-je poster des contenus à partir d’une tablette Ipad ?
    Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir

  • MediaSPIP 0.1 Beta version

    25 avril 2011, par

    MediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
    The zip file provided here only contains the sources of MediaSPIP in its standalone version.
    To get a working installation, you must manually install all-software dependencies on the server.
    If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...)

  • Submit bugs and patches

    13 avril 2011

    Unfortunately a software is never perfect.
    If you think you have found a bug, report it using our ticket system. Please to help us to fix it by providing the following information : the browser you are using, including the exact version as precise an explanation as possible of the problem if possible, the steps taken resulting in the problem a link to the site / page in question
    If you think you have solved the bug, fill in a ticket and attach to it a corrective patch.
    You may also (...)

Sur d’autres sites (6801)

  • Revision 47613d071c : idct_blk_mmx.c : use vpx_memset instead of cast Fix warning with -Wstrict-aliasi

    29 octobre 2013, par Johann

    Changed Paths :
     Modify /vp8/common/x86/idct_blk_mmx.c



    idct_blk_mmx.c : use vpx_memset instead of cast

    Fix warning with -Wstrict-aliasing=1

    Change-Id : Ic37013e6477cf213925830d0bd8e6f17364ff7cc

  • Revision dc799a875b : vp9_decodframe.c : use vpx_memset instead of cast Fix warning with -Wstrict-alia

    29 octobre 2013, par Johann

    Changed Paths :
     Modify /vp9/decoder/vp9_decodframe.c



    vp9_decodframe.c : use vpx_memset instead of cast

    Fix warning with -Wstrict-aliasing=1

    Change-Id : Idfac09be1ab328923883e63436577f1018c895b8

  • Why sliced thread affect so much on realtime encoding using ffmpeg x264 ?

    13 avril 2016, par CurtisGuo

    I’m using ffmpeg libx264 to encode a 720p screen captured from x11 in realtime with a fps of 30.
    when I use -tune zerolatency paramenter, the average encode time per-frame can be as large as 12ms with profile baseline.

    After a study of the ffmpeg x264 source code, I found that the key parameter leading to such long encode time is sliced-threads which enabled by -tune zerolatency. After disabled using -x264-params sliced-threads=0 the encode time can be as low as 2ms

    And with sliced-threads disabled, the CPU usage will be 40%, while only 20% when enabled.

    Can someone explain the details about this sliced-thread ? Especially in realtime encoding(assume no frame is buffered to be encoded. only encode when a frame is captured).

Navigation