
Recherche avancée
Autres articles (99)
-
Support audio et vidéo HTML5
10 avril 2011MediaSPIP utilise les balises HTML5 video et audio pour la lecture de documents multimedia en profitant des dernières innovations du W3C supportées par les navigateurs modernes.
Pour les navigateurs plus anciens, le lecteur flash Flowplayer est utilisé.
Le lecteur HTML5 utilisé a été spécifiquement créé pour MediaSPIP : il est complètement modifiable graphiquement pour correspondre à un thème choisi.
Ces technologies permettent de distribuer vidéo et son à la fois sur des ordinateurs conventionnels (...) -
HTML5 audio and video support
13 avril 2011, parMediaSPIP uses HTML5 video and audio tags to play multimedia files, taking advantage of the latest W3C innovations supported by modern browsers.
The MediaSPIP player used has been created specifically for MediaSPIP and can be easily adapted to fit in with a specific theme.
For older browsers the Flowplayer flash fallback is used.
MediaSPIP allows for media playback on major mobile platforms with the above (...) -
MediaSPIP v0.2
21 juin 2013, parMediaSPIP 0.2 is the first MediaSPIP stable release.
Its official release date is June 21, 2013 and is announced here.
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 (...)
Sur d’autres sites (10004)
-
avfilter/buffersrc : make channel_layout a CHLAYOUT type AVOption
2 janvier, par James Almer -
Revision 35fadf1d25 : bilinearpredict_neon : fix type conversion warnings make bifilter4_coeff[][] uin
11 juillet 2014, par James ZernChanged Paths :
Modify /vp8/common/arm/neon/bilinearpredict_neon.c
bilinearpredict_neon : fix type conversion warningsmake bifilter4_coeff[][] uint8_t, no values exceed this range and
they’re loaded with vdup_n_u8().Change-Id : I921983e9edd828d29820e40ac30a7801dbe0fb4f
-
vp8 : change mv_{min,max}.{x,y} type to int
8 juin 2015, par Andreas Cadhalpunvp8 : change mv_min,max.x,y type to int
If one of the dimensions is larger than 8176, s->mb_width or
s->mb_height is larger than 511, leading to an int16_t overflow of
s->mv_max.x,y. This then causes av_clip to be called with amin > amax.Changing the type to int avoids the overflow and has no negative
effect, because s->mv_max is only used in clamp_mv for clipping.
Since mv_max.x,y is positive and mv_min.x,y negative, av_clip can’t
increase the absolute value. The input to av_clip is an int16_t, and
thus the output fits into int16_t as well.For additional safety, s->mv_min,max.x,y are clipped to int16_t range
before use.Reviewed-by : Ronald S. Bultje <rsbultje@gmail.com>
Signed-off-by : Andreas Cadhalpun <Andreas.Cadhalpun@googlemail.com>