Recherche avancée

Sur d’autres sites (5120)

• The new GDPR data protection regulation and potential consequences on Piwik

  7 septembre 2017, par Piwik Core Team — About, Privacy

  GDPR is a new data protection related regulation in Europe. GDPR stands for General Data Protection Regulation.

  The purpose of this European regulation is to strengthen and unify data protection for all individuals within the European Union. This also includes entities outside Europe willing to do business with European citizens. GDPR is a set of processes you need to follow within your organization to protect the privacy of European citizens.

  GDPR will start to apply in May 2018. It is recognized to be dissuasive because of the potential penalty of up to 4% of the yearly turnover, in case of infringement.

  Many articles have been written about GDPR including our previous article. Few of them are explaining how it will affect web analytics vendors : this is what this article is about.

  Am I really impacted by GDPR if I am a Piwik user ?

  As Piwik can collect personal data, the answer is yes. Piwik analytics data is impacted by the GDPR.

  As GDPR is a general concept, we decided from the official guidelines to assume what will be the potential consequences on the use of Piwik.

  There are 2 potential scenarios we can identify :

  • 1 – You are collecting personal data with Piwik
  • 2 – You are not collecting personal data with Piwik

  1 – Personal data collection with Piwik

  According to GDPR : IP addresses, cookies, UserID are personal data.

  IP addresses are personal data, so you will have to anonymize them unless you receive explicit consent from the visitor. Please view the following article in order to learn : how can I anonymize IP addresses in Piwik ?

  According to GDPR, cookies are personal data too. But as all cookies are not created equal it may be possible that some need to require user consent whereas other not. Whatever will be the final decision, you can learn about the first-party cookies created by Piwik and how to disable all tracking cookies in Piwik ?

  User ID, you are impacted if the User ID you assign is specific to an individual or if you can cross the User ID data further and find back the individual personal data.

  Any extra personal data you may collect with Piwik, it could be for example : first names, family names, e-mail address… You are able to collect such data using custom dimensions, custom variables…

  What are the rules I have to comply with ?

  By collecting personal data, you will have to respect EU citizens rights, which include :

  • The possibility for them to view the data you collected on them
  • The possibility to rectify some data concerning them
  • The possibility to delete their data when they request about it

  As you can imagine, for the first obligation, you will have to export all the data. So if a user is requesting it, you will have to export the data linked to his IP address(es). It can be easily exported as a .csv file for example.
  In order to do that, just create a segment according to the IP address of the user who requested it and then export the “Visitor log” report.
  If the personal data is not linked with the IP address but other attributes such as User ID or a custom dimension, you can provide the same data export by using the segment function and filtering on the personal data field.

  The data edit and deletion process on Piwik is a bit trickier as it currently requires administration system skills. We are planning to develop a new plugin for GDPR compliance (which will be available for free on the Marketplace). This plugin will let you edit and easily delete data of a particular user. Currently you can delete a specific user’s data by accessing the Piwik database and directly delete the different records for this specific user.

  2 – You are not collecting personal data with Piwik

  Unfortunately it is not because you do not collect personal data that you will not be affected by GDPR.
  The details of GDPR are not confirmed yet and GDPR could involve enabling the DoNotTrack setting by default on all browsers.
  Yes, you read it well, by default, unless the internet user uncheck this option, Piwik respecting DoNoTrack would not be able to track any user. If one needed to collect data anyway, Piwik Log Analytics and server-side tracking can be considered.

  If you need help regarding how to set up your Piwik installation in order to be GDPR compliant :

  Contact us

  Do you have a Piwik experience you would like to share with the community ? Please share it with us by contacting Piwik core team.

• ffmpeg blocky chroma decoding

  12 septembre 2017, par noiseshaper

  I’m using ffmpeg-3.2.4-win32, static and dev versions from zeranoe page, to decode some h264 mp4 videos I have created with x264 encoder. The videos have lots of static zones, 2d videogame type.

  When I decode their frames using either ffmpeg.exe or avcodec_decode_video2() API function, I get poor chroma resolution, blocky and quite visible in the static zones of the video (edit : avcodec_decode_video2() returns correct YUV, the problem is the YUV->RGB conversion, see my own answer).

  Strangely, with ffmpeg.exe I get poor chroma only if I output the frames to png, but if I output them to jpg, chroma seems much better.

  The videos are 30 fps full hd videos created from static images or from Lagarith RGB captures, converted to YUV with Rec.709 colormatrix and then input to x264.exe using crf 20 and baseline profile. Using high profile makes no difference in my tests (edit : irrelevant, since the problem is in the YUV->RGB conversion).

  If I play a mp4 video with ffplay.exe or MPC HC + LAV decoder, the chroma is good, nearly equal to the uncompressed YUV 4:2:0 version.

  Here is an example of the same frame obtained from a mp4 video created with a static image, the output frame is zoomed in to clearly see the effect.

  https://drive.google.com/file/d/0B5KI1D-N1kHpV3lGaERJRjNkcms/view

  1 : Original frame before compressing.

  2 : YUV 4:2:0 conversion before compressing

  3 : Video output from MPC HC + LAV decoder. ffplay output looks the same.

  4 : Video frames decoded with ffmpeg.exe to jpeg, some jpeg macroblocking is visible.

  5 : Video frames decoded with ffmpeg.exe to png, very blocky chroma. Using avcodec_decode_video2() function, the YUV output or its conversion to RGB produces the same blocky chroma.

  ---

  The command lines for decoding the frames to jpg and png are these :

  ffmpeg -i testcase.mp4 -vf colormatrix=bt709:bt601 -vframes 5 -qscale:v 2 output%03d.jpg

  ffmpeg -i testcase.mp4 -vf colormatrix=bt709:bt601 -vframes 5 output%03d.png

  You can download mp4 and bat files that showcase the effect here :

  https://drive.google.com/drive/folders/0B5KI1D-N1kHpcUdGd2IyM2pXMTg

  ---

  I have tried with ffmpeg 3.2, but same thing happens.

• Merge commit '10f4511f14a4e830c0ed471df4cd1cc2a18a481a'

  26 octobre 2017, par James Almer

  Merge commit '10f4511f14a4e830c0ed471df4cd1cc2a18a481a'
  * commit '10f4511f14a4e830c0ed471df4cd1cc2a18a481a' :
  
    libavutil : Make LOCAL_ALIGNED(xx be equal to LOCAL_ALIGNED_xx(
  Also added LOCAL_ALIGNED_4 as it's used in vp8 decoder, and
  
  simplified the configure defines.
  Merged-by : James Almer <jamrial@gmail.com>
  

  • [DH] configure
  • [DH] libavutil/internal.h