Recherche avancée

Médias (1)

Mot : - Tags -/MediaSPIP

Autres articles (11)

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

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

  • avcodec/mpeg4videodec : Clear bits_per_raw_sample if it has originated from a previous...

    9 juin 2018, par Michael Niedermayer
    avcodec/mpeg4videodec : Clear bits_per_raw_sample if it has originated from a previous instance

    Fixes : assertion failure
    
Fixes : ffmpeg_crash_5.avi
    

    Found-by : Thuan Pham <thuanpv@comp.nus.edu.sg>, Marcel Böhme, Andrew Santosa and Alexandru Razvan Caciulescu with AFLSmart
    
Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>
    • [DH] libavcodec/mpeg4videodec.c

  • Supported audio and video formats in Windows Store apps

    27 décembre 2013, par TheQuestioner

    I searched a lot on the internet and I know that this problem has been discussed on several forums, but because I am making a media player and I intend to sell it, I fell the need to ask for a more complete answer.
    As I understand, this is the list with the audio and video formats available in Windows Store Apps : http://msdn.microsoft.com/en-us/library/windows/apps/hh986969.aspx. This are indeed the most used formats for playing audio and video, but I truly fell the lack of support for the .MKV files. So my questions are :

    1. Will Microsoft include .MKV in that list ? When ?
    2. Can I somehow include the .MKV codec in my app ? (or other codecs, like .flv)
    3. If I can't add the MKV codec in my app and Microsoft doesn't intend to add it, is there a way that I can convert the .MKV in , let's say, a .MP4 so that my app can be able to play it ?

    I know that I'm not the first that asks this questions, but I didn't find anywhere a good/complete answer or solution to this problem.

    In my opinion .MKV in pretty popular already. Searching for media players in the Windows Store I found one which claims that it supports .MKV (but only if you buy it, so I didn't try it). So is this possible ? How ?

  • Fragmented MP4 : TrackFragHeader TFHD must have TrackID, is this in the spec ?

    27 juillet 2021, par Penquin

    I'm building a fragmented mp4 muxer and noticed that the track id is repeated inside the TFHD.&#xA;If the video does not have this undocumented track id, it will simply not play.

    &#xA;

    Here's an example of a muxer adding it :&#xA;https://github.com/edgeware/mp4ff/blob/bb9320744777dc97f18034c8aed45a9bcdbaa995/mp4/tfhd.go#L154

    &#xA;

    I was relying on the open spec provided by Microsoft :&#xA;https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-sstr/513ea48c-9a57-4792-a32a-fb6202ce2a58

    &#xA;

    Is this an addition to the spec ? Is the spec provided by Microsoft wrong ?

    &#xA;

Navigation