
Recherche avancée
Médias (1)
-
MediaSPIP Simple : futur thème graphique par défaut ?
26 septembre 2013, par
Mis à jour : Octobre 2013
Langue : français
Type : Video
Autres articles (19)
-
Ajouter notes et légendes aux images
7 février 2011, parPour pouvoir ajouter notes et légendes aux images, la première étape est d’installer le plugin "Légendes".
Une fois le plugin activé, vous pouvez le configurer dans l’espace de configuration afin de modifier les droits de création / modification et de suppression des notes. Par défaut seuls les administrateurs du site peuvent ajouter des notes aux images.
Modification lors de l’ajout d’un média
Lors de l’ajout d’un média de type "image" un nouveau bouton apparait au dessus de la prévisualisation (...) -
ANNEXE : Les plugins utilisés spécifiquement pour la ferme
5 mars 2010, parLe site central/maître de la ferme a besoin d’utiliser plusieurs plugins supplémentaires vis à vis des canaux pour son bon fonctionnement. le plugin Gestion de la mutualisation ; le plugin inscription3 pour gérer les inscriptions et les demandes de création d’instance de mutualisation dès l’inscription des utilisateurs ; le plugin verifier qui fournit une API de vérification des champs (utilisé par inscription3) ; le plugin champs extras v2 nécessité par inscription3 (...)
-
Selection of projects using MediaSPIP
2 mai 2011, parThe examples below are representative elements of MediaSPIP specific uses for specific projects.
MediaSPIP farm @ Infini
The non profit organizationInfini develops hospitality activities, internet access point, training, realizing innovative projects in the field of information and communication technologies and Communication, and hosting of websites. It plays a unique and prominent role in the Brest (France) area, at the national level, among the half-dozen such association. Its members (...)
Sur d’autres sites (4500)
-
CentOS 7.4.1708 : ERROR : x265 not found using pkg-config
16 novembre 2017, par AdrianI’m trying to compile ffmpeg with Nvidia support following the guides on https://trac.ffmpeg.org/wiki/CompilationGuide/Centos and https://developer.nvidia.com/ffmpeg. I’ve ended up with the following command :
PATH="$HOME/bin:$PATH" PKG_CONFIG_PATH="$HOME/ffmpeg_build/lib/pkgconfig" ./configure --enable-pthreads --disable-w32threads --prefix="$HOME/ffmpeg_build" --pkg-config-flags="--static" --extra-cflags="-I$HOME/ffmpeg_build/include -I/usr/local/cuda/include" --extra-ldflags="-L$HOME/ffmpeg_build/lib -L/usr/local/cuda/lib64" --extra-libs='-lpthread -lm' --bindir="$HOME/bin" --enable-gpl --enable-libfdk_aac --enable-libfreetype --enable-libmp3lame --enable-libopus --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libx265 --enable-nonfree --enable-cuda --enable-cuvid --enable-nvenc --enable-nonfree --enable-libnpp
I’m getting the wonderful error
ERROR : x265 not found using pkg-config
looking in
ffbuild/config.log
reveals the following error :gcc -D_ISOC99_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_POSIX_C_SOURCE=200112 -D_XOPEN_SOURCE=600 -I/home/agilbert/ffmpeg_build/include -I/usr/local/cuda/include -std=c11 -fomit-frame-pointer -pthread -I/home/agilbert/ffmpeg_build/include -I/usr/include/freetype2 -I/home/agilbert/ffmpeg_build/include/opus -I/home/agilbert/ffmpeg_build/include/opus -I/home/agilbert/ffmpeg_build/include -I/home/agilbert/ffmpeg_build/include -I/home/agilbert/ffmpeg_build/include -I/home/agilbert/ffmpeg_build/include -I/home/agilbert/ffmpeg_build/include -I/home/agilbert/ffmpeg_build/include -I/home/agilbert/ffmpeg_build/include -I/home/agilbert/ffmpeg_build/include -L/home/agilbert/ffmpeg_build/lib -c -o /tmp/ffconf.MfrVBc4k/test.o /tmp/ffconf.MfrVBc4k/test.c
In file included from /tmp/ffconf.MfrVBc4k/test.c:1:0:
/home/agilbert/ffmpeg_build/include/x265.h:1753:40: error: expected ';', ',' or ')' before '&' token
FILE* x265_csvlog_open(const x265_param& param);
^
/home/agilbert/ffmpeg_build/include/x265.h:1757:40: error: expected ';', ',' or ')' before '&' token
void x265_csvlog_frame(const x265_param& param, const x265_picture& pic);
^
/home/agilbert/ffmpeg_build/include/x265.h:1762:64: error: expected ';', ',' or ')' before '&' token
void x265_csvlog_encode(x265_encoder *encoder, const x265_stats& stats, int argc, char** argv);
^
/home/agilbert/ffmpeg_build/include/x265.h:1766:36: error: expected ';', ',' or ')' before '&' token
void x265_dither_image(x265_picture& pic, int picWidth, int picHeight, int16_t *errorBuf, int bitDepth);
^
/home/agilbert/ffmpeg_build/include/x265.h:1815:50: error: expected ';', ',' or ')' before '&' token
FILE* (*csvlog_open)(const x265_param&);
^
/home/agilbert/ffmpeg_build/include/x265.h:1816:51: error: expected ';', ',' or ')' before '&' token
void (*csvlog_frame)(const x265_param&, const x265_picture&);
^
/home/agilbert/ffmpeg_build/include/x265.h:1817:67: error: expected ';', ',' or ')' before '&' token
void (*csvlog_encode)(x265_encoder*, const x265_stats&, int, char**);
^
/home/agilbert/ffmpeg_build/include/x265.h:1818:47: error: expected ';', ',' or ')' before '&' token
void (*dither_image)(x265_picture&, int, int, int16_t*, int);
^
/home/agilbert/ffmpeg_build/include/x265.h:1820:1: warning: no semicolon at end of struct or union [enabled by default]
} x265_api;
^gcc version is gcc-4.8.5-16.el7.x86_64
As per a question below : Yes - x265 is installed as per https://trac.ffmpeg.org/wiki/CompilationGuide/Centos and yes pkg-config is finding it. The compilation error makes me think that I’m missing a flag to the —pkg-config-flags optnion, but I can’t find one that works.
Does anyone know what I should be passing to pkg-config to get it to enable x265 ?
-
ffmpeg blocky chroma decoding
12 septembre 2017, par noiseshaperI’m using ffmpeg-3.2.4-win32, static and dev versions from zeranoe page, to decode some h264 mp4 videos I have created with x264 encoder. The videos have lots of static zones, 2d videogame type.
When I decode their frames using either ffmpeg.exe or avcodec_decode_video2() API function, I get poor chroma resolution, blocky and quite visible in the static zones of the video (edit : avcodec_decode_video2() returns correct YUV, the problem is the YUV->RGB conversion, see my own answer).
Strangely, with ffmpeg.exe I get poor chroma only if I output the frames to png, but if I output them to jpg, chroma seems much better.
The videos are 30 fps full hd videos created from static images or from Lagarith RGB captures, converted to YUV with Rec.709 colormatrix and then input to x264.exe using crf 20 and baseline profile. Using high profile makes no difference in my tests (edit : irrelevant, since the problem is in the YUV->RGB conversion).
If I play a mp4 video with ffplay.exe or MPC HC + LAV decoder, the chroma is good, nearly equal to the uncompressed YUV 4:2:0 version.
Here is an example of the same frame obtained from a mp4 video created with a static image, the output frame is zoomed in to clearly see the effect.
https://drive.google.com/file/d/0B5KI1D-N1kHpV3lGaERJRjNkcms/view
1 : Original frame before compressing.
2 : YUV 4:2:0 conversion before compressing
3 : Video output from MPC HC + LAV decoder. ffplay output looks the same.
4 : Video frames decoded with ffmpeg.exe to jpeg, some jpeg macroblocking is visible.
5 : Video frames decoded with ffmpeg.exe to png, very blocky chroma. Using avcodec_decode_video2() function, the YUV output or its conversion to RGB produces the same blocky chroma.
The command lines for decoding the frames to jpg and png are these :
ffmpeg -i testcase.mp4 -vf colormatrix=bt709:bt601 -vframes 5 -qscale:v 2 output%03d.jpg
ffmpeg -i testcase.mp4 -vf colormatrix=bt709:bt601 -vframes 5 output%03d.png
You can download mp4 and bat files that showcase the effect here :
https://drive.google.com/drive/folders/0B5KI1D-N1kHpcUdGd2IyM2pXMTg
I have tried with ffmpeg 3.2, but same thing happens.
-
Revision f35b0e80919311d791d278836f6485322c6ad561 : Passage en minuscule des noms de serveurs : [14467] était effectivement ...
2 octobre 2010, par Committo,Ergo:sum — LogPassage en minuscule des noms de serveurs : [14467] était effectivement sale et brutal, puisque URL_PAGE ne fonctionnait plus du tout sur un connect avec une majuscule, et il doit y avoir d’autres problèmes car l’oubli était chronique dans le code, on répercute. Ce dépôt corrige également l’autre bug (...)