Recherche avancée

Médias (1)

Mot : - Tags -/biomaping

Autres articles (112)

  • Personnaliser en ajoutant son logo, sa bannière ou son image de fond

    5 septembre 2013, par

    Certains thèmes prennent en compte trois éléments de personnalisation : l’ajout d’un logo ; l’ajout d’une bannière l’ajout d’une image de fond ;

  • Script d’installation automatique de MediaSPIP

    25 avril 2011, par

    Afin de palier aux difficultés d’installation dues principalement aux dépendances logicielles coté serveur, un script d’installation "tout en un" en bash a été créé afin de faciliter cette étape sur un serveur doté d’une distribution Linux compatible.
    Vous devez bénéficier d’un accès SSH à votre serveur et d’un compte "root" afin de l’utiliser, ce qui permettra d’installer les dépendances. Contactez votre hébergeur si vous ne disposez pas de cela.
    La documentation de l’utilisation du script d’installation (...)

  • Demande de création d’un canal

    12 mars 2010, par

    En fonction de la configuration de la plateforme, l’utilisateur peu avoir à sa disposition deux méthodes différentes de demande de création de canal. La première est au moment de son inscription, la seconde, après son inscription en remplissant un formulaire de demande.
    Les deux manières demandent les mêmes choses fonctionnent à peu près de la même manière, le futur utilisateur doit remplir une série de champ de formulaire permettant tout d’abord aux administrateurs d’avoir des informations quant à (...)

Sur d’autres sites (11752)

  • why FFMPEG is not convert some audio file in 64k in android ?

    18 décembre 2019, par tailor

    There are many question regarding ffmpeg and might be this should be duplicate.
    I tried to convert any mp3 file in to lower bitrate 64k.
    It gets successfully but some mp3 files are not converted and ffmpeg direct call to onFinish command.

    Here is my command line :
    according to this

    -i /sdcard/vk2/in.mp3 -ar 44100 -ac 2 -ab 64k -f mp3 /sdcard/videokit/out.mp3";

    Here is my logcate
    on successfully

    2019-12-18 04:18:26.741 7733-7733/myapp I/audioCompression: start
    
2019-12-18 04:18:27.104 7733-7733/myapp I/audioCompression: in_progress
    
2019-12-18 04:18:27.104 7733-7733/myapp I/audioCompression: in_progress
    
2019-12-18 04:18:42.165 7733-7733/myapp I/audioCompression: success
    
2019-12-18 04:18:42.165 7733-7733/myapp I/audioCompression: finish

    otherwise

    2019-12-18 04:18:26.741 7733-7733/myapp I/audioCompression: start
    
2019-12-18 04:18:27.104 7733-7733/myapp I/audioCompression: in_progress
    
2019-12-18 04:18:27.104 7733-7733/myapp I/audioCompression: in_progress
    
2019-12-18 04:18:42.165 7733-7733/myapp I/audioCompression: finish

    report

           2019-12-18 05:34:45.965 10635-10635/myapp V/audioCompression: start command : ffmpeg
    
2019-12-18 05:34:46.124 10635-10635/myapp V/audioCompression: in_progress command : ffmpeg ffmpeg version n3.0.1 Copyright (c) 2000-2016 the FFmpeg developers
    
2019-12-18 05:34:46.124 10635-10635/myapp V/audioCompression: in_progress command : ffmpeg   built with gcc 4.8 (GCC)
    
2019-12-18 05:34:46.124 10635-10635/myapp V/audioCompression: in_progress command : ffmpeg   configuration: --target-os=linux --cross-prefix=/home/vagrant/SourceCode/ffmpeg-android/toolchain-android/bin/arm-linux-androideabi- --arch=arm --cpu=cortex-a8 --enable-runtime-cpudetect --sysroot=/home/vagrant/SourceCode/ffmpeg-android/toolchain-android/sysroot --enable-pic --enable-libx264 --enable-libass --enable-libfreetype --enable-libfribidi --enable-libmp3lame --enable-fontconfig --enable-pthreads --disable-debug --disable-ffserver --enable-version3 --enable-hardcoded-tables --disable-ffplay --disable-ffprobe --enable-gpl --enable-yasm --disable-doc --disable-shared --enable-static --pkg-config=/home/vagrant/SourceCode/ffmpeg-android/ffmpeg-pkg-config --prefix=/home/vagrant/SourceCode/ffmpeg-android/build/armeabi-v7a --extra-cflags='-I/home/vagrant/SourceCode/ffmpeg-android/toolchain-android/include -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -fno-strict-overflow -fstack-protector-all' --extra-ldflags='-L/home/vagrant/SourceCode/ffmpeg-android/toolchain-android/lib -Wl,-z,relro -Wl,-z,now -pie' --extra-libs='-lpng -lexpat -lm' --extra-cxxflags=
    
2019-12-18 05:34:46.124 10635-10635/myapp V/audioCompression: in_progress command : ffmpeg   libavutil      55. 17.103 / 55. 17.103
    
2019-12-18 05:34:46.124 10635-10635/myapp V/audioCompression: in_progress command : ffmpeg   libavcodec     57. 24.102 / 57. 24.102
    
2019-12-18 05:34:46.124 10635-10635/myapp V/audioCompression: in_progress command : ffmpeg   libavformat    57. 25.100 / 57. 25.100
    
2019-12-18 05:34:46.124 10635-10635/myapp V/audioCompression: in_progress command : ffmpeg   libavdevice    57.  0.101 / 57.  0.101
    
2019-12-18 05:34:46.124 10635-10635/myapp V/audioCompression: in_progress command : ffmpeg   libavfilter     6. 31.100 /  6. 31.100
    
2019-12-18 05:34:46.125 10635-10635/myapp V/audioCompression: in_progress command : ffmpeg   libswscale      4.  0.100 /  4.  0.100
    
2019-12-18 05:34:46.125 10635-10635/myapp V/audioCompression: in_progress command : ffmpeg   libswresample   2.  0.101 /  2.  0.101
    
2019-12-18 05:34:46.125 10635-10635/myapp V/audioCompression: in_progress command : ffmpeg   libpostproc    54.  0.100 / 54.  0.100
    
2019-12-18 05:34:46.125 10635-10635/myapp V/audioCompression: in_progress command : ffmpeg [mp3 @ 0xf6519000] Skipping 0 bytes of junk at 0.
    
2019-12-18 05:34:46.125 10635-10635/myapp V/audioCompression: in_progress command : ffmpeg [mp3 @ 0xf6519000] Estimating duration from bitrate, this may be inaccurate
    
2019-12-18 05:34:46.125 10635-10635/myapp V/audioCompression: in_progress command : ffmpeg Input #0, mp3, from '/storage/emulated/0/Download/HumnavaMereSongsMp3ioRingtone.mp3':
    
2019-12-18 05:34:46.125 10635-10635/myapp V/audioCompression: in_progress command : ffmpeg   Duration: 00:00:24.19, start: 0.000000, bitrate: 320 kb/s
    
2019-12-18 05:34:46.125 10635-10635/myapp V/audioCompression: in_progress command : ffmpeg     Stream #0:0: Audio: mp3, 44100 Hz, stereo, s16p, 320 kb/s
    
2019-12-18 05:34:46.126 10635-10635/myapp V/audioCompression: in_progress command : ffmpeg Output #0, mp3, to '/storage/emulated/0/VideoCompressor/Temp/ok.mp3':
    
2019-12-18 05:34:46.126 10635-10635/myapp V/audioCompression: in_progress command : ffmpeg   Metadata:
    
2019-12-18 05:34:46.126 10635-10635/myapp V/audioCompression: in_progress command : ffmpeg     TSSE            : Lavf57.25.100
    
2019-12-18 05:34:46.126 10635-10635/myapp V/audioCompression: in_progress command : ffmpeg     Stream #0:0: Audio: mp3 (libmp3lame), 44100 Hz, stereo, s16p, 64 kb/s
    
2019-12-18 05:34:46.126 10635-10635/myapp V/audioCompression: in_progress command : ffmpeg     Metadata:
    
2019-12-18 05:34:46.126 10635-10635/myapp V/audioCompression: in_progress command : ffmpeg       encoder         : Lavc57.24.102 libmp3lame
    
2019-12-18 05:34:46.126 10635-10635/myapp V/audioCompression: in_progress command : ffmpeg Stream mapping:
    
2019-12-18 05:34:46.127 10635-10635/myapp V/audioCompression: in_progress command : ffmpeg   Stream #0:0 -> #0:0 (mp3 (native) -> mp3 (libmp3lame))
    
2019-12-18 05:34:46.127 10635-10635/myapp V/audioCompression: in_progress command : ffmpeg Press [q] to stop, [?] for help
    
2019-12-18 05:34:46.577 10635-10635/myapp V/audioCompression: in_progress command : ffmpeg size=       6kB time=00:00:00.73 bitrate=  68.9kbits/s speed=1.46x    
    
2019-12-18 05:34:47.082 10635-10635/myapp V/audioCompression: in_progress command : ffmpeg size=      13kB time=00:00:01.56 bitrate=  66.3kbits/s speed=1.55x    
    
2019-12-18 05:34:47.583 10635-10635/myapp V/audioCompression: in_progress command : ffmpeg size=      19kB time=00:00:02.37 bitrate=  65.5kbits/s speed=1.57x    
    
2019-12-18 05:34:48.094 10635-10635/myapp V/audioCompression: in_progress command : ffmpeg size=      26kB time=00:00:03.21 bitrate=  65.1kbits/s speed=1.59x    
    
2019-12-18 05:34:48.607 10635-10635/myapp V/audioCompression: in_progress command : ffmpeg size=      32kB time=00:00:04.05 bitrate=  64.9kbits/s speed= 1.6x    
    
2019-12-18 05:34:49.110 10635-10635/myapp V/audioCompression: in_progress command : ffmpeg size=      38kB time=00:00:04.85 bitrate=  64.7kbits/s speed= 1.6x    
    
2019-12-18 05:34:49.616 10635-10635/myapp V/audioCompression: in_progress command : ffmpeg size=      45kB time=00:00:05.66 bitrate=  64.6kbits/s speed= 1.6x    
    
2019-12-18 05:34:50.117 10635-10635/myapp V/audioCompression: in_progress command : ffmpeg size=      51kB time=00:00:06.47 bitrate=  64.6kbits/s speed= 1.6x    
    
2019-12-18 05:34:50.620 10635-10635/myapp V/audioCompression: in_progress command : ffmpeg size=      57kB time=00:00:07.28 bitrate=  64.5kbits/s speed= 1.6x    
    
2019-12-18 05:34:51.128 10635-10635/myapp V/audioCompression: in_progress command : ffmpeg size=      64kB time=00:00:08.12 bitrate=  64.4kbits/s speed=1.61x    
    
2019-12-18 05:34:51.635 10635-10635/myapp V/audioCompression: in_progress command : ffmpeg size=      70kB time=00:00:08.93 bitrate=  64.4kbits/s speed=1.61x    
    
2019-12-18 05:34:52.143 10635-10635/myapp V/audioCompression: in_progress command : ffmpeg size=      77kB time=00:00:09.77 bitrate=  64.4kbits/s speed=1.61x    
    
2019-12-18 05:34:52.651 10635-10635/myapp V/audioCompression: in_progress command : ffmpeg size=      83kB time=00:00:10.60 bitrate=  64.3kbits/s speed=1.61x    
    
2019-12-18 05:34:53.156 10635-10635/myapp V/audioCompression: in_progress command : ffmpeg size=      90kB time=00:00:11.41 bitrate=  64.3kbits/s speed=1.61x    
    
2019-12-18 05:34:53.659 10635-10635/myapp V/audioCompression: in_progress command : ffmpeg size=      96kB time=00:00:12.22 bitrate=  64.3kbits/s speed=1.61x    
    
2019-12-18 05:34:54.159 10635-10635/myapp V/audioCompression: in_progress command : ffmpeg size=     102kB time=00:00:13.03 bitrate=  64.3kbits/s speed=1.61x    
    
2019-12-18 05:34:54.676 10635-10635/myapp V/audioCompression: in_progress command : ffmpeg size=     109kB time=00:00:13.87 bitrate=  64.3kbits/s speed=1.61x    
    
2019-12-18 05:34:55.177 10635-10635/myapp V/audioCompression: in_progress command : ffmpeg size=     115kB time=00:00:14.68 bitrate=  64.2kbits/s speed=1.61x    
    
2019-12-18 05:34:55.685 10635-10635/myapp V/audioCompression: in_progress command : ffmpeg size=     122kB time=00:00:15.51 bitrate=  64.2kbits/s speed=1.61x    
    
2019-12-18 05:34:56.208 10635-10635/myapp V/audioCompression: in_progress command : ffmpeg size=     128kB time=00:00:16.35 bitrate=  64.2kbits/s speed=1.61x    
    
2019-12-18 05:34:56.701 10635-10635/myapp V/audioCompression: in_progress command : ffmpeg size=     135kB time=00:00:17.16 bitrate=  64.2kbits/s speed=1.61x    
    
2019-12-18 05:34:57.203 10635-10635/myapp V/audioCompression: in_progress command : ffmpeg size=     141kB time=00:00:17.97 bitrate=  64.2kbits/s speed=1.61x    
    
2019-12-18 05:34:57.717 10635-10635/myapp V/audioCompression: in_progress command : ffmpeg size=     147kB time=00:00:18.80 bitrate=  64.2kbits/s speed=1.61x    
    
2019-12-18 05:34:58.233 10635-10635/myapp V/audioCompression: in_progress command : ffmpeg size=     154kB time=00:00:19.64 bitrate=  64.2kbits/s speed=1.62x    
    
2019-12-18 05:34:58.736 10635-10635/myapp V/audioCompression: in_progress command : ffmpeg size=     160kB time=00:00:20.45 bitrate=  64.2kbits/s speed=1.61x    
    
2019-12-18 05:34:59.238 10635-10635/myapp V/audioCompression: in_progress command : ffmpeg size=     167kB time=00:00:21.26 bitrate=  64.2kbits/s speed=1.61x    
    
2019-12-18 05:34:59.743 10635-10635/myapp V/audioCompression: in_progress command : ffmpeg size=     173kB time=00:00:22.07 bitrate=  64.2kbits/s speed=1.61x    
    
2019-12-18 05:35:00.258 10635-10635/myapp V/audioCompression: in_progress command : ffmpeg size=     179kB time=00:00:22.91 bitrate=  64.2kbits/s speed=1.61x    
    
2019-12-18 05:35:00.770 10635-10635/myapp V/audioCompression: in_progress command : ffmpeg size=     186kB time=00:00:23.72 bitrate=  64.2kbits/s speed=1.61x    
    
2019-12-18 05:35:01.017 10635-10635/myapp V/audioCompression: in_progress command : ffmpeg size=     189kB time=00:00:24.19 bitrate=  64.1kbits/s speed=1.62x    
    
2019-12-18 05:35:01.017 10635-10635/myapp V/audioCompression: in_progress command : ffmpeg video:0kB audio:189kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.130598%
    
2019-12-18 05:35:01.029 10635-10635/myapp V/audioCompression: success command : ffmpeg ffmpeg version n3.0.1 Copyright (c) 2000-2016 the FFmpeg developers
    
      built with gcc 4.8 (GCC)
    
      configuration: --target-os=linux --cross-prefix=/home/vagrant/SourceCode/ffmpeg-android/toolchain-android/bin/arm-linux-androideabi- --arch=arm --cpu=cortex-a8 --enable-runtime-cpudetect --sysroot=/home/vagrant/SourceCode/ffmpeg-android/toolchain-android/sysroot --enable-pic --enable-libx264 --enable-libass --enable-libfreetype --enable-libfribidi --enable-libmp3lame --enable-fontconfig --enable-pthreads --disable-debug --disable-ffserver --enable-version3 --enable-hardcoded-tables --disable-ffplay --disable-ffprobe --enable-gpl --enable-yasm --disable-doc --disable-shared --enable-static --pkg-config=/home/vagrant/SourceCode/ffmpeg-android/ffmpeg-pkg-config --prefix=/home/vagrant/SourceCode/ffmpeg-android/build/armeabi-v7a --extra-cflags='-I/home/vagrant/SourceCode/ffmpeg-android/toolchain-android/include -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -fno-strict-overflow -fstack-protector-all' --extra-ldflags='-L/home/vagrant/SourceCode/ffmpeg-android/toolchain-android/lib -Wl,-z,relro -Wl,-z,now -pie' --extra-libs='-lpng -lexpat -lm' --extra-cxxflags=
    
      libavutil      55. 17.103 / 55. 17.103
    
      libavcodec     57. 24.102 / 57. 24.102
    
      libavformat    57. 25.100 / 57. 25.100
    
      libavdevice    57.  0.101 / 57.  0.101
    
      libavfilter     6. 31.100 /  6. 31.100
    
      libswscale      4.  0.100 /  4.  0.100
    
      libswresample   2.  0.101 /  2.  0.101
    
      libpostproc    54.  0.100 / 54.  0.100
    
    [mp3 @ 0xf6519000] Skipping 0 bytes of junk at 0.
    
    [mp3 @ 0xf6519000] Estimating duration from bitrate, this may be inaccurate
    
    Input #0, mp3, from '/storage/emulated/0/Download/HumnavaMereSongsMp3ioRingtone.mp3':
    
      Duration: 00:00:24.19, start: 0.000000, bitrate: 320 kb/s
    
        Stream #0:0: Audio: mp3, 44100 Hz, stereo, s16p, 320 kb/s
    
    Output #0, mp3, to '/storage/emulated/0/VideoCompressor/Temp/ok.mp3':
    
      Metadata:
    
        TSSE            : Lavf57.25.100
    
        Stream #0:0: Audio: mp3 (libmp3lame), 44100 Hz, stereo, s16p, 64 kb/s
    
        Metadata:
    
          encoder         : Lavc57.24.102 libmp3lame
    
    Stream mapping:
    
      Stream #0:0 -> #0:0 (mp3 (native) -> mp3 (libmp3lame))
    
    Press [q] to stop, [?] for help
    
    size=       6kB time=00:00:00.73 bitrate=  68.9kbits/s speed=1.46x    
    
    size=      13kB time=00:00:01.56 bitrate=  66.3kbits/s speed=1.55x    
    
    size=      19kB time=00:00:02.37 bitrate=  65.5kbits/s speed=1.57x    
    
    size=      26kB time=00:00:03.21 bitrate=  65.1kbits/s speed=1.59x    
    
    size=      32kB time=00:00:04.05 bitrate=  64.9kbits/s speed= 1.6x    
    
    size=      38kB time=00:00:04.85 bitrate=  64.7kbits/s speed= 1.6x    
    
    size=      45kB time=00:00:05.66 bitrate=  64.6kbits/s speed= 1.6x    
    
    size=      51kB time=00:00:06.47 bitrate=  64.6kbits/s speed= 1.6x    
    
    size=      57kB time=00:00:07.28 bitrate=  64.5kbits/s speed= 1.6x    
    
    size=      64kB time=00:00:08.12 bitrate=  64.4kbits/s speed=1.61x    
    
    size=      70kB time=00:00:08.93 bitrate=  64.4kbits/s speed=1.61x    
    
    size=      77kB time=00:00:09.77 bitrate=  64.4kbits/s speed=1.61x    
    
    size=      83kB time=00:00:10.60 bitrate=  64.3kbits/s speed=1.61x    
    
    size=      90kB time=00:00:11.41 bitrate=  64.3kbits/s speed=1.61x    
    
    size=      96kB time=00:00:12.22 bitrate=  64.3kbits/s speed=1.61x    
    
    size=     102kB time=00:00:13.03 bitrate=  64.3kbits/s speed=1.61x    
    
    size=     109kB time=00:00:13.87 bitrate=  64.3kbits/s speed=1.61x    
    
    size=     115kB time=00:00:14.68 bitrate=  64.2kbits/s speed=1.61x    
    
    size=     122kB time=00:00:15.51 bitrate=  64.2kbits/s speed=1.61x    
    
    size=     128kB time=00:00:16.35 bitrate=  64.2kbits/s speed=1.61x    
    
    size=     135kB time=00:00:17.16 bitrate=  64.2kbits/s speed=1.61x    
    
    size=     141kB time=00:00:17.97 bitrate=  64.2kbits/s speed=1.61x    
    
    size=     147kB time=00:00:18.80 bitrate=  64.2kbits/s speed=1.61x    
    
    size=     154kB time=00:00:19.64 bitrate=  64.2kbits/s speed=1.62x    
    
    size=     160kB time=00:00:20.45 bitrate=  64.2kbits/s speed=1.61x    
    
    size=     167kB time=00:00:21.26 bitrate=  64.2kbits/s speed=1.61x  
    
2019-12-18 05:35:01.029 10635-10635/myapp V/audioCompression: Finished command : ffmpeg

  • Evolution #4419 (Nouveau) : Mettre à jour la lib jquery.flot

    26 décembre 2019, par Franck D

    Hello :)
    https://zone.spip.net/trac/spip-zone/browser/spip-zone/_core_/plugins/statistiques/javascript

    Pendant des années, la lib ne bougeait plus, la 0.8.3 date du 21/04/2014
    En 2019, elle est revenue à la vie, bref maintenant, elle est en 4.1.1 https://github.com/flot/flot
    Le changelog est là : https://github.com/flot/flot/blob/master/CHANGELOG.md

    Il me semble que excanvas.js ne sert plus en 4.1.1
    Franck

  • On-premise analytics demand grows as Google Analytics GDPR uncertainties continue

    7 janvier 2020, par Jake Thornton — Privacy

    The Google Analytics GDPR relationship is a complicated one. Website owners in states like Berlin in Germany are now required to ask users for consent to collect their data. This doesn’t make for the friendliest user-experience and often the website visitor will simply click “no.”

    The problem Google Analytics now presents website owners in the EU is with more visitors clicking “no”, the less accurate your data will become.

    Why do you need to ask your visitors for consent ?

    At this stage it’s simply because Google Analytics collects data for its own purposes. An example of this is using your visitor’s personal data for retargeting purposes across their advertising platforms like Google Ads and YouTube. 

    Google’s Privacy & Terms states : “when you visit a website that uses advertising services like AdSense, including analytics tools like Google Analytics, or embeds video content from YouTube, your web browser automatically sends certain information to Google. This includes the URL of the page you’re visiting and your IP address. We may also set cookies on your browser or read cookies that are already there. Apps that use Google advertising services also share information with Google, such as the name of the app and a unique identifier for advertising.”

    The rise of hosting web analytics on-premise

    Managing Google Analytics and GDPR can quickly become complicated, so there’s been an increase in website owners switching from cloud-hosted web analytics platforms, like Google Analytics, to more GDPR compliant alternatives, where you can host web analytics software on your own servers. This is called hosting web analytics on-premise.

    Hosting web analytics on your own servers means :

    No third-parties are involved

    The visitor data your website collects is stored on your own internal infrastructure. This means no third-parties are involved and there’s no risk of personal data being used in the way Google Analytics uses it e.g. sending personal data to its advertising platforms. 

    When you sign up with Google Analytics you sign away control of your user’s personal data. With on-premise website analytics, you own your data and are in full control.

    NOTE : Though Google Analytics uses personal data for its own purposes, not all cloud hosted web analytics platforms do this. As an example, Matomo Analytics Cloud hosted solution states that all personal data collected is not used for its own purposes and that Matomo has no rights in accessing or using this personal data. 

    You control where in the world your personal data is stored

    Google Analytics servers are based out of USA, Europe and Asia, so where your personal data will end up is uncertain and you don’t have the option to choose which location it goes to when using free Google Analytics.

    Different countries have different laws when it comes to accessing personal data. When you choose to host your web analytics on-premise, you can choose the location of your servers and where the personal data is stored.

    More flexibility

    With self-hosted web analytics platforms like Matomo On-Premise, you can extend the platform to do anything you want without the restrictions that cloud hosted platforms impose.

    You can :

    • Get full access to the source code of open-source solutions, like Matomo
    • Extend the platform however you want for your business
    • Get access to APIs
    • Have no data limitations or restrictions
    • Get RAW data access
    • Have control over security

    >> Read more about on-premise flexibility for web analytics here

    So what does the future look like for Google Analytics and GDPR ?

    It’s difficult to assess this right now. How exactly GDPR is enforced is still quite unclear. 

    What is clear however, is now website owners in Berlin using Google Analytics are lawfully required to ask their visitors for consent to collect personal data. It has been reported that Google Analytics has already received 200,000 complaints in Germany alone and it appears this trend is likely to continue across much of the EU.

    When using Google Analytics in the EU you must also ensure your privacy policy is updated so website visitors are aware that data is being collected through Google Analytics for its own purposes.

    Moving to a web analytics on-premise platform

    Matomo Analytics is the #1 open-source web analytics platform in the world and has been rated as an exceptional alternative to Google Analytics. Check the reviews on Capterra.

    Choosing Matomo On-Premise means you can control exactly where your data is stored, you have full flexibility to customise the platform to do what you want and it’s FREE.

    Matomo’s mission is to give control back to website owners and the team has designed the platform so that moving away from Google Analytics is seamless. Matomo offers most of your favourite Google Analytics features, a leaner interface to navigate, and the option to add free and paid premium features that Google Analytics can’t even offer you.

    And now you can import your historical Google Analytics data directly into your Matomo with the Google Analytics Importer plugin.

    DOWNLOAD MATOMO (FREE)

    And if you can’t host web analytics on your own servers ...

    Hosting web analytics on-premise is not an option for all businesses as you do need the internal infrastructure and technical knowledge to host your own platform.

    If you can’t self-host, then Matomo has a Cloud hosted solution you can easily install and operate like Google Analytics, which is hosted on Matomo’s servers in the EU. 

    The GDPR advantages of choosing Matomo Cloud over Google Analytics are :

    • Servers are secure and based in the EU (strict laws forbid outside access)
    • 100% data ownership – we never use data for our own purposes
    • You can export your data anytime and switch to Matomo On-Premise whenever you like
    • User-privacy protection
    • Advanced GDPR Manager and data anonymisation features which GA doesn’t offer

    Interested to learn more ?

    If you are wanting to learn more about why users are making the move from Google Analytics to Matomo, check out our Matomo Analytics vs Google Analytics comparison page.

    >> Matomo Analytics vs Google Analytics

Navigation