Recherche avancée

Sur d’autres sites (8823)

• 11 ways Piwik Analytics helps you to protect your visitors privacy

  11 janvier 2017, par InnoCraft — Community

  At Piwik and at InnoCraft, we think Privacy matters. From the beginning, Piwik has had a strong focus on privacy and ensures the privacy of your visitors and analytics data. As a result, Piwik has been recommended as a privacy-compliant analytics tool for example by the Independent Center for Privacy Protection in Germany (ULD) and by the Center for Data Privacy Protection in France (CNIL). In France, Piwik is the only web analytics tool that does not require Cookie Consent.

  Here are some ways how you can ensure your users and visitors privacy by using Piwik.

  1. You own the data

  Whether you host Piwik on premise yourself, managed on premise by InnoCraft, or whether you use our Piwik cloud, when you use Piwik, YOU keep control of your data and nobody else. This also means you can decide where your data should be located physically.

  2. Anonymized IP addresses

  For better privacy by default, Piwik will not record the full IP address of your visitors because otherwise the browsing history could be easily tracked across several days and even across websites within the same Piwik server. Some countries even require to anonymize the IP address, considered Personally Identifiable Information (PII).

  To change the IP anonymization settings go to “Administration > Privacy”. Optionally, you can use the full IP to still get for example accurate location data.

  

  3. Delete old visitor logs

  The visitor logs contain information all the collected raw data about every visitor and every action. You can configure Piwik to automatically delete logs from the database. When you delete old logs, only the real time and visitor log reports will no longer work for this old time period, all other aggregated reports will still work.

  For privacy reasons, we highly recommend that you keep the detailed Piwik logs for only 3 to 6 months and delete older log data. This has one other nice side effect : it will free significant database space, which will, in turn, slightly increase performance !

  

  4. Support Do Not Track preference

  Do Not Track enables users to opt out of any tracking by websites they do not visit, including analytics services, advertising networks, and social platforms. By default, Piwik respects users preference and will not track visitors which have specified “I do not want to be tracked” in their web browsers. Get more information about DoNotTrack.

  To make sure Do Not Track is respected, go to “Administration => Privacy”.

  5. Include an Opt-Out Feature on your website or app

  By embedding the Opt-Out feature in your website, you give your visitors the possibility to opt-out of the tracking. When you go to “Administration > Privacy”, you will be able to copy and paste an HTML Iframe code to embed the opt-out feature for example into your privacy policy page or in your ‘Legal’ page. Your users can then click on a link to opt-out.

  On the Piwik Marketplace there are also some plugins available to customize the Opt-Out experience. For example AjaxOptOut and CustomOptOut.

  

  6. Disable Live features

  The Real-Time, Visitor Log and Visitor Profile features give you insights into the tracked raw data by showing you details about every visitor and every action they performed. To protect the privacy of your visitors you may decide to prevent access to such features by disabling the “Live” plugin in “Administration => Plugins”. This way only aggregated reports will be shown in your Piwik.

  7. Disable fingerprinting across websites

  By default, when one of your visitors visits several of your websites, Piwik will create a fingerprint for this user that will be different across the websites to increase the visitors’ privacy. You can make sure that this feature is disabled by going to “Administration => Config file” and verifying that the value of “enable_fingerprinting_across_websites” is set to zero.

  8. Disable tracking cookies

  Piwik uses cookies to store some information about visitors between visits. In some countries, the legislation requires websites to provide a way for users to opt-out of all tracking, in particular tracking cookies. You can disable cookies by adding one line in the Piwik Javascript code.

  9. Custom development

  Piwik is an open platform that lets you extend and customize the tracking, the reporting and the Piwik user interface to your needs and to protect your visitors’ privacy the way you want or need it. Learn more in the Piwik Developer Zone. You may also have a look at our Piwik Marketplace where you can find several free and premium features to extend your Piwik.

  10. Transparency

  By default, all information and all collected data in your Piwik server are protected and nobody can access it. However, Piwik allows you to optionally make your collected data public and you can export any Piwik report including the whole dashboard to embed it into your website. This way you can show your users exactly which information you track. When you decide to make reports public, we do our best to protect privacy and automatically hide any Personally Identifiable Information such as the Visitor Profile and we make sure to not show any Visitor IP address and the Visitor ID.

  11. Privacy policy

  When you use Piwik to track your visitors, we recommend to update your Privacy Policy to explain how Piwik is used and what data it gathers. We provide a Privacy Policy template for Piwik users that you can copy on your site.

  Continuous privacy improvements

  We are always interested in improving the privacy. If you miss any feature or have an idea on how to improve the privacy, please let us know.

  More information about all the Piwik features

  If you want to learn more about all the features in Piwik, have a look at our User Guides and FAQ entries.

• ffmpeg return black and white image

  16 décembre 2011, par njai

  Video capture device is kworld dvd maker 2 (em2861)
  It returns the image in "black and white" with green line at the bottom of screen ; but when I tested it with webcam, it worked properly.

  Here is 30s video. http://www.youtube.com/watch?v=7q2wFGVwGGI

  How can I convert it to color ?

  [root@localhost ~]# ffmpeg -f video4linux2 -i /dev/video0 -vcodec mpeg4 -y output.mp4
  
  ffmpeg version git-2011-11-05-5fd1a69, Copyright (c) 2000-2011 the FFmpeg developers
  
  built on Nov  5 2011 21:10:52 with gcc 4.4.4 20100726 (Red Hat 4.4.4-13)
  
  configuration: --enable-libx264 --enable-gpl --enable-libvpx
  
  libavutil    51. 23. 0 / 51. 23. 0
  
  libavcodec   53. 27. 0 / 53. 27. 0
  
  libavformat  53. 18. 0 / 53. 18. 0
  
  libavdevice  53.  4. 0 / 53.  4. 0
  
  libavfilter   2. 47. 0 /  2. 47. 0
  
  libswscale    2.  1. 0 /  2.  1. 0
  
  libpostproc  51.  2. 0 / 51.  2. 0
  
  [video4linux2,v4l2 @ 0x2a64780] Estimating duration from bitrate, this may be inaccurate
  
  Input #0, video4linux2,v4l2, from '/dev/video0':
  
  Duration: N/A, start: 1320637788.113946, bitrate: 165888 kb/s
  
  Stream #0:0: Video: rawvideo (YUY2 / 0x32595559), yuyv422, 720x576, 165888 kb/s, 25 tbr, 1000k tbn, 25 tbc
  
  Incompatible pixel format 'yuyv422' for codec 'mpeg4', auto-selecting format 'yuv420p'
  
  [buffer @ 0x2a63920] w:720 h:576 pixfmt:yuyv422 tb:1/1000000 sar:0/1 sws_param:
  
  [buffersink @ 0x2a63cc0] auto-inserting filter 'auto-inserted scale 0' between the filter    'src' and the filter 'out'
  
  [scale @ 0x2a64560] w:720 h:576 fmt:yuyv422 -> w:720 h:576 fmt:yuv420p flags:0x4
  
  Output #0, mp4, to 'output.mp4':
  
  Metadata:
  
  encoder         : Lavf53.18.0
  
  Stream #0:0: Video: mpeg4 ( [0][0][0] / 0x0020), yuv420p, 720x576, q=2-31, 200 kb/s, 25    tbn, 25 tbc
  
  Stream mapping:
  
  Stream #0.0 -> #0.0 (rawvideo -> mpeg4)
  
  Press [q] to stop, [?] for help
  
  frame=  969 fps= 25 q=31.0 Lsize=    1547kB time=00:00:38.76 bitrate= 327.0kbits/s    
  
  video:1538kB audio:0kB global headers:0kB muxing overhead 0.561411%

• FFMPEG - Scale video filter not providing expected results

  11 novembre 2011, par dpassera

  Apologies if this question has been asked. I couldn't find it, but if it has, please let me know and I'll close this out.

  I'm attempting a simple scale of a video whose original dimensions are 480x360 and whose target dimensions are 400x300. The video starts as an FLV and eventually needs to end up as an MPEG. I'm using the following command line to do this :

  ffmpeg -i user.flv -vf "scale=400:300" user_scaled.mpg

  When I play the scaled video in MPEG Streamclip, the scale is correct and the video info shows that the dimensions are 400x300. However, when I play the scaled video in Quicktime, the video is scaled to 478x359. More importantly, FFMPEG, itself, treats the video as being 478x359, so any future commands (trimming, conversion, overlaying, etc) executed on it result in a video of 478x359.

  The initial workflow required an FLV to MPEG conversion, but I've tried this with several different in and out formats (FLV -> FLV, FLV -> MPEG, MPEG -> MPEG, etc) all with the same results. As long as I can end up with an MPEG, though, I can deal with however many steps and conversions it would take to get this scaling working.

  I'll paste the command-line output below, and a sample input video is also linked below, if you'd like it. Thank you very much for any help.

  http://www.monkeydriver.com/dpassera/stack_flv.zip

  Command-line output :

  ffmpeg -i user.flv -vf "scale=400:300" user_scaled.mpg
  
  
  
  ffmpeg version 0.7-rc1, Copyright (c) 2000-2011 the FFmpeg developers
  
    built on May 21 2011 22:13:19 with gcc 4.1.2 20080704 (Red Hat 4.1.2-50)
  
    configuration: --prefix=/usr --libdir=/usr/lib64 --shlibdir=/usr/lib64 
  
   --mandir=/usr/share/man --incdir=/usr/include --disable-avisynth
  
   --extra-cflags='-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
  
   -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -fPIC'
  
   --enable-avfilter --enable-libdirac --enable-libgsm --enable-libmp3lame
  
   --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libx264
  
   --enable-gpl --enable-postproc --enable-pthreads --enable-shared
  
   --enable-swscale --enable-vdpau --enable-version3 --enable-x11grab
  
   --disable-yasm --enable-filters --enable-filter=movie
  
  
  
    libavutil    50. 40. 1 / 50. 40. 1
  
    libavcodec   52.120. 0 / 52.120. 0
  
    libavformat  52.108. 0 / 52.108. 0
  
    libavdevice  52.  4. 0 / 52.  4. 0
  
    libavfilter   1. 77. 0 /  1. 77. 0
  
    libswscale    0. 13. 0 /  0. 13. 0
  
    libpostproc  51.  2. 0 / 51.  2. 0
  
  
  
  [flv @ 0x11dd3b30] Estimating duration from bitrate, this may be inaccurate
  
  Input #0, flv, from 'user.flv':
  
  
  
    Metadata:
  
      duration        : 5
  
      videocodecid    : 2
  
      audiocodecid    : 6
  
      canSeekToEnd    : true
  
      createdby       : FMS 4.0
  
      creationdate    : Mon Oct 31 11:43:44 2011
  
  
  
    Duration: 00:00:04.62, start: 0.000000, bitrate: N/A
  
      Stream #0.0: Video: flv, yuv420p, 640x480, 1k tbr, 1k tbn, 1k tbc
  
      Stream #0.1: Audio: nellymoser, 44100 Hz, mono, s16
  
  
  
  [buffer @ 0x11ddc950] w:640 h:480 pixfmt:yuv420p
  
  
  
  [scale @ 0x11dda610] w:640 h:480 fmt:yuv420p -> w:400 h:300 fmt:yuv420p flags:0xa0000004
  
  
  
  [mpeg @ 0x11dd6bd0] VBV buffer size not set, muxing may fail
  
  
  
  Output #0, mpeg, to 'user_scaled.mpg':
  
    Metadata:
  
      duration        : 5
  
      videocodecid    : 2
  
      audiocodecid    : 6
  
      canSeekToEnd    : true
  
      createdby       : FMS 4.0
  
      creationdate    : Mon Oct 31 11:43:44 2011
  
      encoder         : Lavf52.108.0
  
  
  
      Stream #0.0: Video: mpeg1video, yuv420p, 400x300, q=2-31, 200 kb/s, 90k tbn, 60 tbc
  
  
  
      Stream #0.1: Audio: mp2, 44100 Hz, mono, s16, 64 kb/s
  
  
  
  Stream mapping:
  
  Stream #0.0 -> #0.0
  
  Stream #0.1 -> #0.1
  
  
  
  Press [q] to stop encoding
  
  frame=  230 fps=  0 q=10.2 size=     366kB time=3.82 bitrate= 785.6kbits/s dup=175 drop=0 
  
  frame=  267 fps=  0 q=10.7 Lsize=     412kB time=4.43 bitrate= 761.3kbits/s dup=203 drop=0    
  
  
  
  video:370kB audio:36kB global headers:0kB muxing overhead 1.568959%