
Recherche avancée
Autres articles (81)
-
MediaSPIP version 0.1 Beta
16 avril 2011, parMediaSPIP 0.1 beta est la première version de MediaSPIP décrétée comme "utilisable".
Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
Pour avoir une installation fonctionnelle, il est nécessaire d’installer manuellement l’ensemble des dépendances logicielles sur le serveur.
Si vous souhaitez utiliser cette archive pour une installation en mode ferme, il vous faudra également procéder à d’autres modifications (...) -
MediaSPIP 0.1 Beta version
25 avril 2011, parMediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
The zip file provided here only contains the sources of MediaSPIP in its standalone version.
To get a working installation, you must manually install all-software dependencies on the server.
If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...) -
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 (...)
Sur d’autres sites (10442)
-
sws_scale performance comparison to media players real time resize
14 juillet 2018, par Andrey KatkovWhile playing 4K video user can resize players window - and result image will be scaled smoothly in run time.
On the other hand - program written with libav which reads 4k video file frame by frame and scale it down with sws_scale function do it less effective : it took more time then video duration to resize it.
Why is it so ? Maybe because player fps is less and some frames are skipped - but video still looks smooth ?
-
Revision 360c80cfb9 : Use fast HEX search in real time mode In good quality mode motion search, the b
15 février 2014, par Yunqing WangChanged Paths :
Modify /vp9/encoder/vp9_mcomp.c
Modify /vp9/encoder/vp9_mcomp.h
Modify /vp9/encoder/vp9_onyx_if.c
Modify /vp9/encoder/vp9_onyx_int.h
Modify /vp9/encoder/vp9_rdopt.c
Use fast HEX search in real time modeIn good quality mode motion search, the best matches are normally
found after searching in a large area. In real time mode, to make
encoding fast, a center-biased fast HEX search is used, which
converges quickly most of the time. A 4-point diamond search is
also carried out as the following refining search, which gives more
precise results, and maintains good motion search quality.At speed 5, the borg test on rtc set showed an overall PSNR loss of
0.936%. The encoding speed gain is 4% - 5%.Change-Id : I42cd68bb56a09ca1b86293c99d5f7312225ca7ae
-
FFMPEG API real-time encoding, skipped frames
24 octobre 2015, par Paul KnopfI am using FFMPEG to encode live video. If I can’t keep up with the live encoding, I need to drop frames. Currently, I just skip the encoding of a raw frame, and the PTS for the next frame is the same. Meaning, even if there is a skipped frame, the pts is always 1,2,3,4,5,6....
This causes the playback of the file to skip ahead in time. Instead, I would like to add blank frames to the muxed file. I tried making PTS indicate a skipped frame by setting it to 1,2,4,5,8,...., but the FFMPEG h264 encoders depend on PTS being consecutive.
How do I pass empty data to my mp4/container, indicating a blank space in time, so that decoders won’t appear to jump ahead in time, but instead just see a delay/freeze.