Recherche avancée

Médias (91)

Autres articles (72)

  • Publier sur MédiaSpip

    13 juin 2013

    Puis-je poster des contenus à partir d’une tablette Ipad ?
    Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir

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

  • Support audio et vidéo HTML5

    10 avril 2011

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

Sur d’autres sites (10738)

  • Revision 37456 : rha ... c’est vraiment du hack là

    20 avril 2010, par kent1@… — Log

    rha ... c’est vraiment du hack là

  • We are hiring engineers to build an awesome product and platform used by millions of people

    16 février 2016, par Piwik Core Team — Uncategorized

    Are you ready for a new challenge ? Or maybe you know someone who is looking for a change ? We have some exciting problems to solve and are looking for senior developers to work with us and our community on our open source Piwik Analytics platform. Piwik is used by more than one million websites all over the world. It is deployed on more than 300.000 servers and some users track more than 1 billion actions per month.

    What is it like to work on Piwik ?

    We develop this software using modern PHP, MySQL, Redis, AngularJS and more. We provide several kind of APIs and a plugin architecture to allow developers to extend and change Piwik to their needs. However, we would not be Piwik if we stopped at this point ! We want to turn Piwik into an even more awesome product and platform.
    You can imagine there is a lot to do and many challenges to face !

    While one part is to always make Piwik scale better and to improve UI and UX, we also want to provide simple APIs to make the life of developers as pleasant as possible. We aim to solve things the right way and our thousands of unit, integration, system, JavaScript and screenshot tests help us to innovate and to not be afraid of change. We like clean code and constant improvements.

    The Piwik team lives in New Zealand and Europe (Germany). We do the vast majority of our collaboration online. Our values include being open, transparent and sharing knowledge. For this we use tools like GitHub and Slack to communicate and Quake servers to take our minds off complex challenges. We are a small, flexible team, so when you come aboard, you will play an integral part in engineering and have a big impact on the product loved by so many people. You’ll help to create a welcoming environment for new contributors and set an example with your development practices and communications skills.

    Apply now, or spread the word !

    If you have strong skills in PHP send us an email with your CV and tell us a little about yourself and your experience in engineering complex applications.

    Apply for a job here http://piwik.org/jobs/ and if you’re maybe not the right candidate, contribute to the project by sharing this blog post and by sending it to your friends !

  • avcodec/hevc : reduce memory for SAO

    12 janvier 2015, par Fabrice Bellard
    avcodec/hevc : reduce memory for SAO
    

    cherry picked from commit 5d9f79edef2c11b915bdac3a025b59a32082f409

    SAO edge filter uses pre-SAO pixel data on the left and top of the ctb, so
    this data must be kept available. This was done previously by having 2
    copies of the frame, one before and one after SAO.

    This commit reduces the storage to just that, instead of the previous whole
    frame.

    Commit message taken from patch by Christophe Gisquet <christophe.gisquet@gmail.com>

    Signed-off-by : Michael Niedermayer <michaelni@gmx.at>

    • [DH] libavcodec/hevc.c
    • [DH] libavcodec/hevc.h
    • [DH] libavcodec/hevc_filter.c