Recherche avancée

Médias (91)

Autres articles (82)

  • MediaSPIP Player : problèmes potentiels

    22 février 2011, par

    Le lecteur ne fonctionne pas sur Internet Explorer
    Sur Internet Explorer (8 et 7 au moins), le plugin utilise le lecteur Flash flowplayer pour lire vidéos et son. Si le lecteur ne semble pas fonctionner, cela peut venir de la configuration du mod_deflate d’Apache.
    Si dans la configuration de ce module Apache vous avez une ligne qui ressemble à la suivante, essayez de la supprimer ou de la commenter pour voir si le lecteur fonctionne correctement : /** * GeSHi (C) 2004 - 2007 Nigel McNie, (...)

  • HTML5 audio and video support

    13 avril 2011, par

    MediaSPIP 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 (...)

  • De l’upload à la vidéo finale [version standalone]

    31 janvier 2010, par

    Le chemin d’un document audio ou vidéo dans SPIPMotion est divisé en trois étapes distinctes.
    Upload et récupération d’informations de la vidéo source
    Dans un premier temps, il est nécessaire de créer un article SPIP et de lui joindre le document vidéo "source".
    Au moment où ce document est joint à l’article, deux actions supplémentaires au comportement normal sont exécutées : La récupération des informations techniques des flux audio et video du fichier ; La génération d’une vignette : extraction d’une (...)

Sur d’autres sites (5278)

  • 3 million downloads for Piwik Analytics

    11 janvier 2017, par Matthieu Aubry — Community

    A testament to the power of our mission statement…

    “To create, as a community, the leading international open source digital analytics platform, that gives every user full control of their data.”

    … Piwik has been downloaded more than 3 million times !

    Piwik is the most popular open analytics platform

    Piwik is the number one most popular open analytics platform, used on more than 1 million websites in 200 different countries, and the 7th overall most popular analytics tool.

    Together we can make Piwik even better !

    Piwik is a community project. We are so proud of what we have created and would love your help too ! Help us by filling in our community survey (takes just 5 minutes !), by getting involved or becoming a sponsor.

    Thank you so much for using Piwik and respecting privacy while keeping control of your data.

    Happy Analytics !

  • imdct15 : remove the AArch64 assembly

    4 janvier 2017, par Rostislav Pehlivanov
    imdct15 : remove the AArch64 assembly
    

    Prep work for the next commit, which will add a new FFT algorithm
    which makes the iMDCT over 3x faster than it is currently (standalone,
    the FFT is with some framesizes over 10x faster).

    The new FFT algorithm uses the already thouroughly SIMD’d power of two
    FFT which already has SIMD for AArch64, so users of that platform will
    still see an improvement.

    The previous FFT+SIMD was barely 2.5x faster than the C versions on these
    platforms.

    Signed-off-by : Rostislav Pehlivanov <atomnuker@gmail.com>

    • [DH] libavcodec/aarch64/Makefile
    • [DH] libavcodec/aarch64/imdct15_init.c
    • [DH] libavcodec/aarch64/imdct15_neon.S
    • [DH] libavcodec/imdct15.c
    • [DH] libavcodec/imdct15.h
  • imdct15 : replace the FFT with a faster PFA FFT algorithm

    4 janvier 2017, par Rostislav Pehlivanov
    imdct15 : replace the FFT with a faster PFA FFT algorithm
    

    This commit replaces the current inefficient non-power-of-two FFT with a
    much faster FFT based on the Prime Factor Algorithm.
    Although it is already much faster than the old algorithm without SIMD,
    the new algorithm makes use of the already very throughouly SIMD’d power
    of two FFT, which improves performance even more across all platforms
    which we have SIMD support for.

    Most of the work was done by Peter Barfuss, who passed the code to me to
    implement into the iMDCT and the current codebase. The code for a
    5-point and 15-point FFT was derived from the previous implementation,
    although it was optimized and simplified, which will make its future
    SIMD easier. The 15-point FFT is currently using 6% of the current
    overall decoder overhead.

    The FFT can now easily be used as a forward transform by simply not
    multiplying the 5-point FFT’s imaginary component by -1 (which comes
    from the fact that changing the complex exponential’s angle by -1 also
    changes the output by that) and by multiplying the "theta" angle of the
    main exptab by -1. Hence the deliberately left multiplication by -1 at
    the end.

    FATE passes, and performance reports on other platforms/CPUs are
    welcome.

    Performance comparisons :

    iMDCT, PFA :
    101127 decicycles in speed, 32765 runs, 3 skips
    iMDCT, Old :
    211022 decicycles in speed, 32768 runs, 0 skips

    Standalone FFT, 300000 transforms of size 960 :
    PFA Old FFT kiss_fft libfftw3f
    3.659695s, 15.726912s, 13.300789s, 1.182222s

    Being only 3x slower than libfftw3f is a big achievement by itself.

    There appears to be something capping the performance in the iMDCT side
    of things, possibly during the pre-stage reindexing. However, it is
    certainly fast enough for now.

    Signed-off-by : Rostislav Pehlivanov <atomnuker@gmail.com>

    • [DH] libavcodec/imdct15.c
    • [DH] libavcodec/imdct15.h