
Recherche avancée
Autres articles (71)
-
Websites made with MediaSPIP
2 mai 2011, parThis page lists some websites based on MediaSPIP.
-
Amélioration de la version de base
13 septembre 2013Jolie sélection multiple
Le plugin Chosen permet d’améliorer l’ergonomie des champs de sélection multiple. Voir les deux images suivantes pour comparer.
Il suffit pour cela d’activer le plugin Chosen (Configuration générale du site > Gestion des plugins), puis de configurer le plugin (Les squelettes > Chosen) en activant l’utilisation de Chosen dans le site public et en spécifiant les éléments de formulaires à améliorer, par exemple select[multiple] pour les listes à sélection multiple (...) -
Creating farms of unique websites
13 avril 2011, parMediaSPIP platforms can be installed as a farm, with a single "core" hosted on a dedicated server and used by multiple websites.
This allows (among other things) : implementation costs to be shared between several different projects / individuals rapid deployment of multiple unique sites creation of groups of like-minded sites, making it possible to browse media in a more controlled and selective environment than the major "open" (...)
Sur d’autres sites (15332)
-
libavutil/hwcontext_qsv : fix a bug for mapping vaapi frame to qsv
16 novembre 2021, par nyanmisakalibavutil/hwcontext_qsv : fix a bug for mapping vaapi frame to qsv
The data stored in data[3] in VAAPI AVFrame is VASurfaceID while
the data stored in pair->first is the pointer of VASurfaceID, so
we need to do cast to make following commandline works :ffmpeg -hwaccel vaapi -hwaccel_device /dev/dri/renderD128 \
hwaccel_output_format vaapi -i input.264 \
vf "hwmap=derive_device=qsv,format=qsv" -c:v h264_qsv output.264
Signed-off-by : nyanmisaka <nst799610810@gmail.com>
Signed-off-by : Wenbin Chen <wenbin.chen@intel.com>
Signed-off-by : Anton Khirnov <anton@khirnov.net> -
libavfilter/scale : Populate ow/oh when using 0 as w/h
14 juin 2017, par Kevin Marklibavfilter/scale : Populate ow/oh when using 0 as w/h
The input width and height is known at parse time so there's no
reason ow/oh should not be usable when using 0 as the width or
height expression.Previously in "scale=0:ow" ow would be set to "0" which works,
conveniently, as "scale=0:0" is perfectly valid input but this breaks
down when you do something like "scale=0:ow/4" which one could
reasonably expect to work as well, but does not as ow is 0 not the
real value.This change handles the 0 case for w/h immediately so the ow/oh
variables work as expected. Consequently, the rest of the code does
not need to handle 0 input. w/h will always be > 0 or < 0.The second explicit (int) cast ensures that ow/oh appear as integers
as a user might expect when dealing with pixel dimensions.Signed-off-by : Kevin Mark <kmark937@gmail.com>
Signed-off-by : Ronald S. Bultje <rsbultje@gmail.com> -
ffv1 : Drop unnecessary casts and const qualifiers to match function signatures
18 décembre 2014, par Diego Biurrun