
Recherche avancée
Médias (1)
-
Géodiversité
9 septembre 2011, par ,
Mis à jour : Août 2018
Langue : français
Type : Texte
Autres articles (70)
-
Websites made with MediaSPIP
2 mai 2011, parThis page lists some websites based on MediaSPIP.
-
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" (...) -
Publier sur MédiaSpip
13 juin 2013Puis-je poster des contenus à partir d’une tablette Ipad ?
Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir
Sur d’autres sites (7547)
-
av_seek_frame() Can't seek to the place I want
5 juillet 2022, par alexander chenI want to intercept a frame of my video file, so I used the
av_seek_frame
function, the timestamp value I tried usingtimestamp*AV_TIME_BASE
andtimestamp/(av_q2d(videostream->time_base)*av_TIME_BASE)
, but no matter what I use Which one, the obtained frame is always not what I want, and it is observed that the frame time that I want is very different (so the accuracy problem ofAVSEEK_FLAG_BACKWARD
is excluded here).
My code is as follows :


double tmp0 = timeStamp/(av_q2d(inputVideoStream->time_base)*AV_TIME_BASE);
// double tmp0 = timeStamp * AV_TIME_BASE;
code = av_seek_frame(inputAVFormatContext, videoStreamIndex, tmp0, AVSEEK_FLAG_BACKWARD);



-
vaapi_h265 : Fix slice header writing
30 septembre 2016, par Mark Thompsonvaapi_h265 : Fix slice header writing
This was not observed earlier because the only syntax element which
it normally misses with the current setup is slice_qp_delta, but that
is always going to be zero (in IDR frames QP isn’t varied on the
slice) which will always exp-golomb code as a single 1 bit. The
immediately following part is the byte alignment, which is always a 1
bit followed by 0s which are ignored, so as long as the bitstream is
never aligned at that point we will never notice because the only
difference is that an ignored bit is a 1 instead of a 0.(cherry picked from commit fc30a90898e419cee7c7cb496976da6337d0bf3e)
-
checkasm : lls : Use relative tolerances rather than absolute ones
4 octobre 2024, par Martin Storsjöcheckasm : lls : Use relative tolerances rather than absolute ones
Depending on the magnitude of the output values, the potential
errors can be larger.This fixes errors in the lls tests on x86_32 for some seeds,
observed with GCC 11 (on Ubuntu 22.04, with the distro compiler,
with -m32).Signed-off-by : Martin Storsjö <martin@martin.st>