Recherche avancée

Médias (3)

Mot : - Tags -/collection

Autres articles (21)

  • Participer à sa traduction

    10 avril 2011

    Vous pouvez nous aider à améliorer les locutions utilisées dans le logiciel ou à traduire celui-ci dans n’importe qu’elle nouvelle langue permettant sa diffusion à de nouvelles communautés linguistiques.
    Pour ce faire, on utilise l’interface de traduction de SPIP où l’ensemble des modules de langue de MediaSPIP sont à disposition. ll vous suffit de vous inscrire sur la liste de discussion des traducteurs pour demander plus d’informations.
    Actuellement MediaSPIP n’est disponible qu’en français et (...)

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

  • Les formats acceptés

    28 janvier 2010, par

    Les commandes suivantes permettent d’avoir des informations sur les formats et codecs gérés par l’installation local de ffmpeg :
    ffmpeg -codecs ffmpeg -formats
    Les format videos acceptés en entrée
    Cette liste est non exhaustive, elle met en exergue les principaux formats utilisés : h264 : H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 m4v : raw MPEG-4 video format flv : Flash Video (FLV) / Sorenson Spark / Sorenson H.263 Theora wmv :
    Les formats vidéos de sortie possibles
    Dans un premier temps on (...)

Sur d’autres sites (3450)

  • ffmpeg c++ API encode mpegts with KLV data stream

    4 mars 2016, par arms

    I need to encode an mpegts video using the ffmpeg C++ API. The output video shall have two streams : the first one shall be of type AVMEDIA_TYPE_VIDEO ; the second one shall be of type AVMEDIA_TYPE_DATA and shall contain a set of KLV data.

    I have written my own KLV library to manage the KLV format.

    However I’m not able to create "from scratch" a new video by combining the two streams. Following the implementation as in FFMPEG C api h.264 encoding / MPEG2 ts streaming problems I can successfully encode a mpegts video with a single video stream.

    However I’m not able to add a new AVMEDIA_TYPE_DATA stream to the output video since, as soon as I add a new data stream using methods like avformat_new_stream(...) the output video is empty : neither the data stream nor the video one are produced and the output file is empty.

    Can anyone suggest me a tutorial page or a sample on how to properly add a data stream to my output video in mpegts format ?

    Thanks a lot !

  • ffmpeg c++ API encode mpegts with KLV data stream

    29 novembre 2019, par arms

    I need to encode an mpegts video using the ffmpeg C++ API. The output video shall have two streams : the first one shall be of type AVMEDIA_TYPE_VIDEO ; the second one shall be of type AVMEDIA_TYPE_DATA and shall contain a set of KLV data.

    I have written my own KLV library to manage the KLV format.

    However I’m not able to create "from scratch" a new video by combining the two streams. Following the implementation as in FFMPEG C api h.264 encoding / MPEG2 ts streaming problems I can successfully encode a mpegts video with a single video stream.

    However I’m not able to add a new AVMEDIA_TYPE_DATA stream to the output video since, as soon as I add a new data stream using methods like avformat_new_stream(...) the output video is empty : neither the data stream nor the video one are produced and the output file is empty.

    Can anyone suggest me a tutorial page or a sample on how to properly add a data stream to my output video in mpegts format ?

    Thanks a lot !

  • FFmpeg can't decode H264 stream/frame data

    31 juillet 2015, par Gediminas

    Recently I had chance to work with two devices that are streaming the H264 through RTSP.
    And I’ve ran into some problem trying to decompress this stream using FFmpeg library.

    Every time the "avcodec_decode_video2" is called - FFmpeg just says something like :

    [h264 @ 00339220] no frame !

    My raw H264 stream I frame data starts like this : "65 88 84 21 3F F8 F8 0D..."
    (as far as I understand this 0x65 indicates that it’s a IDR frame ?)

    Other frames for one device starts like : "41 9A 22 07 F3 4E 48 CC...."

    and for other device - like this : "61 9A 25 C1 1C 45 62 39...."

    • Am I missing some frame data here ?
    • Does FFmpeg needs to have some extra parameters set up ?

    I was expecting at least "00 00 00 01" bytes at the start for the frame data... but this is what I’ve got..

Navigation