
Recherche avancée
Autres articles (48)
-
La file d’attente de SPIPmotion
28 novembre 2010, parUne file d’attente stockée dans la base de donnée
Lors de son installation, SPIPmotion crée une nouvelle table dans la base de donnée intitulée spip_spipmotion_attentes.
Cette nouvelle table est constituée des champs suivants : id_spipmotion_attente, l’identifiant numérique unique de la tâche à traiter ; id_document, l’identifiant numérique du document original à encoder ; id_objet l’identifiant unique de l’objet auquel le document encodé devra être attaché automatiquement ; objet, le type d’objet auquel (...) -
Monitoring de fermes de MediaSPIP (et de SPIP tant qu’à faire)
31 mai 2013, parLorsque l’on gère plusieurs (voir plusieurs dizaines) de MediaSPIP sur la même installation, il peut être très pratique d’obtenir d’un coup d’oeil certaines informations.
Cet article a pour but de documenter les scripts de monitoring Munin développés avec l’aide d’Infini.
Ces scripts sont installés automatiquement par le script d’installation automatique si une installation de munin est détectée.
Description des scripts
Trois scripts Munin ont été développés :
1. mediaspip_medias
Un script de (...) -
Encoding and processing into web-friendly formats
13 avril 2011, parMediaSPIP automatically converts uploaded files to internet-compatible formats.
Video files are encoded in MP4, Ogv and WebM (supported by HTML5) and MP4 (supported by Flash).
Audio files are encoded in MP3 and Ogg (supported by HTML5) and MP3 (supported by Flash).
Where possible, text is analyzed in order to retrieve the data needed for search engine detection, and then exported as a series of image files.
All uploaded files are stored online in their original format, so you can (...)
Sur d’autres sites (7405)
-
avcodec/aacenc_is : replace pow(x, 0.75) by x/sqrtf(sqrtf(x))
14 janvier 2016, par Claudio Freireavcodec/aacenc_is : replace pow(x, 0.75) by x/sqrtf(sqrtf(x))
This is quite an accurate approximation ; testing shows 2ulp error in
the floating point result. Tested with FATE.Alternatively, if one wants "full accuracy", one can use powf, or sqrt
instead of sqrtf. With powf, one gets 1 ulp error (theoretically should be 0, as
0.75 is exactly representable) on GNU libm, with sqrt, 0 ulp error.Signed-off-by : Ganesh Ajjanagadde <gajjanagadde@gmail.com>
Abstracted into pos_pow34 utility function
Signed-off-by : Claudio Freire <klaussfreire@gmail.com>
-
avcodec/mpegaudio_tablegen : speed up dynamic table creation
25 novembre 2015, par Ganesh Ajjanagaddeavcodec/mpegaudio_tablegen : speed up dynamic table creation
This does some miscellaneous stuff mainly avoiding the usage of pow to
achieve significant speedups. This is not speed critical, but is
unnecessary latency and cycles wasted for a user.All tables tested and are identical to the old ones
(bit-exact even in floating point case).Sample benchmark (x86-64, Haswell, GNU/Linux) :
old :
102329530 decicycles in mpegaudio_tableinit, 1 runs, 0 skipsnew :
34111900 decicycles in mpegaudio_tableinit, 1 runs, 0 skipsReviewed-by : Ronald S. Bultje <rsbultje@gmail.com>
Signed-off-by : Ganesh Ajjanagadde <gajjanagadde@gmail.com> -
FFmpeg compilation warnings ATOMIC_VAR_INIT
2 août 2022, par YozWhile compiling ffmpeg (commit 1368b5a) with emscripten 3.1.17, there are two warnings, I would like the internet to help me better understand (I am not someone with deep c++ experience) :


fftools/ffmpeg.c:339:41: warning: macro 'ATOMIC_VAR_INIT' has been marked as deprecated [-Wdeprecated-pragma]
static atomic_int transcode_init_done = ATOMIC_VAR_INIT(0);
 ^
/home/XYZ/ffmpeg-wasm/modules/emsdk/upstream/lib/clang/15.0.0/include/stdatomic.h:50:41: note: macro marked 'deprecated' here
#pragma clang deprecated(ATOMIC_VAR_INIT)
 ^



I understand ATOMIC_VAR_INIT in this place is deprecated, but by which tool (emscripten, clang) ? And which party to be involved in the fix.


The other one is also interesting :


fftools/ffmpeg_filter.c:898:35: warning: floating-point comparison is always true; constant cannot be represented exactly in type 'float' [-Wliteral-range]
 if (audio_drift_threshold != 0.1)
 ~~~~~~~~~~~~~~~~~~~~~ ^ ~~~



The message and consequences are very clear. Whats not clear to me, is, if this is particular compiler issue, or code issue and which party to take care ?