
Recherche avancée
Autres articles (41)
-
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" (...) -
Contribute to a better visual interface
13 avril 2011MediaSPIP is based on a system of themes and templates. Templates define the placement of information on the page, and can be adapted to a wide range of uses. Themes define the overall graphic appearance of the site.
Anyone can submit a new graphic theme or template and make it available to the MediaSPIP community.
Sur d’autres sites (4384)
-
Understanding ffmpeg -benchmark results
6 septembre 2022, par Ivy GrowingAdding
-benchmark
flag toffmpeg
command resutls with addition of following 2 lines in the shell output :

bench: utime=10.125s stime=4.234s rtime=5.606s
bench: maxrss=110080kB



The
maxrss
serves to indicate the maximum RAM used during theffmpeg
execution. Theutime
,stime
,rtime
indicate accordingly :

- 

- user time ;
- system time ;
- real time.








I tried to understand the meaning of these times from the source code and failed. Please, help.


- 

- Which of these times indicate how much time was human waiting while the ffpmeg was processing the video ?
- Can this time be seen directly or it's a combination/calculation of these 3 parameters ?
- How it can be for certain videos
utime > rtime
and for othersutime < rtime
?








-
vaapi_h264 : Add trivial support for low-power encoding
18 mai 2016, par Mark Thompson -
pcx : Consume the whole packet if giving up due to missing palette
28 septembre 2013, par Martin Storsjöpcx : Consume the whole packet if giving up due to missing palette
Previously, we returned 0, meaning successful decoding but 0
bytes consumed, leading to an infinite loop.Reported-by : Mateusz "j00ru" Jurczyk and Gynvael Coldwind
CC : libav-stable@libav.org
Signed-off-by : Martin Storsjö <martin@martin.st>