Recherche avancée

Médias (0)

Mot : - Tags -/formulaire

Aucun média correspondant à vos critères n’est disponible sur le site.

Autres articles (4)

  • Use, discuss, criticize

    13 avril 2011, par

    Talk to people directly involved in MediaSPIP’s development, or to people around you who could use MediaSPIP to share, enhance or develop their creative projects.
    The bigger the community, the more MediaSPIP’s potential will be explored and the faster the software will evolve.
    A discussion list is available for all exchanges between users.

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

  • Le plugin : Podcasts.

    14 juillet 2010, par

    Le problème du podcasting est à nouveau un problème révélateur de la normalisation des transports de données sur Internet.
    Deux formats intéressants existent : Celui développé par Apple, très axé sur l’utilisation d’iTunes dont la SPEC est ici ; Le format "Media RSS Module" qui est plus "libre" notamment soutenu par Yahoo et le logiciel Miro ;
    Types de fichiers supportés dans les flux
    Le format d’Apple n’autorise que les formats suivants dans ses flux : .mp3 audio/mpeg .m4a audio/x-m4a .mp4 (...)

Sur d’autres sites (3058)

  • mpegvideo : allocate sufficiently large scratch buffer for interlaced vid

    16 mai 2013, par Jindrich Makovicka
    mpegvideo : allocate sufficiently large scratch buffer for interlaced vid

    MPV_decode_mb_internal needs 3 * 16 * linesize bytes of scratch buffer
    

    For interlaced content, linesize is multiplied by two after the allocation
    
of the scratch buffer, and the dest_cr pointer ends past the buffer.
    

    This patch makes ff_mpv_frame_size_alloc allocate a total of
    
(aligned line_size) * 2 * 16 * 3 bytes, which suffices even for the
    
interlaced case.
    

    CC:libav-stable@libav.org
    

    Signed-off-by : Jindrich Makovicka <makovick@gmail.com>
    
Signed-off-by : Anton Khirnov <anton@khirnov.net>
    • [DBH] libavcodec/mpegvideo.c

  • rtpdec_hevc : Drop extra sanity check for size of input packet

    9 mars 2015, par Vittorio Giovara
    rtpdec_hevc : Drop extra sanity check for size of input packet

    In this case len is always at least 3, since it is checked against
    
RTP_HEVC_PAYLOAD_HEADER_SIZE + 1 before entering the switch block.
    

    Bug-Id : CID 1238784
    • [DBH] libavformat/rtpdec_hevc.c

  • How to make a video out of images using ffmpeg without any extra frames getting added ?

    1er août 2019, par momo

    I currently used the following command to make a video out of some 200 images, from here, this forces the frame rate of the input file (valid for raw formats only) to 1 fps and the frame rate of the output file to 24 fps, and from here, when outputting H.264, adding -vf format=yuv420p or -pix_fmt yuv420p will ensure compatibility so crappy players can decode the video. :

    ffmpeg -r 1 -i img%03d.png -r 24 output.mp4 -pix_fmt yuv420p

    Now I thought this will simply take the frames and stack them one after another. But using the following command on the output video :

    ffprobe -show_frames output.mp4 > data.txt

    I get around 4640 frames,i.e. that many [FRAME]..[/FRAME] blocks,each having 28 lines in between the delimiters.

    Why does the number of frames increase so drastically ? What am I missing ? Also, using H.264 does it mean the some kind of video compression is taking place ? Because I only really want the images to be shown one after another without any extra processing.

Navigation