
Recherche avancée
Autres articles (33)
-
Use, discuss, criticize
13 avril 2011, parTalk to people directly involved in MediaSPIP’s development, or to people around you who could use MediaSPIP to share, enhance or develop their creative projects.
The bigger the community, the more MediaSPIP’s potential will be explored and the faster the software will evolve.
A discussion list is available for all exchanges between users. -
Sélection de projets utilisant MediaSPIP
29 avril 2011, parLes exemples cités ci-dessous sont des éléments représentatifs d’usages spécifiques de MediaSPIP pour certains projets.
Vous pensez avoir un site "remarquable" réalisé avec MediaSPIP ? Faites le nous savoir ici.
Ferme MediaSPIP @ Infini
L’Association Infini développe des activités d’accueil, de point d’accès internet, de formation, de conduite de projets innovants dans le domaine des Technologies de l’Information et de la Communication, et l’hébergement de sites. Elle joue en la matière un rôle unique (...) -
L’espace de configuration de MediaSPIP
29 novembre 2010, parL’espace de configuration de MediaSPIP est réservé aux administrateurs. Un lien de menu "administrer" est généralement affiché en haut de la page [1].
Il permet de configurer finement votre site.
La navigation de cet espace de configuration est divisé en trois parties : la configuration générale du site qui permet notamment de modifier : les informations principales concernant le site (...)
Sur d’autres sites (6248)
-
Manually feeding x264 with my own motion data ?
6 septembre 2011, par ldoogyI am trying to encode a stream using x264 (by feeding individual images), but what's unusual is that I already have some motion information for my frames. I know exactly which areas have been modified in each frame, and I know where motion has occurred in the frame.
Is there a way to feed x264 my own motion information ? I'd like to give it motion vectors for given areas in the frame, and somehow tell it that certain areas in the frame are guaranteed to not have had any motion in them.
I think this might significantly improve the performance of the encoding (because I'm allowing the codec to completely skip the motion estimation phase), and should also somewhat increase quality in cases where the encoder's motion estimation algos might have missed the motion that actually occurred.
Do I need to modify the encoder in order to do this, or is this supported in the existing API ?
-
Revision 096eaba728 : Remove VP8 save_reg_neon function This patch did a cleanup following the commit
29 avril 2014, par Yunqing WangChanged Paths :
Delete /vp8/common/arm/neon/save_reg_neon.asm
Modify /vp8/decoder/onyxd_if.c
Modify /vp8/encoder/onyx_if.c
Modify /vp8/vp8_common.mk
Remove VP8 save_reg_neon functionThis patch did a cleanup following the commit "Save NEON registers
in VP8 NEON functions". The pushing/poping of callee-saved NEON
registers was moved into individual NEON functions. Therefore,
we don’t need to save those registers at the beginning of codec.
The related code was removed.Change-Id : I5648166514fc9beffb780aa138495597731f49ea
-
ffmpeg returns 'frame_pts' as unrecognized option
25 janvier 2018, par HélderEarlier today I posted a question about frame extration with keyframes per encoding order (here) and I tried to run the command provided in one of the answers but ffmpeg returns :
Unrecognized option 'frame_pts'.
Error splitting the argument list : Option not found
Any clue how to make ffmpeg to recognize ’frame_pts’ option ?
The full command that I ran is :ffmpeg -i input.mp4 "select='eq(pict_type\,I)" -vsync 0 -frame_pts 1 thumbnails-%02d-I.png