
Recherche avancée
Autres articles (107)
-
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 (...) -
Multilang : améliorer l’interface pour les blocs multilingues
18 février 2011, parMultilang est un plugin supplémentaire qui n’est pas activé par défaut lors de l’initialisation de MediaSPIP.
Après son activation, une préconfiguration est mise en place automatiquement par MediaSPIP init permettant à la nouvelle fonctionnalité d’être automatiquement opérationnelle. Il n’est donc pas obligatoire de passer par une étape de configuration pour cela. -
Supporting all media types
13 avril 2011, parUnlike most software and media-sharing platforms, MediaSPIP aims to manage as many different media types as possible. The following are just a few examples from an ever-expanding list of supported formats : images : png, gif, jpg, bmp and more audio : MP3, Ogg, Wav and more video : AVI, MP4, OGV, mpg, mov, wmv and more text, code and other data : OpenOffice, Microsoft Office (Word, PowerPoint, Excel), web (html, CSS), LaTeX, Google Earth and (...)
Sur d’autres sites (18106)
-
Android built in Camera encoder VS FFMPEG --- Speed
3 novembre 2015, par user3903275How does recording a 1080P, H264 encoded video in android camera application is realtime fast but encoding a video in android using FFMPEG is slow at the same video size ?
I know FFMPEG is a software level encoder and it wont support any hardware features.
I know camera applications directly get buffer data from camera driver.
But actually where the difference happens ??
Why camera application is Realtime fast ???
Does it use GPU and OpenGL features of the phone to encode the video so that its so realtime fast ??
Because both Camera Application and FFMPEG runs on same mobile but still camera encodes H264 realtime ???
-
Revision 62c6411820 : Remove neon version of vp8 extend borders The code fails the unit test. Speed c
24 juillet 2014, par JohannChanged Paths :
Modify /test/scale_border_test.cc
Delete /vpx_scale/arm/neon/vp8_vpxyv12_extendframeborders_neon.asm
Modify /vpx_scale/arm/neon/yv12extend_arm.c
Modify /vpx_scale/vpx_scale.mk
Modify /vpx_scale/vpx_scale_rtcd.pl
Remove neon version of vp8 extend bordersThe code fails the unit test. Speed comparisons to the C are invalid
because the code frequently didn’t correctly extend the right and
bottom portions of the frame.Reduce maximum frame size on ARM devices to avoid OOM
Change-Id : Ia664c86406f0bb8120fd7ad401f32d0bd44994fb
-
Revision 51c60a891e : make default_interp_filter choice a speed feature This commit changed the hard-
16 juillet 2014, par Yaowu XuChanged Paths :
Modify /vp9/encoder/vp9_encoder.c
Modify /vp9/encoder/vp9_speed_features.c
Modify /vp9/encoder/vp9_speed_features.h
make default_interp_filter choice a speed featureThis commit changed the hard-coded DEFAULT_INTERP_FILTER to a speed
feature with the same default value : SWITCHABLE.Change-Id : I7f54f40f1bd3f5277841d04b85db7a84e47313f1