
Recherche avancée
Médias (1)
-
Sintel MP4 Surround 5.1 Full
13 mai 2011, par
Mis à jour : Février 2012
Langue : English
Type : Video
Autres articles (112)
-
Contribute to a better visual interface
13 avril 2011MediaSPIP is based on a system of themes and templates. Templates define the placement of information on the page, and can be adapted to a wide range of uses. Themes define the overall graphic appearance of the site.
Anyone can submit a new graphic theme or template and make it available to the MediaSPIP community. -
De près ou de loin...
29 avril 2011, parIls ne le savent pas forcément mais sont indispensables
MediaSPIP est un logiciel open-source, il se base sur d’autres logiciels, et d’autres logiciels lui sont également nécessaires pour fonctionner ... Les personnes ici listées ne savent pas forcément qu’elles ont un rôle important dans le développement, elles ont apporté leur connaissances dans le cadre de la création d’une partie de ces éléments nécessaires ou ont écrit des articles permettant de comprendre certaines choses... il semble indispensable (...) -
Liste des distributions compatibles
26 avril 2011, parLe tableau ci-dessous correspond à la liste des distributions Linux compatible avec le script d’installation automatique de MediaSPIP. Nom de la distributionNom de la versionNuméro de version 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
Si vous souhaitez nous aider à améliorer cette liste, vous pouvez nous fournir un accès à une machine dont la distribution n’est pas citée ci-dessus ou nous envoyer le (...)
Sur d’autres sites (5588)
-
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.
-
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 ?
-
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>