
Recherche avancée
Autres articles (104)
-
Encoding and processing into web-friendly formats
13 avril 2011, parMediaSPIP automatically converts uploaded files to internet-compatible formats.
Video files are encoded in MP4, Ogv and WebM (supported by HTML5) and MP4 (supported by Flash).
Audio files are encoded in MP3 and Ogg (supported by HTML5) and MP3 (supported by Flash).
Where possible, text is analyzed in order to retrieve the data needed for search engine detection, and then exported as a series of image files.
All uploaded files are stored online in their original format, so you can (...) -
MediaSPIP v0.2
21 juin 2013, parMediaSPIP 0.2 is the first MediaSPIP stable release.
Its official release date is June 21, 2013 and is announced here.
The zip file provided here only contains the sources of MediaSPIP in its standalone version.
To get a working installation, you must manually install all-software dependencies on the server.
If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...) -
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 (...)
Sur d’autres sites (6650)
-
avcodec/rv30 : Mark decoder as init-threadsafe
11 février 2022, par Andreas Rheinhardt -
avcodec/svq3 : Mark decoder as init-threadsafe
11 février 2022, par Andreas Rheinhardtavcodec/svq3 : Mark decoder as init-threadsafe
The only interesting thing done in SVQ3's init function
is using zlib, but this is fine : https://zlib.net/zlib_faq.html#faq21Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
-
ffmpeg segment_atclocktime inaccutare file segment BEFORE the *:00 mark
25 octobre 2017, par Soft StrategyI use ffmpeg to save a single RTSP stream on multiple files, one for every minute. The command is similar to this (I’ve simplified it) :
ffmpeg -y -i rtsp://IP/media.amp -c copy -r 15 -f segment -segment_time 60 -reset_timestamps 1 -segment_atclocktime 1 -strftime 1 outputFile%Y-%m-%d_%H-%M-%S.mp4
FFmpeg should create a new file every minute according to the following settings :
-segment_time 60 -segment_atclocktime 1
FFmpeg should create a new file every minute around the *:00 seconds mark. Because of busy CPU sometimes the file resets at *:01 seconds or even later which is fine. Rarely, the file is reset just before the *:00 mark, and the timestamp is *:59 of the same minute of the previous file.
The file timestamps looks like this :
outputFile2017-10-25_12-30-00.mp4
outputFile2017-10-25_12-30-59.mp4Instead it should be :
outputFile2017-10-25_12-30-00.mp4
outputFile2017-10-25_12-31-00.mp4Again, this happens very rarely but screwes up my timeline a bit and it looks like ffmpeg skipped a minute.
Is this normal ? Is there some settings to avoid this ?
Thanks in advance.