Recherche avancée

Médias (1)

Mot : - Tags -/biomaping

Autres articles (50)

  • 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

  • HTML5 audio and video support

    13 avril 2011, par

    MediaSPIP uses HTML5 video and audio tags to play multimedia files, taking advantage of the latest W3C innovations supported by modern browsers.
    The MediaSPIP player used has been created specifically for MediaSPIP and can be easily adapted to fit in with a specific theme.
    For older browsers the Flowplayer flash fallback is used.
    MediaSPIP allows for media playback on major mobile platforms with the above (...)

  • Librairies et binaires spécifiques au traitement vidéo et sonore

    31 janvier 2010, par

    Les logiciels et librairies suivantes sont utilisées par SPIPmotion d’une manière ou d’une autre.
    Binaires obligatoires FFMpeg : encodeur principal, permet de transcoder presque tous les types de fichiers vidéo et sonores dans les formats lisibles sur Internet. CF ce tutoriel pour son installation ; Oggz-tools : outils d’inspection de fichiers ogg ; Mediainfo : récupération d’informations depuis la plupart des formats vidéos et sonores ;
    Binaires complémentaires et facultatifs flvtool2 : (...)

Sur d’autres sites (9268)

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

  • avfilter/showcqt : remove yuv offset

    3 novembre 2015, par Muhammad Faiz
    avfilter/showcqt : remove yuv offset

    this makes draw_bar faster
    
slightly different result with old version
    

    check result (with 3 minutes audio file) :
    
old :
    
    real    0m49.611s
    
    user    0m49.260s
    
    sys     0m0.073s
    
new :
    
    real    0m47.606s
    
    user    0m47.378s
    
    sys     0m0.068s
    
PSNR between old and new :
    
yuv444p PSNR
    
    y:109.519298 u:107.506485 v:104.746878
    
    average:106.816074 min:99.167305 max:inf
    
yuv422p PSNR
    
    y:109.519298 u:108.025801 v:104.489734
    
    average:107.279817 min:98.007467 max:inf
    
yuv420p PSNR
    
    y:109.519298 u:108.363875 v:105.290200
    
    average:108.261511 min:97.461812 max:inf
    

    Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>
    • [DH] libavfilter/avf_showcqt.c

  • avfilter/delogo : Set default band to 1

    7 octobre 2015, par Jean Delvare
    avfilter/delogo : Set default band to 1

    The original interpolation algorithm behaved poorly on the borders and
    
did not even guarantee continuity at the borders. For this reason, a
    
second interpolation/blending pass was required on the borders to make
    
them seamless.
    

    However, since the interpolation algorithm was improved in June 2013,
    
the border issues no longer exist. The new algorithm does guarantee
    
continuity at the borders, making the second pass useless. A larger
    
band always increases the cumulated interpolation error. In most cases
    
it also increases the average interpolation error, even though the
    
samples in the band are only partially interpolated.
    

    For this reason I would like to get rid of the "band" parameter. As a
    
first step, let’s change its default value from 4 to 1 and document it
    
as deprecated.
    

    I have benchmarked this change on a combination of input sources and
    
realistic logo areas. Lowering the band value from 4 to 1 resulted in
    
8 to 39 % less interpolation error per frame (or 1 to 34 % less
    
interpolation error per luma sample.)
    

    Signed-off-by : Jean Delvare <jdelvare@suse.de>
    
Signed-off-by : Stefano Sabatini <stefasab@gmail.com>
    • [DH] doc/filters.texi
    • [DH] libavfilter/vf_delogo.c

Navigation