
Recherche avancée
Autres articles (99)
-
MediaSPIP 0.1 Beta version
25 avril 2011, parMediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
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 (...) -
Personnaliser en ajoutant son logo, sa bannière ou son image de fond
5 septembre 2013, parCertains thèmes prennent en compte trois éléments de personnalisation : l’ajout d’un logo ; l’ajout d’une bannière l’ajout d’une image de fond ;
-
Multilang : améliorer l’interface pour les blocs multilingues
18 février 2011, parMultilang est un plugin supplémentaire qui n’est pas activé par défaut lors de l’initialisation de MediaSPIP.
Après son activation, une préconfiguration est mise en place automatiquement par MediaSPIP init permettant à la nouvelle fonctionnalité d’être automatiquement opérationnelle. Il n’est donc pas obligatoire de passer par une étape de configuration pour cela.
Sur d’autres sites (11329)
-
Is it possible to link FFmpeg statically into an application built with Visual C++ ?
29 juillet 2013, par Richard NZI'm currently building and using FFmpeg on Windows and it works nicely. At present there are 5 relevant DLLs which I load and map relevant functions in as needed. However I am wondering if it is possible to avoid these DLLs by linking FFmpeg statically ?
My initial reaction is probably not, because the FFmpeg builds are done with MinGW's GCC and any static libraries generated by those tools will be in a format incompatible with Visual C++. If anyone has looked into this before I'd be curious to know if you had any luck ?
I did find this tool : http://www.binary-soft.com/dll2lib/dll2lib.htm. It's expensive but looks like it might do the trick as it converts a DLL directly to a static library.
Thanks.
-
h264 decoding rtsp link error
13 août 2015, par Yasin SOYASLANI am receiving RTSP stream with live555 library and decode them with ffmpeg.
At first, i couldnt decode data’s that come from live555. After a little search i learned that I needed to include the sequence (SPS) and picture parameter sets (PPS) for my frame data before sending frame to the FFmpeg.header : 00 00 00 01 67 4d 00 14 95 b8 58 25 90 00 00 00 01 68 ee 3c 80 00 00 00 01
FFmpeg can’t decode H264 stream/frame data
Now i can take frame but a tiny problem comes out. [![enter image description here][1]][1]
3 packets still have problem. FFmpeg cant decode them i am suggesting they are special command. Because they are so small 9,4 and 5 byte come.
Here they are
[h264 @ 0x137c00] no frame !
00 00 00 01 67 4d 00 14 95 b8 58 25 90 00 00 00 01 68 ee 3c 80 00 00 00 01 67 4d 00 14 95 b8 58 25 90
[h264 @ 0x137c00] no frame !
00 00 00 01 67 4d 00 14 95 b8 58 25 90 00 00 00 01 68 ee 3c 80 00 00 00 01 68 ee 3c 80
[h264 @ 0x137c00] no frame !
00 00 00 01 67 4d 00 14 95 b8 58 25 90 00 00 00 01 68 ee 3c 80 00 00 00 01 06 e5 01 ec 80
[h264 @ 0x137c00] no frame !any suggestion ?
-
lavfi : use a video frame pool for each link of the filtergraph
11 décembre 2015, par Matthieu Bouron