Recherche avancée

Sur d’autres sites (10010)

• GDPR compliance for Matomo’s Premium Features like Heatmaps & Session Recording, Form Analytics, Media Analytics & co

  27 avril 2018, par InnoCraft

  The General Data Protection Regulation (EU) 2016/679, also referred to as RGPD in French, Datenschutz-Grundverordnung, DS-GVO in German, is fast-approaching. It is now less than 30 days until GDPR applies to most businesses around the world on 25th May 2018. If you haven’t heard of this new regulation yet, I recommend you check out our GDPR guide which we continue to expand regularly to get you up to speed with it.

  GDPR compliance in Matomo

  We are currently adding several new features to Matomo to get you GDPR ready. You will have for example the possibility to delete and export data for data subjects, delete and anonymize previously tracked data, anonymize the IP address and location, ask for consent, and more. A beta version with these features is already available. We will release more blog posts and user guides about these features soon and just recently published a post on how to avoid collecting personal information in the first place soon.

  If you are still using Piwik, we highly recommend you update to a recent version of Matomo as all versions of Piwik will NOT be GDPR compliant.

  GDPR compliance for premium features

  InnoCraft, the company of the makers of Matomo, are offering various premium features for your self-hosted Matomo so you can be sure to make the right decisions and continuously grow your business. These features are also available on the cloud-hosted version of Matomo.

  If you are now wondering how GDPR applies to these features, you will be happy to hear that none of them collect any personal information except for possibly Heatmaps & Session Recording and the WooCommerce integration. All of them also support all the new upcoming GDPR features like the possibility to export and delete data. It is important that you update your Matomo Premium Features to the latest version to use these features.

  Making Heatmaps & Session Recording GDPR compliant

  We have added several new features to make it easy for you to be GDPR compliant and in many cases you might not even have to do anything. Some of the changes include :

  • Keystrokes (text entered into form fields) are no longer captured by default.
  • You may enable the capturing of keystrokes, and all keystrokes will be anonymized by default.
  • You may whitelist certain form fields to be recorded in plain text. However, fields that likely contain personal or sensitive information like passwords, phone numbers, addresses, credit card details, names, email addresses, and more will be always anonymized to protect user privacy. (this has always been the case but we have now included many more fields).

  How personal information may still be recorded

  Nevertheless, Heatmaps and Session Recordings may still record personal or sensitive information if you show them as part of the regular website as plain text (and not as part of a form field). The below example shows an email address for a paypal account as well as a name and VAT information as a regular content.

  

  To anonymize such information, simply add a data-matomo-mask attribute to your website :

  <span data-matomo-mask>example@example.com</span>

  You can read more about this in the developer guide “Masking content on your website”.

  WooCommerce Integration

  The WooCommerce integration may record an Order ID when a customer purchases something on your shop. As the Order ID is an identifier which could be linked with your shop to identify an individual, it may be considered as personal information. Matomo now offers an option to automatically anonymize this Order ID so it is no longer considered as personal information. To enable this feature, log in to your Matomo and go to “Administration => Anonymize Data”.

  GDPR compliance for third party plugins on the Matomo Marketplace

  The Matomo Marketplace currently features over 80 free plugins. Over 50 of them are compatible with the latest Matomo 3.X version and most of them should support Matomo’s new GDPR features out of the box. If you are concerned by GDPR and are not sure if a third party plugin stores any personal information, we highly recommend you ask the developer of this plugin about the compliance.

  You can find a link to the plugin’s issue tracker by going to a plugin page and then clicking on “Github” on the bottom right.

  

  If you are a plugin developer, please read our developer guide “GDPR & How do I make my Matomo plugin compliant”.

  The post GDPR compliance for Matomo’s Premium Features like Heatmaps & Session Recording, Form Analytics, Media Analytics & co appeared first on Analytics Platform - Matomo.

• How can I use ffmpeg with h264_qsv ?

  29 avril 2018, par Ubunkun

  I’ve installed the "Intel MediaServer Studio Essentials 2018R1". And I complied ffmpeg with h264_qsv.

  When I tried to use ffmpeg with h264_qsv, the errors occurred.

  $ ffmpeg -y -i ffefc5a076d93be46df1ff8674592d39.mp4 -vframes 2000 -b:v 2000K -vcodec h264_qsv -preset slow out00.mp4
  
  ffmpeg version git-2018-04-24-f09fdf2 Copyright (c) 2000-2018 the FFmpeg developers
  
    built with gcc 4.8.5 (GCC) 20150623 (Red Hat 4.8.5-16)
  
    configuration: --pkg-config-flags=--static --enable-gpl --enable-nonfree --enable-libfdk-aac --enable-libfreetype --enable-libmp3lame --enable-libopus --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libx265 --enable-libmfx
  
    libavutil      56. 15.100 / 56. 15.100
  
    libavcodec     58. 19.100 / 58. 19.100
  
    libavformat    58. 13.100 / 58. 13.100
  
    libavdevice    58.  4.100 / 58.  4.100
  
    libavfilter     7. 19.100 /  7. 19.100
  
    libswscale      5.  2.100 /  5.  2.100
  
    libswresample   3.  2.100 /  3.  2.100
  
    libpostproc    55.  2.100 / 55.  2.100
  
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'ffefc5a076d93be46df1ff8674592d39.mp4':
  
    Metadata:
  
      major_brand     : isom
  
      minor_version   : 512
  
      compatible_brands: isomiso2avc1mp41
  
      encoder         : Lavf57.55.100
  
    Duration: 02:13:42.92, start: 0.000000, bitrate: 1590 kb/s
  
      Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p, 720x480 [SAR 8:9 DAR 4:3], 1453 kb/s, 29.97 fps, 29.97 tbr, 30k tbn, 59.94 tbc (default)
  
      Metadata:
  
        handler_name    : VideoHandler
  
      Stream #0:1(und): Audio: aac (LC) (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 128 kb/s (default)
  
      Metadata:
  
        handler_name    : SoundHandler
  
  Stream mapping:
  
    Stream #0:0 -> #0:0 (h264 (native) -> h264 (h264_qsv))
  
    Stream #0:1 -> #0:1 (aac (native) -> aac (native))
  
  Press [q] to stop, [?] for help
  
  [h264_qsv @ 0x3729200] Error initializing an internal MFX session: unsupported (-3)
  
  Error initializing output stream 0:0 -- Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or height
  
  [aac @ 0x36e3740] Qavg: 65536.000
  
  [aac @ 0x36e3740] 2 frames left in the queue on closing
  
  Conversion failed!

  I don’t know where is wrong. If input file is wrong, I can change input file. I have not succeeded in running ffmpeg with h264_qsv.
  I would appreciate it if somebody can help me on how to run ffmpeg with h264_qsv.

• ffmpeg can't work via nginx + nginx-rtmp-module

  2 mai 2018, par Ubunkun

  nginx version : nginx/1.12.2
  ffmpeg version 3.4.2

  I’m trying to below.
  -> nginx -> ffmpeg multi encode -> HLS publish

  nginx configration is below (nginx.conf)

  worker_processes  1;
  
  
  
  events {
  
      worker_connections  1024;
  
  }
  
  
  
  http {
  
      include       mime.types;
  
      default_type  application/octet-stream;
  
  
  
      sendfile        on;
  
  
  
      keepalive_timeout  65;
  
  
  
      server {
  
          listen       80;
  
          server_name  localhost;
  
  
  
          location / {
  
              root   html;
  
              index  index.html index.htm index.php;
  
          }
  
  
  
      location ~ \.php$ {
  
              root           html;
  
              fastcgi_pass   unix:/var/run/php-fpm/php-fpm.sock;
  
              fastcgi_index  index.php;
  
              fastcgi_param  SCRIPT_FILENAME  $document_root$fastcgi_script_name;
  
              include        fastcgi_params;
  
          }
  
  
  
          error_page   500 502 503 504  /50x.html;
  
          location = /50x.html {
  
              root   html;
  
          }
  
      }
  
  }
  
  
  
  rtmp {
  
      server {
  
          listen 1935;
  
          application hls {
  
              live on;
  
              exec /usr/local/sbin/ffscript.sh $name;
  
          }
  
  
  
          application hls2 {
  
              live on;
  
              hls on;
  
              hls_path /usr/local/nginx/html;
  
              hls_nested on;
  
              hls_fragment 9s;
  
              hls_variant _low  BANDWIDTH=300000;
  
              hls_variant _mid  BANDWIDTH=700000;
  
              hls_variant _high BANDWIDTH=1200000;
  
          }
  
      }
  
  }

  (/usr/local/sbin/ffscript.sh)

  export LIBVA_DRIVERS_PATH=/opt/intel/mediasdk/lib64
  
  export LIBVA_DRIVER_NAME=iHD
  
  export MFX_HOME=/opt/intel/mediasdk
  
  export PKG_CONFIG_PATH=/opt/intel/opencl:
  
  
  
  /usr/local/bin/ffmpeg -i rtmp://localhost/hls/${1} -vcodec h264_qsv -init_hw
  
  _device qsv:hw -b:v 128K -c:a aac -ar 44100 -ac 2 -r 30 -f flv rtmp://localhost/
  
  hls2/${1}_low -b:v 512k -c:a aac -ar 44100 -ac 2 -r 30 -f flv rtmp://localhost/h
  
  ls2/${1}_mid -b:v 1024k -c:a aac -ar 44100 -ac 2 -r 30 -f flv rtmp://localhost/h
  
  ls2/${1}_high

  But it can’t work. The access.log appears just one line.

  192.168.1.121 [02/May/2018:21:52:39 +0900] PUBLISH "hls" "test2" "" - 580840 753 "" "FMLE/3.0 (compatible; Lavf57.55" (21s)

  There is no "hls2" PUBLISH on access log.

  When I tried to run the ffmpeg command line while nginx is running, it was succeed.

  Why ffmpeg called by nginx doesn’t work ? If you have any solution, let me know.

  Bests,