Recherche avancée

Médias (1)

Mot : - Tags -/ogv

Autres articles (94)

  • Configuration spécifique d’Apache

    4 février 2011, par

    Modules spécifiques
    Pour la configuration d’Apache, il est conseillé d’activer certains modules non spécifiques à MediaSPIP, mais permettant d’améliorer les performances : mod_deflate et mod_headers pour compresser automatiquement via Apache les pages. Cf ce tutoriel ; mode_expires pour gérer correctement l’expiration des hits. Cf ce tutoriel ;
    Il est également conseillé d’ajouter la prise en charge par apache du mime-type pour les fichiers WebM comme indiqué dans ce tutoriel.
    Création d’un (...)

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

  • Contribute to translation

    13 avril 2011

    You can help us to improve the language used in the software interface to make MediaSPIP more accessible and user-friendly. You can also translate the interface into any language that allows it to spread to new linguistic communities.
    To do this, we use the translation interface of SPIP where the all the language modules of MediaSPIP are available. Just subscribe to the mailing list and request further informantion on translation.
    MediaSPIP is currently available in French and English (...)

Sur d’autres sites (7005)

  • Revision ea284d6281 : added checks to prevent rate/distortion overflow At speed 2, due to the thresho

    20 juillet 2013, par Yaowu Xu

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



    added checks to prevent rate/distortion overflow

    At speed 2, due to the threshold scheme used, it is possible the rate
    and distortion assigned with INT_MAX value. The patch added checking
    to prevent the INT_MAX value is used in further calculation of RD
    scores. The patch also changed the assertion in rd_use_partition() to
    be mirror similar assertion in rd_pick_partition().

    Change-Id : Idb52c543cc1e10abdf6e6a5d6e9cb535a42214dc

  • x264 library speed - Altivec vs SSE4 -

    15 août 2015, par Asain Kujovic

    I have simple cheap dualcore intel-3ghz-debian and access to super-expensive powerPc7-Aix.

    And after few days of strugle, i compiled libx264 and tested it on both computers :

    1. GCC : library x264 on intel (with SSE2 capabilities) and
    2. GCC on 16 core powerPc (with altivec).

    ... and result is that cheap intel is x2 times faster ! (with altivec disabled, intel is 10x times faster)

    My question : is this normal ?
    Does all other powerPC-users have same results ? Can powerPc-altivec-optimisation of x264 library work at same speed with intel... or MMX/SSE optimisation is officially at least 2 times faster for this library ?

    I am not interested in multi-thread options. Number of cores and threads are irrelevant. Just simple one-thread x264 encoding with default "medium preset" using rawvideo as source, sse vs altivec.

    Maybe native Aix XLC compiler provide better results ? (i managed only gcc to work)

    ... mac-powerpc-users maybe know something about this.

    powrPc7-Aix:$ time (cat raw10sec.y4m |x264 --input-res 720x576 --fps 50 -o /dev/null -)
    
x264: 64-bit XCOFF
    
x264 [info]: using cpu capabilities: Altivec
    
time: real 0m33.559s
    
---
    
intelDebian:$ time (cat raw10sec.y4m |x264 --input-res 720x576 --fps 50 -o /dev/null -)
    
x264: ELF 32-bit LSB executable
    
x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 FastShuffle SSE4.1 Cache64
    
time: real 0m16.503s

  • x264 library speed - Altivec vs SSE4 -

    15 août 2015, par Asain Kujovic

    I have simple cheap dualcore intel-3ghz-debian and access to super-expensive powerPc7-Aix.

    And after few days of strugle, i compiled libx264 and tested it on both computers :

    1. GCC : library x264 on intel (with SSE2 capabilities) and
    2. GCC on 16 core powerPc (with altivec).

    ... and result is that cheap intel is x2 times faster ! (with altivec disabled, intel is 10x times faster)

    My question : is this normal ?
    Does all other powerPC-users have same results ? Can powerPc-altivec-optimisation of x264 library work at same speed with intel... or MMX/SSE optimisation is officially at least 2 times faster for this library ?

    I am not interested in multi-thread options. Number of cores and threads are irrelevant. Just simple one-thread x264 encoding with default "medium preset" using rawvideo as source, sse vs altivec.

    Maybe native Aix XLC compiler provide better results ? (i managed only gcc to work)

    ... mac-powerpc-users maybe know something about this.

    powrPc7-Aix:$ time (cat raw10sec.y4m |x264 --input-res 720x576 --fps 50 -o /dev/null -)
    
x264: 64-bit XCOFF
    
x264 [info]: using cpu capabilities: Altivec
    
time: real 0m33.559s
    
---
    
intelDebian:$ time (cat raw10sec.y4m |x264 --input-res 720x576 --fps 50 -o /dev/null -)
    
x264: ELF 32-bit LSB executable
    
x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 FastShuffle SSE4.1 Cache64
    
time: real 0m16.503s

Navigation