
Recherche avancée
Médias (1)
-
Bug de détection d’ogg
22 mars 2013, par
Mis à jour : Avril 2013
Langue : français
Type : Video
Autres articles (28)
-
Submit bugs and patches
13 avril 2011Unfortunately a software is never perfect.
If you think you have found a bug, report it using our ticket system. Please to help us to fix it by providing the following information : the browser you are using, including the exact version as precise an explanation as possible of the problem if possible, the steps taken resulting in the problem a link to the site / page in question
If you think you have solved the bug, fill in a ticket and attach to it a corrective patch.
You may also (...) -
Emballe médias : à quoi cela sert ?
4 février 2011, parCe plugin vise à gérer des sites de mise en ligne de documents de tous types.
Il crée des "médias", à savoir : un "média" est un article au sens SPIP créé automatiquement lors du téléversement d’un document qu’il soit audio, vidéo, image ou textuel ; un seul document ne peut être lié à un article dit "média" ; -
Création définitive du canal
12 mars 2010, parLorsque votre demande est validée, vous pouvez alors procéder à la création proprement dite du canal. Chaque canal est un site à part entière placé sous votre responsabilité. Les administrateurs de la plateforme n’y ont aucun accès.
A la validation, vous recevez un email vous invitant donc à créer votre canal.
Pour ce faire il vous suffit de vous rendre à son adresse, dans notre exemple "http://votre_sous_domaine.mediaspip.net".
A ce moment là un mot de passe vous est demandé, il vous suffit d’y (...)
Sur d’autres sites (4421)
-
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>