Recherche avancée

Médias (16)

Mot : - Tags -/mp3

Autres articles (17)

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

  • suitable video encoding for browsers

    26 juin 2022, par seriously

    I was researching how illegal movie streaming services handle all the traffic they get and to understand that I had to follow the steps they perform to get the video data to the users. I got to the stage of video transmission and noticed something that boggled me. Most of the illegal movie streaming sites get their movies/tv-shows through piracy/torrents and even most of the streamers are sister companies of the piracy websites. Now when I took a look at the video encodings of the torrent movies and shows they are h.265 but h.265 is not supported by popular browsers like chrome, firefox edge... Does this mean they (the streamers) have to re-encode every h.265 videos to avc/h.264 before they stream it ? If that's the case, that takes them a huge amount of time to convert their whole movie catalog to h.264 not to mention the space they require to save them. Am I taking a look at this the right way ? Do they really convert and store 2, 3 ... differently encoded video files and stream the suitable one ? Or can they somehow convert the chunks of data they are streaming to h.264 live simultaneously without having to store the h.264 formats hence saving conversion time and space ?

    


  • fate : Add a dependency on ffprobe for fate-flcl1905

    12 décembre 2024, par Martin Storsjö
    fate : Add a dependency on ffprobe for fate-flcl1905

    This fixes occasional failed tests, if doing "make fate" without a
    
regular "make" or "make all" inbetween.
    

    Signed-off-by : Martin Storsjö <martin@martin.st>
    • [DH] tests/fate/audio.mak

  • AIR - Transfer Bitmap data to FFmpeg video

    22 mars 2016, par mika

    Hey I’m running into a similar problem as : Converting RGB to YUV, + ffmpeg

    From AIR, I figured the encoding was too long to render frames at a reasonable rate - so I exported the argb ByteArray from bitmap.getPixels(rect) directly to a file.

    So for a 30sec flash animation, I’d export let’s say 1500 frames to 1500 .argb files.

    This method works great. I was able to render HD video using the ffmpeg cmd :

    ffmpeg -f image2 -pix_fmt argb -vcodec rawvideo -s 640x380 -i frame_%d.argb -r 24 -qscale 1.1 -s 640x380 -i ./music.mp3 -shortest render-high.mpg

    So far so good ! However, inbetween the two processes we need to store those 3gb of data.

    I then tried to append all the argb to one single file and have ffmpeg consume it, but didn’t get anything good out of it... Also tried messing tcp/udp but getting stuck...

    Does anyone know of a way to streamline that process and hopefully pipe both Air and ffmpeg together ?

Navigation