Recherche avancée

Médias (1)

Mot : - Tags -/censure

Autres articles (61)

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

  • Les autorisations surchargées par les plugins

    27 avril 2010, par

    Mediaspip core
    autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs

  • 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

Sur d’autres sites (14569)

  • Merge commit '0c0b87f12d48d4e7f0d3d13f9345e828a3a5ea32'

    28 septembre 2017, par James Almer
    Merge commit '0c0b87f12d48d4e7f0d3d13f9345e828a3a5ea32'

    * commit '0c0b87f12d48d4e7f0d3d13f9345e828a3a5ea32' :
    
  aarch64 : vp9itxfm : Fix incorrect vertical alignment
    
  aarch64 : vp9itxfm : Update a comment to refer to a register with a different name
    
  aarch64 : vp9itxfm : Use the right lane sizes in 8x8 for improved readability
    
  aarch64 : vp9itxfm : Use a single lane ld1 instead of ld1r where possible
    
  aarch64 : vp9itxfm : Share instructions for loading idct coeffs in the 8x8 function
    
  arm : vp9itxfm : Share instructions for loading idct coeffs in the 8x8 function
    
  aarch64 : vp9itxfm : Do separate functions for half/quarter idct16 and idct32
    
  arm : vp9itxfm : Do a simpler half/quarter idct16/idct32 when possible
    
  aarch64 : vp9itxfm : Move the load_add_store macro out from the itxfm16 pass2 function
    
  arm : vp9itxfm : Move the load_add_store macro out from the itxfm16 pass2 function
    
  aarch64 : vp9itxfm : Make the larger core transforms standalone functions
    
  arm : vp9itxfm : Make the larger core transforms standalone functions
    

    This commit is a noop, see
    
f8fcee0daf42d16581ec581bd5ff6373c3a76103
    
dc47bf3872fde18f6aea33f015a95b70e24dff19
    
3bd9b39108076e1fca8cd26970cb946fce66523a
    
a681c793a30386d01d273ce86b3368311cffb511
    
824589556cb7c4bfafb8a0190e71a10c628f5339
    
9532a7d4d060f2a2741225a76945daed52dbc478
    
1d8ab576a7e40ea6209dd753929f26dcb37e1444
    
3006e5253afc6a0ee001916806aae80f157d7043
    
19a0f9529ccdb48696f0caa251fe36b1d30df739
    
6752318c737663f0ac019de3acd63e3cea706864
    
d0fbf7f34e7243f6a4cbde9925f34d924e6d93f7
    
16ef000799b227d0226b7a678d28c34ff1d09410
    

    Merged-by : James Almer <jamrial@gmail.com>

  • Is H.264 used with CRF 0 really strictly lossless ?

    23 décembre 2017, par Mephisto

    I am surprised by how small files are when encoded in ffmpeg with the libx264 codec in Constant Rate Factor mode equals zero (-crf 0) that, according to the documentation, is "lossless".

    I would like to make sure what the word "lossless" here means. I would like to know if it follows my personal definition of lossless video : After encoding a video, you can confidently bet the life of your mother that, once you play it, the numerical values in the pixels of the restored video will be identically equal (within maybe a factor 0.00001 due to the floating point arithmetic) to the original.

    Does the H.264 lossless encoding follow my definition, or do they call it "lossless" because it is visually very close, very beautiful, whatever... ?

  • configure : Use pkg-config for fdk-aac

    10 mai 2015, par Luca Barbato
    configure : Use pkg-config for fdk-aac

    Makes the life of the people already setting PKG_CONFIG_PATH simpler.
    • [DH] configure

Navigation