
Recherche avancée
Autres articles (61)
-
Submit bugs and patches
13 avril 2011Unfortunately a software is never perfect.
If you think you have found a bug, report it using our ticket system. Please to help us to fix it by providing the following information : the browser you are using, including the exact version as precise an explanation as possible of the problem if possible, the steps taken resulting in the problem a link to the site / page in question
If you think you have solved the bug, fill in a ticket and attach to it a corrective patch.
You may also (...) -
Les images
15 mai 2013 -
Taille des images et des logos définissables
9 février 2011, parDans beaucoup d’endroits du site, logos et images sont redimensionnées pour correspondre aux emplacements définis par les thèmes. L’ensemble des ces tailles pouvant changer d’un thème à un autre peuvent être définies directement dans le thème et éviter ainsi à l’utilisateur de devoir les configurer manuellement après avoir changé l’apparence de son site.
Ces tailles d’images sont également disponibles dans la configuration spécifique de MediaSPIP Core. La taille maximale du logo du site en pixels, on permet (...)
Sur d’autres sites (11819)
-
lavu/hwcontext_vaapi : fix a race mapping to allow CSC to YUV420P
7 août, par nyanmisakalavu/hwcontext_vaapi : fix a race mapping to allow CSC to YUV420P
There's a race condition for YUV420P when mapping from pix_fmt
to VA fourcc, both I420 and YV12 could be found by pix_fmt.Currently, vaapi_get_image_format() iterates over the query results
of pix_fmt and returns the first matching result in the order
declared in the driver. This may result in an incorrect image_format.Now use fourcc to find the image_format.
Fixes :
ffmpeg -hwaccel vaapi -hwaccel_output_format vaapi -i INPUT \vf scale_vaapi=format=yuv420p,hwmap,format=yuv420p \
vframes 1 -f rawvideo -y yuv420p.yuv
Signed-off-by : nyanmisaka <nst799610810@gmail.com>
-
avcodec/mpeg4videoenc : Fix data race when using AC prediction
14 juin, par Andreas Rheinhardtavcodec/mpeg4videoenc : Fix data race when using AC prediction
The check for whether we can use the fast path to process
AC coefficients used the qscale value belonging to a different
slice ; this worked in practice, because the predicted AC values
are zero in this case, so it does not matter whether we use
the fast or the slow path.Fix this by checking for first_slice_line instead. This fixes all
the races in the encoding part of the vsynth*-mpeg4-thread tests
(and fixes them if no frame threading is in use for the decoding part).(The left prediction check may use data from a different slice, too,
but said slice is always processed by the same thread, so that no race
can happen. Given that out-of-slice AC values are zero, it does not
matter whether we use the fast path or the slow path either.)Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
-
fftools/resources/resman : Don't alloc ResourceManager, fix race
1er juin, par Andreas Rheinhardtfftools/resources/resman : Don't alloc ResourceManager, fix race
The resman_ctx pointer was accessed outside of its guarding
mutex.Also make the ResourceManager static.
Reviewed-by : softworkz . <softworkz-at-hotmail.com@ffmpeg.org>
Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@outlook.com>