
Recherche avancée
Autres articles (72)
-
List of compatible distributions
26 avril 2011, parThe table below is the list of Linux distributions compatible with the automated installation script of MediaSPIP. Distribution nameVersion nameVersion number Debian Squeeze 6.x.x Debian Weezy 7.x.x Debian Jessie 8.x.x Ubuntu The Precise Pangolin 12.04 LTS Ubuntu The Trusty Tahr 14.04
If you want to help us improve this list, you can provide us access to a machine whose distribution is not mentioned above or send the necessary fixes to add (...) -
Les formats acceptés
28 janvier 2010, parLes 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 (...) -
Supporting all media types
13 avril 2011, parUnlike 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 (...)
Sur d’autres sites (7128)
-
fate : support testing of release branches
26 juillet 2014, par Janne Grunaufate : support testing of release branches
Adding ’branch=release/10’ to the fate config file will check the
release/10 branch instead of master. If no branch is specified it will
use ’master’ so that existing config are still valid.The server side changes are already deployed, see
https://fate.libav.org/v10/ for an example. The server supports only the
release/* branches.The server enforces that a single slot tests always the same branch.
Please append "-v$RELEASE" to the slot of release branch configs or make
the slot otherwise unique.A different fate samples dir is needed for each release branch. make
fate-rsync has the correct URL in each branch. -
version.sh : Print versions based on the last git tag for release branches
28 juillet 2014, par Michael Niedermayerversion.sh : Print versions based on the last git tag for release branches
release branches are detected by checking if "git" is not in RELEASE
This changes "N-64706-g2f71aeb" to "n2.3-8-g2f71aeb"
for git master theres no changeThis should improve the readability of lists of versions which come from
more than 1 release branch or master + release. fate.ffmpeg.org is
one possible exampleReviewed-by : Timothy Gu <timothygu99@gmail.com>
Signed-off-by : Michael Niedermayer <michaelni@gmx.at>
(cherry picked from commit ee606fd0317df202b59946cf9b738c0a01056316)Signed-off-by : Michael Niedermayer <michaelni@gmx.at>
-
FFmpeg iOS av_read_frame() hangs on cellular connections
8 novembre 2014, par MossI am able to play an RTMP audio + video stream on iOS. Works fantastic when everything is on a solid WiFi connection.
When I switch to a cellular connection (great signal strength and LTE/4G),
av_read_frame()
will intermittently block for an unacceptable amount of time. In some cases, I’ve clocked 30+ seconds of hang time before it moves on and grabs the next frame.I attempted a work-around by using the
AVIOInterruptCB
interrupt callback to abortav_read_frame()
if the function takes longer than 1 second to return.This definitely aborts
av_read_frame()
after 1 second, but unfortunately after I do this, future attempts to callav_read_frame()
result in EIO errors (-5), which indicates (to me) that the connection has been severed. So I am forced to reconnect withavformat_open_input()
( 3-4 seconds), and then find the stream info again ( 2-3 seconds), and then start reading frames again. This is much better than 10+ seconds of waiting around for the next frame, but it’s much worse than what I wish I could do, which is to just retry immediately and grab the next frame.That means, from a cellular user’s perspective, their video locks up intermittently for 5-10 seconds while we reconnect the stream in the background from scratch. Not a great user experience.
Is there a better way to manage
av_read_frame()
on a lossy cellular connection ? Or at least improve the reconnect time ? Suggestions ?