Recherche avancée

Médias (2)

Mot : - Tags -/rotation

Autres articles (86)

  • Personnaliser en ajoutant son logo, sa bannière ou son image de fond

    5 septembre 2013, par

    Certains thèmes prennent en compte trois éléments de personnalisation : l’ajout d’un logo ; l’ajout d’une bannière l’ajout d’une image de fond ;

  • 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

  • Encoding and processing into web-friendly formats

    13 avril 2011, par

    MediaSPIP automatically converts uploaded files to internet-compatible formats.
    Video files are encoded in MP4, Ogv and WebM (supported by HTML5) and MP4 (supported by Flash).
    Audio files are encoded in MP3 and Ogg (supported by HTML5) and MP3 (supported by Flash).
    Where possible, text is analyzed in order to retrieve the data needed for search engine detection, and then exported as a series of image files.
    All uploaded files are stored online in their original format, so you can (...)

Sur d’autres sites (11652)

  • Anomalie #3436 (Nouveau) : Forum : id_thread = 0

    5 mai 2015, par Debondt Didier

    Si j’utilise l’API objet pour créer des éléments de forum, sans spécifier explicitement un id_thread :

    $id_forum = objet_inserer(’forum’, null, $c) ;

    Il est possible que le champ id_thread soit égale à 0. Hors cela ne devrait jamais être le cas, il devrait à minima être égale à id_forum.

  • Revision 507fd5220b : Enable encode_breakout in real time encoding In real time encoding, we enable e

    4 février 2014, par Yunqing Wang

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


     Modify /vp9/encoder/vp9_firstpass.c


     Modify /vp9/encoder/vp9_onyx_if.c


     Modify /vp9/encoder/vp9_onyx_int.h


     Modify /vp9/encoder/vp9_rdopt.c



    Enable encode_breakout in real time encoding

    In real time encoding, we enable encode_breakout to make encoding
    fast. A speed feature "use_encode_breakout" is defined to set
    encode_breakout thresholds for different speeds.

    However, currently, static_thresh is an encoder option. The encode_
    breakout can be turned off if user sets static_thresh=0 specifically.

    The rtc set borg test result : (need to set —static_thresh=1)
    speed -5, psnr loss -3.543% ;
    speed -4, psnr loss -2.358% ;
    speed -3, psnr loss -0.771%.

    Encoding speed test :
    speed -5, 11% - 60% speedup ;
    speed -4, 5.5% - 28% speedup ;
    speed -3, 0.8% - 7% speedup.

    Change-Id : Icde592ffbe77eac7446f872a2e9eb2051733677b

  • vdpau : do not use buggy HEVC support by default

    1er juillet 2017, par wm4
    vdpau : do not use buggy HEVC support by default

    NVIDIA broke its own API when using VDPAU decoding. If you retrieve the
    
decoded YUV data, or if you map the surfaces with GL interop, the result
    
are interlacing artifacts. The only way to get non-broken data is by
    
using the vdpau video mixer to convert it to RGB. There is no way to
    
block the non-working operations in a reasonable way (a VdpVideoSurface
    
has to support all operations).
    

    NVIDIA refuses to fix this issue (they "fixed" it by making it work with
    
the video mixer, but the rest is still broken). There is no sign of that
    
changing.
    

    Do not use HEVC by default with the generic hwaccle API. Detect whether
    
it's the NVIDIA native implementation, and exit with an error. (The same
    
thing work with the MESA implementation.)
    

    As an escape hatch and to allow applications to use the decoder if they
    
really want to (perhaps because they make sure to explicitly use the
    
video mixer), reuse AV_HWACCEL_FLAG_ALLOW_PROFILE_MISMATCH to disable
    
this check.
    

    Once NVIDIA fixes the bug, working driver versions could be detected,
    
and it could be allowed again.
    • [DH] libavcodec/vdpau.c

Navigation