Recherche avancée

Médias (3)

Mot : - Tags -/spip

Autres articles (17)

  • L’agrémenter visuellement

    10 avril 2011

    MediaSPIP est basé sur un système de thèmes et de squelettes. Les squelettes définissent le placement des informations dans la page, définissant un usage spécifique de la plateforme, et les thèmes l’habillage graphique général.
    Chacun peut proposer un nouveau thème graphique ou un squelette et le mettre à disposition de la communauté.

  • 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

  • Keeping control of your media in your hands

    13 avril 2011, par

    The vocabulary used on this site and around MediaSPIP in general, aims to avoid reference to Web 2.0 and the companies that profit from media-sharing.
    While using MediaSPIP, you are invited to avoid using words like "Brand", "Cloud" and "Market".
    MediaSPIP is designed to facilitate the sharing of creative media online, while allowing authors to retain complete control of their work.
    MediaSPIP aims to be accessible to as many people as possible and development is based on expanding the (...)

Sur d’autres sites (3104)

  • Merge remote-tracking branch ’rbultje/vp9-profile1-wip’

    1er mai 2015, par Michael Niedermayer
    Merge remote-tracking branch ’rbultje/vp9-profile1-wip’

    * rbultje/vp9-profile1-wip :
    
  vp9 : add fate test for 422.
    
  vp9 : copy bug in libvpx for 4:2:2 chroma bs=8x4/4x4 prediction.
    
  vp9 : add yuv440 fate test.
    
  vp9 : fix mask_edges and filter_plane_rows/cols() for 440.
    
  vp9 : more specifically specify mask destination to mask_edges().
    
  vp9 : add fate test for profile 1 444.
    
  vp9 : don’t create special u/v filter masks for 444.
    
  vp9 : merge uv loopfilter code into generic filter_plane_rows/cols().
    
  vp9 : split out loopfilter luma rows/cols functions from loopfilter_sb().
    
  vp9 : invert order of two conditions.
    
  vp9 : use correct chroma subsampling for profile 1 inter block recon.
    
  vp9 : use correct chroma subsampling for profile 1 intra block recon.
    
  vp9 : take chroma subsampling into account when walking the block tree.
    
  vp9 : support non-420 chroma subsampling for profile 1 token decoding.
    
  vp9 : increase buffer sizes for non-420 chroma subsamplings.
    
  vp9 : profile 1 header decoding.
    

    Merged-by : Michael Niedermayer <michaelni@gmx.at>
    • [DH] libavcodec/vp9.c
    • [DH] libavcodec/vp9_mc_template.c
    • [DH] tests/fate/vpx.mak
    • [DH] tests/ref/fate/vp9p1-04-yuv422
    • [DH] tests/ref/fate/vp9p1-04-yuv440
    • [DH] tests/ref/fate/vp9p1-04-yuv444

  • rtsp : Don’t warn about unparsed time ranges

    22 avril 2015, par Martin Storsjö
    rtsp : Don’t warn about unparsed time ranges

    This removes the error logging added in 4e54432164.
    

    This avoids warnings about "Invalid interval start specification ’now’"
    
for live rtsp streams.
    

    We only try to parse some of the many valid values for time ranges
    
in RTSP - the other ones are fully valid but not interesting for the
    
use case in rtsp.c, so we shouldn’t warn about them.
    

    (Parsing the time ranges is needed to allow seeking, but e.g. setting
    
the current realtime clock for the start time doesn’t make sense.
    
av_parse_time has got a different mode for parsing absolute times
    
as well, which can handle the special case "now", but that doesn’t
    
make much sense for this particular use in rtsp.c.)
    

    Signed-off-by : Martin Storsjö <martin@martin.st>
    • [DH] libavformat/rtsp.c

  • rtsp : Don’t warn about unparsed time ranges

    22 avril 2015, par Martin Storsjö
    rtsp : Don’t warn about unparsed time ranges

    This removes the error logging added in 4e54432164.
    

    This avoids warnings about "Invalid interval start specification ’now’"
    
for live rtsp streams.
    

    We only try to parse some of the many valid values for time ranges
    
in RTSP - the other ones are fully valid but not interesting for the
    
use case in rtsp.c, so we shouldn’t warn about them.
    

    (Parsing the time ranges is needed to allow seeking, but e.g. setting
    
the current realtime clock for the start time doesn’t make sense.
    
av_parse_time has got a different mode for parsing absolute times
    
as well, which can handle the special case "now", but that doesn’t
    
make much sense for this particular use in rtsp.c.)
    

    Signed-off-by : Martin Storsjö <martin@martin.st>
    • [DBH] libavformat/rtsp.c

Navigation