Recherche avancée

Médias (1)

Mot : - Tags -/stallman

Autres articles (45)

  • Keeping control of your media in your hands

    13 avril 2011, par

    The vocabulary used on this site and around MediaSPIP in general, aims to avoid reference to Web 2.0 and the companies that profit from media-sharing.
    While using MediaSPIP, you are invited to avoid using words like "Brand", "Cloud" and "Market".
    MediaSPIP is designed to facilitate the sharing of creative media online, while allowing authors to retain complete control of their work.
    MediaSPIP aims to be accessible to as many people as possible and development is based on expanding the (...)

  • Le plugin : Podcasts.

    14 juillet 2010, par

    Le problème du podcasting est à nouveau un problème révélateur de la normalisation des transports de données sur Internet.
    Deux formats intéressants existent : Celui développé par Apple, très axé sur l’utilisation d’iTunes dont la SPEC est ici ; Le format "Media RSS Module" qui est plus "libre" notamment soutenu par Yahoo et le logiciel Miro ;
    Types de fichiers supportés dans les flux
    Le format d’Apple n’autorise que les formats suivants dans ses flux : .mp3 audio/mpeg .m4a audio/x-m4a .mp4 (...)

  • Les images

    15 mai 2013

Sur d’autres sites (4714)

  • Anomalie #4052 : Visualiser ses messages dans le privé

    28 novembre 2017, par tcharlss (*´_ゝ｀)

    J’ai bien ce lien sur contrib, spip.net et forum. C’est tout en bas de la boîte d’infos :

    AUTEUR NUMÉRO

    6944
    

    Je suis rédacteur
    
4 articles
    
24 messages de forum
    
Voir en ligne

  • mips : add support for R6

    24 février 2016, par Vicente Olivert Riera
    mips : add support for R6

    Understanding the mips32r6 and mips64r6 ISAs in the configure script is
    
not enough. In order to have full support for MIPS R6 in FFmpeg we need
    
to be able to build it, and for that we need to make sure we don’t use
    
incompatible assembler code which makes the build fail. Ifdefing the
    
offending code is sufficient to fix the problem.
    

    Signed-off-by : Vicente Olivert Riera <Vincent.Riera@imgtec.com>
    
Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>
    • [DH] libavcodec/mips/aaccoder_mips.c
    • [DH] libavcodec/mips/aacdec_mips.h
    • [DH] libavcodec/mips/aacpsdsp_mips.c
    • [DH] libavcodec/mips/aacpsy_mips.h
    • [DH] libavcodec/mips/aacsbr_mips.c
    • [DH] libavcodec/mips/aacsbr_mips.h
    • [DH] libavcodec/mips/ac3dsp_mips.c
    • [DH] libavcodec/mips/acelp_filters_mips.c
    • [DH] libavcodec/mips/acelp_vectors_mips.c
    • [DH] libavcodec/mips/amrwbdec_mips.c
    • [DH] libavcodec/mips/amrwbdec_mips.h
    • [DH] libavcodec/mips/celp_filters_mips.c
    • [DH] libavcodec/mips/celp_math_mips.c
    • [DH] libavcodec/mips/compute_antialias_float.h
    • [DH] libavcodec/mips/fft_mips.c
    • [DH] libavcodec/mips/iirfilter_mips.c
    • [DH] libavcodec/mips/lsp_mips.h
    • [DH] libavcodec/mips/mpegaudiodsp_mips_fixed.c
    • [DH] libavcodec/mips/mpegaudiodsp_mips_float.c
    • [DH] libavcodec/mips/sbrdsp_mips.c
    • [DH] libavutil/mips/float_dsp_mips.c

  • avutil/libm : correct isnan, isinf compat hacks

    15 novembre 2015, par Ganesh Ajjanagadde
    avutil/libm : correct isnan, isinf compat hacks

    isnan and isinf are actually macros as per the standard. In particular,
    
the existing implementation has incorrect signature. Furthermore, this
    
results in undefined behavior for e.g double values outside float range
    
as per the standard.
    

    This patch corrects the undefined behavior for all usage within FFmpeg.
    

    Note that long double is not handled as it is not used in FFmpeg.
    
Furthermore, even if at some point long double gets used, it is likely
    
not needed to modify the macro in practice for usage in FFmpeg. See
    
below for analysis.
    

    Getting long double to work strictly per the spec is significantly harder
    
since a long double may be an IEEE 128 bit quad (very rare), 80 bit
    
extended precision value (on GCC/Clang), or simply double (on recent Microsoft).
    
On the other hand, any potential future usage of long double is likely
    
for precision (when a platform offers extra precision) and not for range, since
    
the range anyway varies and is not as portable as IEEE 754 single/double
    
precision. In such cases, the implicit cast to a double is well defined
    
and isinf and isnan should work as intended.
    

    Reviewed-by : Michael Niedermayer <michael@niedermayer.cc>
    
Signed-off-by : Ganesh Ajjanagadde <gajjanagadde@gmail.com>
    • [DH] libavutil/libm.h

Navigation