
Recherche avancée
Autres articles (12)
-
Support de tous types de médias
10 avril 2011Contrairement à 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, 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 (...)
-
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 (6846)
-
checkasm : Add a "run-checkasm" make target
14 février 2024, par Martin Storsjöcheckasm : Add a "run-checkasm" make target
Contrary to the existing "fate-checkasm", this always prints the
tool output, and runs all tests at once instead of splitting it up
per target group. This is more useful when the user expects to
look directly at the tool output, instead of being part of a full
fate run.(On failure with the regular "make fate-checkasm" targets, none of
the tool output is printed, but stored in files. If run with reporting
set up to the FATE website, the individual failures are uploaded there,
but if it is run in some sort of other CI setup, the intermediate files
might not be available afterwards for inspection.)Signed-off-by : Martin Storsjö <martin@martin.st>
-
how to synchronize multiple rtsp streams using ffmpeg (or another tool ?)
23 janvier 2015, par user1913115i have several RTP/RTSP live streams that i need to capture to individual mp4 files. this is what i’m doing :
ffmpeg -i rtsp://source1/video \
-i rtsp://source2/video \
-i rtsp://source3/video \
-map 0 -codec copy out1.mp4
-map 1 -codec copy out2.mp4
-map 2 -codec copy out3.mp4which works fine except when packets/frames are dropped, i end up with 3 files of different lengths. e.g. after an hour of capture, i may have this :
out1.mp4 - 59m58s
out2.mp4 - 59m30s
out3.mp4 - 56m41s
when looking at ffmpeg output i see this periodically :
[NULL @ 0x7ff8c3843600] RTP: missed 8 packets
[NULL @ 0x7ff8c3843600] RTP: missed 570 packets
[NULL @ 0x7ff8c3843600] SEI type 81 size 672 truncated at 264is there a way to synchronize these videos ? i.e. if a packet is dropped on source3 to drop same packets on source1 and source2 ? or repeat last received frame as many times as required on source3 to have videos in sync with each other ?
-
RuntimeException on FFmpegMediaMetaDataRetriever setDataSource (status = 0xFFFFFFFF)
27 septembre 2017, par LaVieEnRouxI am attempting to load a .mp4 video from assets. I am getting the following error at the top of the stack trace if I access either via URI or FileDescriptor :
java.lang.RuntimeException : setDataSource failed : status = 0xFFFFFFFF
at wseemann.media.FFmpegMediaMetadataRetriever.setDataSource(Native
Method)A little snippet of code that causes the exception :
mmr = new FFmpegMediaMetadataRetriever();
AssetManager assets = getAssets();
AssetFileDescriptor afd = assets.openFd(TEST_VIDEO);
mmr.setDataSource(afd.getFileDescriptor(), afd.getStartOffset(), afd.getLength());I’m using version 1.0.14 in Android Studio. I’ve tried using either the pre-built AAR or the compile ’com.github.wseemann:FFmpegMediaMetadataRetriever:1.0.14’ link in the build.gradle dependences, and both give the same result.
The curious thing is that this loads perfectly fine when I use MediaMetadataRetriever on the same video in place of FFmpegMediaMetadataRetriever. One of the videos with which the error was happening is available at the following link : https://drive.google.com/open?id=0B_r_uzvCTCgsS2xVMUk4TW13YUE
Anyone have suggestions ? I’d be using MediaMetadataRetriever instead but I need to be able to grab every individual frame of the video and it doesn’t appear to be capable.