
Recherche avancée
Autres articles (49)
-
Publier sur MédiaSpip
13 juin 2013Puis-je poster des contenus à partir d’une tablette Ipad ?
Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir -
(Dés)Activation de fonctionnalités (plugins)
18 février 2011, parPour gérer l’ajout et la suppression de fonctionnalités supplémentaires (ou plugins), MediaSPIP utilise à partir de la version 0.2 SVP.
SVP permet l’activation facile de plugins depuis l’espace de configuration de MediaSPIP.
Pour y accéder, il suffit de se rendre dans l’espace de configuration puis de se rendre sur la page "Gestion des plugins".
MediaSPIP est fourni par défaut avec l’ensemble des plugins dits "compatibles", ils ont été testés et intégrés afin de fonctionner parfaitement avec chaque (...) -
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 (...)
Sur d’autres sites (7649)
-
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>
-
avcodec/g729dec : Use 64bit and clip in scalar product
5 novembre 2019, par Michael Niedermayeravcodec/g729dec : Use 64bit and clip in scalar product
The G729 reference decoder clips after each individual operation and keeps track if overflow
occurred (in the fixed point implementation), this here is
simpler and faster but not 1:1 the same what the reference does.Non fuzzed samples which trigger any such overflow are welcome, so
the need and impact of different clipping solutions can be evaluated.Fixes : signed integer overflow : 1271483721 + 1073676289 cannot be represented in type 'int'
Fixes : 18617/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_ACELP_KELVIN_fuzzer-5137705679978496Found-by : continuous fuzzing process https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>