Recherche avancée

Sur d’autres sites (5680)

• Why the fps of concatenate video file change with old video file ?

  23 juin 2016, par Zuiche

  I have two wmv video file which 25fps.
  I concatenate these video file using ffmpeg command line like this :

  ffmpeg -r 25 -f concat -i 1.txt -c copy output.wmv

  1.txt :

  file 'g:\1.wmv'
  
  file 'g:\2.wmv' 

  It works. But the fps of output.wmv is 30.
  How can I maintain the fps of concatenate video file ?

  UPDATE
  ======Console Output========

  ffmpeg version N-73266-g4aa0de6 Copyright (c) 2000-2015 the FFmpeg developers
  
  built with gcc 4.9.2 (GCC)
  
  configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-avisynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libdcadec --enable-libfreetype --enable-libgme --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable-librtmp --enable-libschroedinger --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvo-aacenc --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxavs --enable-libxvid --enable-lzma --enable-decklink --enable-zlib
  
  libavutil      54. 27.100 / 54. 27.100
  
  libavcodec     56. 45.101 / 56. 45.101
  
  libavformat    56. 40.100 / 56. 40.100
  
  libavdevice    56.  4.100 / 56.  4.100
  
  libavfilter     5. 19.100 /  5. 19.100
  
  libswscale      3.  1.101 /  3.  1.101
  
  libswresample   1.  2.100 /  1.  2.100
  
  libpostproc    53.  3.100 / 53.  3.100
  
  [wmv3 @ 04d452a0] Extra data: 8 bits left, value: 20
  
  [wmv3 @ 04d14d00] Extra data: 8 bits left, value: 20
  
  Input #0, concat, from '1.txt':
  
  Duration: N/A, start: 0.000000, bitrate: 4214 kb/s
  
  Stream #0:0: Video: wmv3 (Main) (WMV3 / 0x33564D57), yuv420p, 720x576, 4194 kb/s, SAR 16:15 DAR 4:3, 25 fps, 25 tbr, 1k tbn, 1k tbc
  
  Stream #0:1: Audio: wmavoice ([10][0][0][0] / 0x000A), 22050 Hz, mono, flt, 20 kb/s
  
  [asf @ 04d12120] Codec for stream 0 does not use global headers but container format requires global headers
  
  [asf @ 04d12120] Codec for stream 1 does not use global headers but container format requires global headers
  
  Output #0, asf, to 'output.wmv':
  
  Metadata:
  
  WM/EncodingSettings: Lavf56.40.100
  
  Stream #0:0: Video: wmv3 (WMV3 / 0x33564D57), yuv420p, 720x576 [SAR 16:15 DAR 4:3], q=2-31, 4194 kb/s, 25 fps, 25 tbr, 1k tbn, 25 tbc
  
  Stream #0:1: Audio: wmavoice ([10][0][0][0] / 0x000A), 22050 Hz, mono, 20 kb/s
  
  Stream mapping:
  
  Stream #0:0 -> #0:0 (copy)
  
  Stream #0:1 -> #0:1 (copy)
  
  Press [q] to stop, [?] for help
  
  [wmv3 @ 04ce8880] Extra data: 8 bits left, value: 20
  
  frame=  538 fps=0.0 q=-1.0 Lsize=    5723kB time=00:00:21.52 bitrate=2178.5kbits/s  
  
  video:5593kB audio:62kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 1.206905%

  =========FFprobe Output=========

  ffprobe version N-60456-g4040b56-Sherpya Copyright (c) 2007-2014 the FFmpeg developers
  
  built on Feb  9 2014 06:50:33 with gcc 4.8 (GCC)
  
  [wmv3 @ 050684e0] Extra data: 8 bits left, value: 20
  
  Input #0, asf, from 'output.wmv':
  
  Metadata:
  
  encoder         : Lavf56.40.100
  
  Duration: 00:00:21.52, start: 0.000000, bitrate: 2178 kb/s
  
  Stream #0:0: Video: wmv3 (Main) (WMV3 / 0x33564D57), yuv420p, 720x576, SAR 16:15 DAR 4:3, 25 tbr, 1k tbn, 1k tbc
  
  Stream #0:1: Audio: wmavoice ([10][0][0][0] / 0x000A), 22050 Hz, mono, flt, 20 kb/s
  
  [wmv3 @ 050684e0] Extra data: 8 bits left, value: 20

• libav error message with H264 codec. "non-strictly-monotonic PTS"

  13 mars 2018, par user1496491

  I have almost zero experience with libav/FFMPEG. I wrote this piece of code which capturing the screen and writes it to the file, and I’m facing some prolems with that. I was working with AV_CODEC_ID_MPEG4 codec at first, it worked just fine, but very quikly application started to spam messages like that

  [dshow @ 02da1c80] real-time buffer [screen-capture-recorder] [video input] too full or near too full (64% of size: 128000000 [rtbufsize parameter])! frame dropped!

  So I googled for some time, and found that probbably encoder is too slow, and I need to change it to faster one. So I changed it to AV_CODEC_ID_H264. Suddenly written file became unreadable, and application started to spam messages

  [libx264 @ 0455ff40] non-strictly-monotonic PTS

  I looked everywhere and all I found was a suggestion to put this two lines

  if(outPacket.pts != AV_NOPTS_VALUE) outPacket.pts = av_rescale_q(outPacket.pts, videoStream->codec->time_base, videoStream->time_base);
  
  if(outPacket.dts != AV_NOPTS_VALUE) outPacket.dts = av_rescale_q(outPacket.dts, videoStream->codec->time_base, videoStream->time_base);

  So I added them, and the result was the same.

  So, what should I do ? How do I configure output correctly ?

  Here’s my code :

  #include "MainWindow.h"
  
  
  
  #include <qguiapplication>
  
  #include <qlabel>
  
  #include <qscreen>
  
  #include <qtimer>
  
  #include <qlayout>
  
  #include <qimage>
  
  #include <qtconcurrent></qtconcurrent>QtConcurrent>
  
  #include <qthreadpool>
  
  #include <qvideoframe>
  
  
  
  #include "ScreenCapture.h"
  
  
  
  MainWindow::MainWindow(QWidget *parent) : QMainWindow(parent)
  
  {
  
      resize(800, 600);
  
  
  
      label = new QLabel();
  
      label->setAlignment(Qt::AlignHCenter | Qt::AlignVCenter);
  
  
  
      auto layout = new QHBoxLayout();
  
      layout->addWidget(label);
  
  
  
      auto widget = new QWidget();
  
      widget->setLayout(layout);
  
      setCentralWidget(widget);
  
  
  
      connect(this, &amp;MainWindow::imageReady, [=](QImage image) {label->setPixmap(QPixmap::fromImage(image).scaled(label->size(), Qt::KeepAspectRatio));});
  
  
  
      init();
  
      initOutFile();
  
      collectFrames();
  
  }
  
  
  
  MainWindow::~MainWindow()
  
  {
  
      isRunning = false;
  
  
  
      QThreadPool::globalInstance()->waitForDone();
  
  
  
      avformat_close_input(&amp;inputFormatContext);
  
      avformat_free_context(inputFormatContext);
  
  }
  
  
  
  void MainWindow::init()
  
  {
  
      av_register_all();
  
      avcodec_register_all();
  
      avdevice_register_all();
  
  
  
      auto screen = QGuiApplication::screens()[0];
  
      QRect geometry = screen->geometry();
  
  
  
      inputFormatContext = avformat_alloc_context();
  
  
  
  //    AVDictionary* options = NULL;
  
  //    av_dict_set(&amp;options, "framerate", "30", NULL);
  
  //    av_dict_set(&amp;options, "offset_x", QString::number(geometry.x()).toLatin1().data(), NULL);
  
  //    av_dict_set(&amp;options, "offset_y", QString::number(geometry.y()).toLatin1().data(), NULL);
  
  //    av_dict_set(&amp;options, "preset", "ultrafast", NULL);
  
  //    av_dict_set(&amp;options, "probesize", "10MB", NULL);
  
  //    av_dict_set(&amp;options, "pix_fmt", "yuv420p", NULL);
  
  //    av_dict_set(&amp;options, "video_size", QString(QString::number(geometry.width()) + "x" + QString::number(geometry.height())).toLatin1().data(), NULL);
  
  
  
  //    AVInputFormat* inputFormat = av_find_input_format("gdigrab");
  
  //    avformat_open_input(&amp;inputFormatContext, "desktop", inputFormat, &amp;options);
  
  
  
      QSettings settings("HKEY_CURRENT_USER\\Software\\screen-capture-recorder", QSettings::NativeFormat);
  
      settings.setValue("start_x", geometry.x());
  
      settings.setValue("start_y", geometry.y());
  
      settings.setValue("capture_width", geometry.width());
  
      settings.setValue("capture_height", geometry.height());
  
  
  
      AVDictionary* options = NULL;
  
      av_dict_set(&amp;options, "preset", "ultrafast", NULL);
  
      av_dict_set(&amp;options, "vcodec", "h264", NULL);
  
      av_dict_set(&amp;options, "video_size", "1920x1080", NULL);
  
      av_dict_set(&amp;options, "crf", "0", NULL);
  
      av_dict_set(&amp;options, "tune", "zerolatency", NULL);
  
      av_dict_set(&amp;options, "rtbufsize", "128M", NULL);
  
  
  
      AVInputFormat *format = av_find_input_format("dshow");
  
      avformat_open_input(&amp;inputFormatContext, "video=screen-capture-recorder", format, &amp;options);
  
  
  
      av_dict_free(&amp;options);
  
      avformat_find_stream_info(inputFormatContext, NULL);
  
  
  
      videoStreamIndex = av_find_best_stream(inputFormatContext, AVMEDIA_TYPE_VIDEO, -1, -1, NULL, 0);
  
  
  
      AVStream* inStream = inputFormatContext->streams[videoStreamIndex];
  
  
  
      inputCodec = avcodec_find_decoder(inStream->codecpar->codec_id);
  
      if(!inputCodec) qDebug() &lt;&lt; "Can't find input codec!";
  
  
  
      inputCodecContext = avcodec_alloc_context3(inputCodec);
  
  
  
      qDebug() &lt;&lt; "IN_FORMAT" &lt;&lt; av_get_pix_fmt_name(inStream->codec->pix_fmt);
  
  
  
      avcodec_parameters_to_context(inputCodecContext, inStream->codecpar);
  
  
  
      if(avcodec_open2(inputCodecContext, inputCodec, NULL)) qDebug() &lt;&lt; "Can't open input codec!";
  
  }
  
  
  
  void MainWindow::initOutFile()
  
  {
  
      const char* filename = "C:/Temp/output.mp4";
  
  
  
      if(avformat_alloc_output_context2(&amp;outFormatContext, NULL, NULL, filename) &lt; 0) qDebug() &lt;&lt; "Can't create out context!";
  
  
  
      outCodec = avcodec_find_encoder(AV_CODEC_ID_H264);
  
      if(!outCodec) qDebug() &lt;&lt; "Can't find codec!";
  
  
  
      videoStream = avformat_new_stream(outFormatContext, outCodec);
  
      videoStream->time_base = {1, 30};
  
  
  
      const AVPixelFormat* pixelFormat = outCodec->pix_fmts;
  
      while (*pixelFormat != AV_PIX_FMT_NONE)
  
      {
  
          qDebug() &lt;&lt; "OUT_FORMAT" &lt;&lt; av_get_pix_fmt_name(*pixelFormat);
  
          ++pixelFormat;
  
      }
  
  
  
      outCodecContext = videoStream->codec;
  
      outCodecContext->bit_rate = 16000000;
  
      outCodecContext->rc_max_rate = 0;
  
      outCodecContext->rc_buffer_size = 0;
  
      outCodecContext->qmin = 10;
  
      outCodecContext->qmax = 51;
  
      outCodecContext->qcompress = 0.6f;
  
      outCodecContext->width = inputCodecContext->width;
  
      outCodecContext->height = inputCodecContext->height;
  
      outCodecContext->time_base = videoStream->time_base;
  
      outCodecContext->gop_size = 10;
  
      outCodecContext->max_b_frames = 1;
  
      outCodecContext->pix_fmt = AV_PIX_FMT_YUV420P;
  
  
  
      if (outFormatContext->oformat->flags &amp; AVFMT_GLOBALHEADER) outCodecContext->flags |= CODEC_FLAG_GLOBAL_HEADER;
  
  
  
      if(avcodec_open2(outCodecContext, outCodec, NULL)) qDebug() &lt;&lt; "Can't open out codec!";
  
  
  
      swsContext = sws_getContext(inputCodecContext->width,
  
                                  inputCodecContext->height,
  
                                  inputCodecContext->pix_fmt,
  
                                  outCodecContext->width,
  
                                  outCodecContext->height,
  
                                  outCodecContext->pix_fmt,
  
                                  SWS_BICUBIC, NULL, NULL, NULL);
  
  
  
      if(avio_open(&amp;outFormatContext->pb, filename, AVIO_FLAG_WRITE) &lt; 0) qDebug() &lt;&lt; "Can't open file!";
  
      if(avformat_write_header(outFormatContext, NULL) &lt; 0) qDebug() &lt;&lt; "Can't write header!";
  
  }
  
  
  
  void MainWindow::collectFrames()
  
  {
  
      QtConcurrent::run([this](){
  
  
  
          AVFrame* inFrame = av_frame_alloc();
  
          inFrame->format = inputCodecContext->pix_fmt;
  
          inFrame->width = inputCodecContext->width;
  
          inFrame->height = inputCodecContext->height;
  
  
  
          int size = av_image_alloc(inFrame->data, inFrame->linesize, inFrame->width, inFrame->height, inputCodecContext->pix_fmt, 1);
  
  
  
          AVFrame* outFrame = av_frame_alloc();
  
          outFrame->format = outCodecContext->pix_fmt;
  
          outFrame->width = outCodecContext->width;
  
          outFrame->height = outCodecContext->height;
  
  
  
          av_image_alloc(outFrame->data, outFrame->linesize, outFrame->width, outFrame->height, outCodecContext->pix_fmt, 1);
  
  
  
          AVPacket packet;
  
          av_init_packet(&amp;packet);
  
  
  
          while(isRunning &amp;&amp; (av_read_frame(inputFormatContext, &amp;packet) >= 0))
  
          {
  
              if(packet.stream_index == videoStream->index)
  
              {
  
                  //for gdigrab
  
  //                uint8_t* result = new uint8_t[inFrame->width * inFrame->height * 4];
  
  //                for (int i = 0; i &lt; inFrame->height * inFrame->width * 4; i += 4)
  
  //                {
  
  //                    result[i + 0] = packet.data[i + 2]; //B
  
  //                    result[i + 1] = packet.data[i + 3]; //G
  
  //                    result[i + 2] = packet.data[i + 0]; //R
  
  //                    result[i + 3] = packet.data[i + 1]; //A
  
  //                }
  
  
  
  //                memcpy(inFrame->data[0], result, size);
  
  //                delete result;
  
  
  
                  QImage image(packet.data, inFrame->width, inFrame->height, QImage::Format_ARGB32);
  
                  QImage mirrored = image.mirrored(false, true);
  
                  emit imageReady(mirrored);
  
  
  
                  memcpy(inFrame->data[0], mirrored.bits(), size);
  
  
  
                  sws_scale(swsContext, inFrame->data, inFrame->linesize, 0, inputCodecContext->height, outFrame->data, outFrame->linesize);
  
  
  
                  av_packet_unref(&amp;packet);
  
  
  
                  AVPacket outPacket;
  
                  av_init_packet(&amp;outPacket);
  
  
  
                  int encodeResult = AVERROR(EAGAIN);
  
                  while(encodeResult == AVERROR(EAGAIN))
  
                  {
  
                      if(avcodec_send_frame(outCodecContext, outFrame)) qDebug() &lt;&lt; "Send frame error!";
  
  
  
                      encodeResult = avcodec_receive_packet(outCodecContext, &amp;outPacket);
  
                  }
  
                  if(encodeResult != 0) qDebug() &lt;&lt; "Encoding error!" &lt;&lt; encodeResult;
  
  
  
                  if(outPacket.pts != AV_NOPTS_VALUE) outPacket.pts = av_rescale_q(outPacket.pts, videoStream->codec->time_base, videoStream->time_base);
  
                  if(outPacket.dts != AV_NOPTS_VALUE) outPacket.dts = av_rescale_q(outPacket.dts, videoStream->codec->time_base, videoStream->time_base);
  
  
  
                  av_interleaved_write_frame(outFormatContext, &amp;outPacket);
  
  
  
                  av_packet_unref(&amp;outPacket);
  
              }
  
          }
  
  
  
          av_freep(inFrame->data);
  
          av_freep(outFrame->data);
  
  
  
          av_write_trailer(outFormatContext);
  
          avio_close(outFormatContext->pb);
  
      });
  
  
  
  }
  
  </qvideoframe></qthreadpool></qimage></qlayout></qtimer></qscreen></qlabel></qguiapplication>

• How to not process any personal data with Matomo and what it means for you

  22 avril 2018, par InnoCraft

  Disclaimer : this blog post has been written by digital analysts, not lawyers. The purpose of this article is to explain how to not process any personal data with Matomo in order to avoid going through the GDPR compliance process with Matomo analytics. This work comes from our interpretation of different sources : the official GDPR text and the UK privacy commission : ICO resources. It cannot be considered as a professional legal advice. So as GDPR, this information is subject to change. GDPR may be also known as RGPD in French, Spanish, Portuguese, Datenschutz-Grundverordnung, DS-GVO in German, Algemene verordening gegevensbescherming in Dutch, Regolamento generale sulla protezione dei dati in Italian.

  Are you looking for a way to not process any personal data with Matomo ? If the answer is yes, you are at the right place. From our understanding, if you are not processing personal data, then you shouldn’t be concerned about GDPR. Our inspiration came from this official reference :

  “The principles of data protection should therefore not apply to anonymous information, namely information which does not relate to an identified or identifiable natural person or to personal data rendered anonymous in such a manner that the data subject is not or no longer identifiable. This Regulation does not therefore concern the processing of such anonymous information, including for statistical or research purposes.“

  In this blog post we are going to see how you can configure Matomo in order to not process any personal data and what the consequences are.

  Which data is considered as personal according to GDPR ?

  From : eur-lex.europa.eu

  (1) “‘personal data’ means any information relating to an identified or identifiable natural person (‘data subject’) ; an identifiable natural person is one who can be identified, directly or indirectly, in particular by reference to an identifier such as a name, an identification number, location data, an online identifier or to one or more factors specific to the physical, physiological, genetic, mental, economic, cultural or social identity of that natural person ;”

  (30) “Natural persons may be associated with online identifiers provided by their devices, applications, tools and protocols, such as internet protocol addresses, cookie identifiers or other identifiers such as radio frequency identification tags. This may leave traces which, in particular when combined with unique identifiers and other information received by the servers, may be used to create profiles of the natural persons and identify them.”

  So according to your Matomo configuration, it may leave some traces within the following data :

  1. IP addresses
  2. Cookies identifiers
  3. Page URL or page titles
  4. User ID and Custom “personal” data
  5. Ecommerce order IDs
  6. Location
  7. Heatmaps & Session Recordings

  Let’s see each of them in more detail.

  1. IP addresses

  IP addresses can indirectly identify an individual. It can also give a good approximation of an individual’s location.

  IP addresses are therefore considered as personal data which means you need to anonymize them. To do so, a feature is available within Matomo, where you can anonymize the IP. We recommend you to anonymize at least the last two bytes :

  

  See our configuration guide for more information

  What are the consequences of using this feature ?

  When applying IP anonymization on two bytes, you will no longer be able to see the full IP in the UI.

  Moreover, there is a small chance that 2 different visitors with the same device and software configuration will be identified as the same visitor if the anonymised IP address is the same for both.

  2. Cookies

  It is not clear for us yet if all cookies are considered equal under GDPR. At this stage it is too early to make a definite decision.

  Did you know ? Matomo lets you optionally disable the creation of cookies by adding an extra line of code to your tracking code see below.

  

  See our configuration guide for more information

  What are the consequences of using this feature ?

  Matomo is using a few first party cookies, and the following cookies may hold personal data :

  • _pk_id : contains a visitor id used to identify unique visitors
  • _pk_ref : to identify from where they came from

  If Matomo cannot set cookies, it will use a technique called Fingerprint. It is based on several metadata such as the operating system, browser, browser plugins, IP address, browser language ; just to name a few to identify a unique visitor. As this feature is less accurate than the one using cookies, the number of visitors and visits will be affected.

  3. Page URLs and page titles

  URLs are not mentioned within the official GDPR text. However, we know that according to the different CMS you use, some of them may have URLs including personal identifiers.

  For example :

  

  As a result, you need to find a way to anonymize this data.

  There are several ways you can perform this action according to your website. If your website is adding the personal data through query parameters, you can define a rule to exclude them from Matomo.

  If the personal data are not included within query parameters, you can use the “setCustomURL” feature and write your code as follow :

  

  See our developer documentation for more information

  If you are also processing personal data within the title tag, you can use the following function : “setDocumentTitle”.

  What are the consequences of using this feature ?

  By anonymizing the URLs containing personal data, some of your  URLs will be grouped together.

  4. User ID and custom personal data

  User ID is a feature (a tracking code needs to be added) which allows you to identify the same user across different devices.

  A User ID needs a corresponding database in order to link a user across different devices, it can be an email, a username, a name, a random number… All those data are either direct or non direct online identifiers and are therefore under the scope of GDPR.

  It will be the same situation if you are using custom variables and/or custom dimensions in order to push personal data to the system.

  To continue using the User ID feature but not recording personal data, you can consider using a hash function which will anonymize/convert your actual User ID into something like “3jrj3j34434834urj33j3”.

  Alternatively, you can enable the feature “Anonymise User IDs”. This feature will be available starting in Matomo 3.5.0 :

  

  What are the consequences of using this feature ?

  Under GDPR, User ID is personal data. Anonymizing the User ID using a hash function or our built-in functionality make the User Id pseudo-anonymous, which means it can’t be easily identified to a specific user. As a result, you will still get accurate visits and unique visitors metrics, and the Visitor Profile, but without tracking the original User ID which is personal data.

  5. Ecommerce order IDs

  Order IDs are the reference number assigned to the products/services bought by your customers. As this information can be crossed with your internal database, it is considered as an online identifier and is therefore under the scope of GDPR. As for User ID, you can anonymize order IDs using our built-in functionality to Anonymise Order IDs (see section 4. about User Id).

  What are the consequences of anonymizing order ID ?

  It really depends on your former use of order IDs. If you were not using them in the past then you should not see any difference.

  6. Location

  Based on the IP address of a visitor, Matomo can detect the visitors location. Location data is problematic for privacy as this technology has become quite accurate and can detect not only the city a visitor is from, but sometimes an even more precise position of a visitor.

  

  In order to not leave any accurate traces, we strongly recommend you to enable the IP anonymization feature. Next, you need to enable the setting “Also use the anonymized IP address when enriching visits”. You find this setting directly below the IP anonymization. This is important as otherwise the full IP address will be used to geolocate a visitor.

  

  What are the consequences of anonymizing location data ?

  The more bytes you anonymize from the IP, the more anonymized your location will be. When you remove two bytes as suggested, the city and region location reports will not be as accurate. In some cases even the country may not be detected correctly anymore.

  7. Heatmaps & Session Recordings

  Heatmaps & Session Recording is a premium feature in Matomo allowing you to see where users click, hover, type and scroll. With session recordings you can then replay their actions in a video.

  Heatmaps & Session Recordings are under the scope of GDPR as they can disclose in some specific cases (for example : filling a contact form) personal data :

  

  To avoid this, Matomo will anonymize all keystrokes which a user enters into a form field unless you specifically whitelist a field. Many fields that could contain personal data, such as a credit card, phone number, email address, password, social security number, and more are always anonymized and not recorded.

  See our configuration guide for more information

  Note that a page may still show personal information within the page as part of regular content (not a form element). For example an address, or the profile page of a forum user. We have added a feature which allows you to set an HTML attribute “data-matomo-mask” to anonymize any personal content shown in the UI.

  What are the consequences of using this feature ?

  Mainly, you will not be able to see in plain text what people are entering into your forms.

  What should you do with past data ?

  Once more, we have to say that we are not lawyers. So do not take our answers as legal advice. From : ec.europa.eu/newsroom/article29/document.cfm ?doc_id=50053

  “For example, as the GDPR requires that a controller must be able to demonstrate that valid consent was obtained, all presumed consents of which no references are kept will automatically be below the consent standard of the GDPR and will need to be renewed.”

  Our interpretation is that, if you were previously relying on consent, unless you can demonstrate that valid consent was obtained, you need to get the consent back (which is almost impossible) or you need to anonymize or remove that data.

  To anonymize previously tracked data, we are actively working on a feature to do just that directly within Matomo. Alternatively, you may also set up the deletion of logs after a certain amount of time.

  We really hope you enjoyed reading this article. GDPR is still on the go and we are pretty sure you have a lot of questions about it. You probably would like to share our vision about it. So do not hesitate to ask us through our contact form to see how we are interpreting GDPR at Matomo and InnoCraft.

  The post How to not process any personal data with Matomo and what it means for you appeared first on Analytics Platform - Matomo.