Recherche avancée

Médias (91)

Autres articles (20)

  • Supporting all media types

    13 avril 2011, par

    Unlike most software and media-sharing platforms, MediaSPIP aims to manage as many different media types as possible. The following are just a few examples from an ever-expanding list of supported formats : images : png, gif, jpg, bmp and more audio : MP3, Ogg, Wav and more video : AVI, MP4, OGV, mpg, mov, wmv and more text, code and other data : OpenOffice, Microsoft Office (Word, PowerPoint, Excel), web (html, CSS), LaTeX, Google Earth and (...)

  • Support de tous types de médias

    10 avril 2011

    Contrairement à beaucoup de logiciels et autres plate-formes modernes de partage de documents, MediaSPIP a l’ambition de gérer un maximum de formats de documents différents qu’ils soient de type : images (png, gif, jpg, bmp et autres...) ; audio (MP3, Ogg, Wav et autres...) ; vidéo (Avi, MP4, Ogv, mpg, mov, wmv et autres...) ; contenu textuel, code ou autres (open office, microsoft office (tableur, présentation), web (html, css), LaTeX, Google Earth) (...)

  • Other interesting software

    13 avril 2011, par

    We don’t claim to be the only ones doing what we do ... and especially not to assert claims to be the best either ... What we do, we just try to do it well and getting better ...
    The following list represents softwares that tend to be more or less as MediaSPIP or that MediaSPIP tries more or less to do the same, whatever ...
    We don’t know them, we didn’t try them, but you can take a peek.
    Videopress
    Website : http://videopress.com/
    License : GNU/GPL v2
    Source code : (...)

Sur d’autres sites (5446)

  • lavc/mediacodecdec_common : enable refcounting of buffers unconditionally

    18 septembre 2022, par sfan5
    lavc/mediacodecdec_common : enable refcounting of buffers unconditionally

    This allows av_mediacodec_release_buffer to be called safely after
    
the decoder is closed, this was already the case with delay_flush=1.
    
Note that this causes holding onto frames to keep the decoding context
    
alive which is generally considered to be the intended behavior.
    

    Signed-off-by : sfan5 <sfan5@live.de>
    
Signed-off-by : Anton Khirnov <anton@khirnov.net>
    • [DH] libavcodec/mediacodecdec_common.c

  • avformat/udp : redesign threaded udp tx code

    25 mai 2016, par Michael Niedermayer
    avformat/udp : redesign threaded udp tx code

    This fixes partially completed send()
    
Avoids holding the mutex during send()
    
fixes race conditions in error handling
    
removes copied non thread specific blocking code
    
Fixes deadlocks on closure
    
Fixes data loss on closure
    

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

  • ffmpeg filter_complex multiple overlays - why are they not syncing properly

    28 décembre 2023, par howdood

    I'm setting up live streaming using three overlaid inputs in ffmpeg. O:v is a webcam directly connected to the streaming box (a headless linux box) while 2:v and 3:v are ultra-low latency UDP streams from two remote R-Pis.

    &#xA;

    The filter_complex argument I'm using (that works, with all three video inputs perfectly in sync) is&#xA;[0:v] fifo [v1] ;[2:v] fifo [v2] ; [3:v] fifo [v3] ;[v1]setpts=PTS-STARTPTS[sync1] ;[v2]setpts=PTS-STARTPTS[sync2] ; [v3]setpts=PTS-STARTPTS+5/TB [sync3] ;[sync1][sync2] overlay=x=W-w:y=H-h [out1] ;[out1][sync3] overlay=x=0:y=H-h [vfinal]

    &#xA;

    Two questions about this :

    &#xA;

      &#xA;

    1. Why am I having to add +5/TB to [sync3] via setpts (in bold above) ? If I omit that, [3:v] is synced in to the stream noticeably ahead of the other two inputs. My best guess is that this may be to compensate for the processing time of the first overlay [sync1][sync2] which is introducing extra latency into that part of the stream. Is that right ?

      &#xA;

      2. &#xA;

    2. Importantly - the value of the extra pts compensation has to be dialed in by hand and will be specific to the underlying hardware used. Is there a way of getting ffmpeg to calculate this automatically so I don't have to worry about keeping in dialed in, in production ?

      &#xA;

      3. &#xA;

    &#xA;

    Thanks for reading ! I'm at the limit of the ffmpeg docs here...

    &#xA;

Navigation