Recherche avancée

Médias (1)

Mot : - Tags -/sintel

Autres articles (63)

  • Le profil des utilisateurs

    12 avril 2011, par

    Chaque utilisateur dispose d’une page de profil lui permettant de modifier ses informations personnelle. Dans le menu de haut de page par défaut, un élément de menu est automatiquement créé à l’initialisation de MediaSPIP, visible uniquement si le visiteur est identifié sur le site.
    L’utilisateur a accès à la modification de profil depuis sa page auteur, un lien dans la navigation "Modifier votre profil" est (...)

  • Configurer la prise en compte des langues

    15 novembre 2010, par

    Accéder à la configuration et ajouter des langues prises en compte
    Afin de configurer la prise en compte de nouvelles langues, il est nécessaire de se rendre dans la partie "Administrer" du site.
    De là, dans le menu de navigation, vous pouvez accéder à une partie "Gestion des langues" permettant d’activer la prise en compte de nouvelles langues.
    Chaque nouvelle langue ajoutée reste désactivable tant qu’aucun objet n’est créé dans cette langue. Dans ce cas, elle devient grisée dans la configuration et (...)

  • XMP PHP

    13 mai 2011, par

    Dixit Wikipedia, XMP signifie :
    Extensible Metadata Platform ou XMP est un format de métadonnées basé sur XML utilisé dans les applications PDF, de photographie et de graphisme. Il a été lancé par Adobe Systems en avril 2001 en étant intégré à la version 5.0 d’Adobe Acrobat.
    Étant basé sur XML, il gère un ensemble de tags dynamiques pour l’utilisation dans le cadre du Web sémantique.
    XMP permet d’enregistrer sous forme d’un document XML des informations relatives à un fichier : titre, auteur, historique (...)

Sur d’autres sites (8038)

  • Matomo Celebrates 15 Years of Building an Open-Source & Transparent Web Analytics Solution

    30 juin 2022, par Matthieu Aubry — About, Community
    &lt;script type=&quot;text/javascript&quot;&gt;<br />
           if ('function' === typeof window.playMatomoVideo){<br />
           window.playMatomoVideo(&quot;brand&quot;, &quot;#brand&quot;)<br />
           } else {<br />
           document.addEventListener(&quot;DOMContentLoaded&quot;, function() { window.playMatomoVideo(&quot;brand&quot;, &quot;#brand&quot;); });<br />
           }<br />
      &lt;/script&gt;

    Fifteen years ago, I realised that people (myself included) were increasingly integrating the internet into their everyday lives, and it was clear that it would only expand in the future. It was an exciting new world, but the amount of personal data shared online, level of tracking and lack of security was a growing concern. Google Analytics was just launched then and was already gaining huge traction – so data from millions of websites started flowing into Google’s database, creating what was then the biggest centralised database about people worldwide and their actions online.

    So as a young engineering student, I decided we needed to build an open source and transparent solution that could help make the internet more secure and private while still providing organisations with powerful insights. I aimed to create a win-win solution for businesses and their digital consumers.

    And in 2007, I started developing Matomo with the help from Scott Switzer and Jennifer Langdon (who offered me an internship and support).   

    All thanks to the Matomo Community

    We have reached significant milestones and made major changes over the last 15 years, but we wouldn’t be where we are today without the Matomo Community.

    So I would like to celebrate and thank the hundreds of volunteer developers who have donated their time to develop Matomo, the thousands of contributors who provided feedback to improve Matomo, the countless supportive forum members, our passionate team of 40 at Matomo, the numerous translators who have translated Matomo and the 1.5 million websites that choose Matomo as their analytics platform.

    Matomo's Birthday
    Team Meetup in Paris in 2012

    Matomo has been a community effort built on the shoulders of many, and we will continue to work for you. 

    So let’s look at some milestones we have achieved over the last 15 years.

    Looking back on milestones in our timeline

    2007

    • Birth of Matomo
    • First alpha version released

    2008

    • Release first public 0.1.0 version

    2009

    • 50,000 websites use Matomo

    2010

    • Matomo first stable 1.0.0 released
    • Mobile app launched

    2011

    • Released Ecommerce Analytics, Custom Variables, First Party Cookies

    • Released Privacy control features (first of many privacy features to come !)

    2012

    • Released Log Analytics feature
    • 1 Million Downloads !
    • 300,000 websites worldwide use Matomo

    2013

    • Matomo is now available in 50 languages !
    • Matomo brand redesign

    2016

    2017

    • Launched Matomo Cloud service 
    • Released Multi Channel Conversion Attribution Premium Feature, Custom Reports Premium Feature, Login Saml Premium Feature, WooCommerceAnalytics Premium Feature and Heatmap & Session Recording Premium Feature 

    2018

    2019

    2020

    2021

    • 1,000,000 websites worldwide use Matomo
    • including 30,000 active Matomo for WordPress installations
    • Released SEO Web Vitals, Advertising Conversion Export and Tracking Spam Prevention feature

    2022

    • Released WP Statistics to Matomo importer

    Our efforts continue

    While we’ve seen incredible growth over the years, our work doesn’t stop there. In fact, we’re only just getting started.

    Today over 55% of the internet continues to use privacy-threatening web analytics solutions, while 1.5% uses Matomo. So there are still great strides to be made to create a more private internet, and joining the Matomo Community is one way to support this movement.

    There are many ways to get involved too, such as :

    So what comes next for Matomo ?

    The future of Matomo is approachable, powerful and flexible. We’re strengthening the customers’ voice, expanding our resources internally (we’re continuously hiring !) and conducting rigorous customer research to craft a tool that balances usability and functionality.

    I look forward to the next 15 years and seeing what the future holds for Matomo and our community.

  • avdevice/xcbgrab : don't assume xserver endianness

    31 janvier 2021, par Andriy Gelman
    avdevice/xcbgrab : don't assume xserver endianness
    

    xserver defines the endianness of the grabbed images. Use this information
    to set the correct pixel format.

    This also fixes format selection in configuration depth=32/bpp=32 with
    xserver on a little endian machine. Before the patch, the big endian
    layout 0RGB was always selected which is incorrect because BGR0 should
    be used. RGB24 was also incorrectly assumed (but this format was removed
    in xserver 1.20).

    The big-endian settings can be tested using docker+qemu from a little-endian
    machine :

    $ docker run —rm —privileged multiarch/qemu-user-static —reset -p yes
    $ docker run —rm -it -v /tmp :/tmp powerpc64/debian /bin/bash

    In docker container
    $ apt-get update
    $ apt-get install xvfb
    $ apt-get install x11-apps

    To test AV_PIX_FMT_0RGB32
    $ Xvfb :2 -screen 0 720x480x24 &
    $ export DISPLAY=:2
    $ xclock -geometry 720x480 -bg green #test different colors

    On your host machine grab the frames using the following
    command. View output to check that colors are rendered correctly
    $ ./ffmpeg -y -f x11grab -i :2.0 -codec:v mpeg2video out.mp4

    Other pixel formats can be tested by modifying how Xvfb is started in the docker
    container :

    AV_PIX_FMT_RGB565
    $ Xvfb :2 -screen 0 720x480x16

    AV_PIX_FMT_RGB555
    $ Xvfb :2 -screen 0 720x480x15

    AV_PIX_FMT_BGR24 / AV_PIX_FMT_RGB24
    This is difficult to test because bpp=24 support was removed in xserver 1.20
    https://lists.x.org/archives/xorg-devel/2018-February/056175.html?hmsr=joyk.com&utm_source=joyk.com&utm_medium=referral
    However, I was able to run previous version of Xvfb (with some
    modifications to force 24bpp) to check that images are rendered correctly.

    Reviewed-by : Carl Eugen Hoyos <ceffmpeg@gmail.com>
    Signed-off-by : Andriy Gelman <andriy.gelman@gmail.com>

    • [DH] libavdevice/xcbgrab.c
  • Webcam - Publishing and Archiving on line video files

    11 novembre 2014, par Emmanuel Brunet

    I want to publish an ASF live video stream over the internet and also copy the backup to disk (without sound to spare disk space)

    I’m running debian 7.7 wheezy / ffmpeg 2.2 and ffserver 1.2.9.


    The IP camera video streams specifications are

    Input #0, asf, from 'http://account:password@webcam/videostream.asf':
     Duration: N/A, start: 0.000000, bitrate: 32 kb/s
       Stream #0:0: Video: mjpeg (MJPG / 0x47504A4D), yuvj422p(pc), 640x480, 50 tbr, 1k tbn, 1k tbc
       Stream #0:1: Audio: adpcm_ima_wav ([17][0][0][0] / 0x0011), 8000 Hz, 1 channels, s16p, 32 kb/s

    To achieve this I have set up a /etc/ffserver.conf configuration

    Port 11000

    BindAddress 0.0.0.0

    MaxClients 1000

    MaxBandwidth 40000

    CustomLog -

    <feed>
    File /tmp/feed1.ffm
    FileMaxSize 200K
    ACL allow localhost
    ACL allow 192.168.1.1 192.168.255.255

    </feed>


    # --------------------------- ASF ----------------------

    <stream>
    Feed feed1.ffm
    Format asf

    AVOptionVideo flags +global_header
    VideoFrameRate 25
    VideoSize 640x480
    VideoBitRate 1024
    VideoBufferSize 1024
    StartSendOnKey
    NoAudio
    </stream>

    # ------------ Server status -------------------

    <stream>
    Format status

    # Only allow local people to get the status
    ACL allow localhost
    ACL allow 192.168.0.0 192.168.255.255

    #FaviconURL http://pond1.gladstonefamily.net:8080/favicon.ico
    </stream>


    # ---------- Redirect --------------------

    <redirect>
    URL http://www.ffmpeg.org/
    </redirect>

    To connect the feed I run

    to start the ffserver

    ffserver -f /etc/ffserver.conf

    to collect the stream from the camera

    ffmpeg -i http://account:password@webcam/videostream.asf -c:v libx264 -an http://localhost:11000/feed1.ffm

    and all works like a charm.


    My questions are :

    • How in the same time having the stream saved to disk ?

    (as done by the command)

    ffmpeg -i http://account:password@webcam/videostream.asf -preset veryfast -t 00:60:00 -b:v 512K -c:v libx264 -pix_fmt yuv420p -an /var/backup/videos/YYY-MM-DD.mp4

    Note that the output .mp4 file names should rotate to get multiple timestamped output archives

    • How can I published video over RTSP ?

    I’ve found examples on the internet but none worked for me

    Thanks in advance

    regards