
Recherche avancée
Autres articles (16)
-
Utilisation et configuration du script
19 janvier 2011, parInformations spécifiques à la distribution Debian
Si vous utilisez cette distribution, vous devrez activer les dépôts "debian-multimedia" comme expliqué ici :
Depuis la version 0.3.1 du script, le dépôt peut être automatiquement activé à la suite d’une question.
Récupération du script
Le script d’installation peut être récupéré de deux manières différentes.
Via svn en utilisant la commande pour récupérer le code source à jour :
svn co (...) -
Encoding and processing into web-friendly formats
13 avril 2011, parMediaSPIP automatically converts uploaded files to internet-compatible formats.
Video files are encoded in MP4, Ogv and WebM (supported by HTML5) and MP4 (supported by Flash).
Audio files are encoded in MP3 and Ogg (supported by HTML5) and MP3 (supported by Flash).
Where possible, text is analyzed in order to retrieve the data needed for search engine detection, and then exported as a series of image files.
All uploaded files are stored online in their original format, so you can (...) -
List of compatible distributions
26 avril 2011, parThe table below is the list of Linux distributions compatible with the automated installation script of MediaSPIP. Distribution nameVersion nameVersion number Debian Squeeze 6.x.x Debian Weezy 7.x.x Debian Jessie 8.x.x Ubuntu The Precise Pangolin 12.04 LTS Ubuntu The Trusty Tahr 14.04
If you want to help us improve this list, you can provide us access to a machine whose distribution is not mentioned above or send the necessary fixes to add (...)
Sur d’autres sites (4643)
-
lavf : Add an MPEG-DASH ISOFF segmenting muxer
6 octobre 2014, par Martin Storsjölavf : Add an MPEG-DASH ISOFF segmenting muxer
This is mostly to serve as a reference example on how to segment
the output from the mp4 muxer, capable of writing the segment
list in four different ways :SegmentTemplate with SegmentTimeline
SegmentTemplate with implicit segments
SegmentList with individual files
SegmentList with one single file per track, and byte ranges
The muxer is able to serve live content (with optional windowing)
or create a static segmented MPD.In advanced cases, users will probably want to do the segmenting
in their own application code.Signed-off-by : Martin Storsjö <martin@martin.st>
-
lavu : add an API function to return the Libav version string
2 juillet 2015, par wm4lavu : add an API function to return the Libav version string
This returns something like "v12_dev0-1332-g333a27c". This is much more
useful than the individual library versions, of which there are too
many, and which are very hard to map back to releases or git commits.Signed-off-by : Janne Grunau <janne-libav@jannau.net>
-
arm : Add NEON optimizations for 10 and 12 bit vp9 loop filter
5 janvier 2017, par Martin Storsjöarm : Add NEON optimizations for 10 and 12 bit vp9 loop filter
This work is sponsored by, and copyright, Google.
This is pretty much similar to the 8 bpp version, but in some senses
simpler. All input pixels are 16 bits, and all intermediates also fit
in 16 bits, so there’s no lengthening/narrowing in the filter at all.For the full 16 pixel wide filter, we can only process 4 pixels at a time
(using an implementation very much similar to the one for 8 bpp),
but we can do 8 pixels at a time for the 4 and 8 pixel wide filters with
a different implementation of the core filter.Examples of relative speedup compared to the C version, from checkasm :
Cortex A7 A8 A9 A53
vp9_loop_filter_h_4_8_10bpp_neon : 1.83 2.16 1.40 2.09
vp9_loop_filter_h_8_8_10bpp_neon : 1.39 1.67 1.24 1.70
vp9_loop_filter_h_16_8_10bpp_neon : 1.56 1.47 1.10 1.81
vp9_loop_filter_h_16_16_10bpp_neon : 1.94 1.69 1.33 2.24
vp9_loop_filter_mix2_h_44_16_10bpp_neon : 2.01 2.27 1.67 2.39
vp9_loop_filter_mix2_h_48_16_10bpp_neon : 1.84 2.06 1.45 2.19
vp9_loop_filter_mix2_h_84_16_10bpp_neon : 1.89 2.20 1.47 2.29
vp9_loop_filter_mix2_h_88_16_10bpp_neon : 1.69 2.12 1.47 2.08
vp9_loop_filter_mix2_v_44_16_10bpp_neon : 3.16 3.98 2.50 4.05
vp9_loop_filter_mix2_v_48_16_10bpp_neon : 2.84 3.64 2.25 3.77
vp9_loop_filter_mix2_v_84_16_10bpp_neon : 2.65 3.45 2.16 3.54
vp9_loop_filter_mix2_v_88_16_10bpp_neon : 2.55 3.30 2.16 3.55
vp9_loop_filter_v_4_8_10bpp_neon : 2.85 3.97 2.24 3.68
vp9_loop_filter_v_8_8_10bpp_neon : 2.27 3.19 1.96 3.08
vp9_loop_filter_v_16_8_10bpp_neon : 3.42 2.74 2.26 4.40
vp9_loop_filter_v_16_16_10bpp_neon : 2.86 2.44 1.93 3.88The speedup vs C code measured in checkasm is around 1.1-4x.
These numbers are quite inconclusive though, since the checkasm test
runs multiple filterings on top of each other, so later rounds might
end up with different codepaths (different decisions on which filter
to apply, based on input pixel differences).Based on START_TIMER/STOP_TIMER wrapping around a few individual
functions, the speedup vs C code is around 2-4x.Signed-off-by : Martin Storsjö <martin@martin.st>