Recherche avancée

Sur d’autres sites (4967)

• Help us to improve Piwik by sending anonymous usage data (and get usage data yourself)

  22 octobre 2015, par Thomas Steur — Community, Plugins

  At Piwik we have developed a new plugin named AnonymousPiwikUsageMeasurement. The opt-in and anonymised usage tracking information will be used by us to build a better product and a great user experience. The plugin can be installed via the Piwik Marketplace with just a few clicks in your Piwik installation. As a Super User simply go to the Administration and select Marketplace in the left menu. There you will find the plugin and can install it with just one click.

  The plugin allows you to track usage data into up to three Piwik installations :

  • demo-anonymous.piwik.org (enabled by default, can be disabled).
  • your own Piwik (can be configured optionally)
  • a custom Piwik (can be configured optionally)

  The usage data that is sent to Piwik can be publicly viewed by anyone under demo-anonymous.piwik.org.

  What are the advantages by tracking the data into my own installation ?

  You can see how your Piwik installation is used and how well your Piwik performs by checking the average generation time of pages and API calls. Use the Row Evolution feature to see how your Piwik is performing over time.

  What is Piwik doing to make sure the data is anonymized ?

  We are very careful in what we track and we make sure to anonymize data that could contain user data.

  • We overwrite the page title as the title could contain the name of the viewed website
  • We remove any referrer information
  • We replace URL paramaters with a predefined value apart from a few whitelisted ones to make sure no actual token_auth, CSRF token or user defined value will be tracked
  • On demo-anonymous.piwik.org 3 bytes of the IP are anonymised (eg when IP is 192.168.1.1 we track only 192.0.0.0). We do not track nor collect your location and provider information.
  • We do not track clicks on outlinks or downloads

  When should I not install this plugin ?

  If you have developed a custom Piwik plugin that contains for example the name of your business in any of the following names we recommend to not install this plugin as it might be tracked :

  • name of a plugin
  • name of a controller action
  • name of a report
  • name of a widget
  • name of an API method

  Plugins that are installed via the Marketplace should not pose a problem as their names don't contain any user specific information such as the name of your business.

  The data is tracked as efficiently as possible as to not slow down your Piwik server. If you already have some performance challenges with your Piwik, we recommend not to install this plugin.

  Which data is tracked ?

  When the plugin is activated, the following data will be tracked :

  • The pages and reports that are viewed
  • The visitors' software and devices data like the used browser and the resolution
  • Some clicks or interactions with certain selectors or buttons. For example we track an event when a segment is selected (but we do not track the actual segment name or value).
  • In a daily task we track the following data :
    • Piwik version
    • PHP version
    • Number of websites
    • Number of users
    • Number of segments
    • How often which API method was called (only plugin name and method name but no parameters) and how long the API calls took on average.

  Are there any prerequisites ?

  • If sending usage data to Piwik is enabled, the Piwik installation must be connected to the internet
  • If tracking to a custom Piwik installation is enabled, your Piwik installation and your Piwik users must be able to connect to this instance

  Where can I report any issues with the plugin ?

  If you experience any issues with the plugin please create a new issue. The source code is available under GPL v3+ on GitHub. We always appreciate pull requests and suggestions to improve this plugin.

• Help us to improve Piwik by sending anonymous usage data (and get usage data yourself)

  22 octobre 2015, par Thomas Steur — Community, Plugins

  At Piwik we have developed a new plugin named AnonymousPiwikUsageMeasurement. The opt-in and anonymised usage tracking information will be used by us to build a better product and a great user experience. The plugin can be installed via the Piwik Marketplace with just a few clicks in your Piwik installation. As a Super User simply go to the Administration and select Marketplace in the left menu. There you will find the plugin and can install it with just one click.

  The plugin allows you to track usage data into up to three Piwik installations :

  • demo-anonymous.piwik.org (enabled by default, can be disabled).
  • your own Piwik (can be configured optionally)
  • a custom Piwik (can be configured optionally)

  The usage data that is sent to Piwik can be publicly viewed by anyone under demo-anonymous.piwik.org.

  What are the advantages by tracking the data into my own installation ?

  You can see how your Piwik installation is used and how well your Piwik performs by checking the average generation time of pages and API calls. Use the Row Evolution feature to see how your Piwik is performing over time.

  What is Piwik doing to make sure the data is anonymized ?

  We are very careful in what we track and we make sure to anonymize data that could contain user data.

  • We overwrite the page title as the title could contain the name of the viewed website
  • We remove any referrer information
  • We replace URL paramaters with a predefined value apart from a few whitelisted ones to make sure no actual token_auth, CSRF token or user defined value will be tracked
  • On demo-anonymous.piwik.org 3 bytes of the IP are anonymised (eg when IP is 192.168.1.1 we track only 192.0.0.0). We do not track nor collect your location and provider information.
  • We do not track clicks on outlinks or downloads

  When should I not install this plugin ?

  If you have developed a custom Piwik plugin that contains for example the name of your business in any of the following names we recommend to not install this plugin as it might be tracked :

  • name of a plugin
  • name of a controller action
  • name of a report
  • name of a widget
  • name of an API method

  Plugins that are installed via the Marketplace should not pose a problem as their names don't contain any user specific information such as the name of your business.

  The data is tracked as efficiently as possible as to not slow down your Piwik server. If you already have some performance challenges with your Piwik, we recommend not to install this plugin.

  Which data is tracked ?

  When the plugin is activated, the following data will be tracked :

  • The pages and reports that are viewed
  • The visitors' software and devices data like the used browser and the resolution
  • Some clicks or interactions with certain selectors or buttons. For example we track an event when a segment is selected (but we do not track the actual segment name or value).
  • In a daily task we track the following data :
    • Piwik version
    • PHP version
    • Number of websites
    • Number of users
    • Number of segments
    • How often which API method was called (only plugin name and method name but no parameters) and how long the API calls took on average.

  Are there any prerequisites ?

  • If sending usage data to Piwik is enabled, the Piwik installation must be connected to the internet
  • If tracking to a custom Piwik installation is enabled, your Piwik installation and your Piwik users must be able to connect to this instance

  Where can I report any issues with the plugin ?

  If you experience any issues with the plugin please create a new issue. The source code is available under GPL v3+ on GitHub. We always appreciate pull requests and suggestions to improve this plugin.

• set MediaRecorder to record 1 frame every N seconds

  19 août 2022, par The Blind Hawk

  Summary

  


  I have a version of my code already working on Chrome and Edge, but I need some fixes for it to work on Safari.
  
My objective is to record around 25 minutes and download a timelapse version of the recording.
  
final product requirements :

  


  speed: 3fps
length: ~25s

(I need to record one frame every 20 seconds for 25 mins)


  


  this.secondStream settings :

  


  this.secondStream = await navigator.mediaDevices.getUserMedia({
    audio: false,
    video: {width: 430, height: 430, facingMode: "user"}
});


  


  My code for IOS so far :

  


          startIOSVideoRecording: function() {
            console.log("setting up recorder");
            var self = this;
            this.data = [];

            if (MediaRecorder.isTypeSupported('video/mp4')) {
                // IOS does not support webm, so I will be using mp4
                var options = {mimeType: 'video/mp4', videoBitsPerSecond : 1000000};
            } else {
                console.log("ERROR: mp4 is not supported, trying to default to webm");
                var options = {mimeType: 'video/webm'};
            }
            console.log("options settings:");
            console.log(options);

            this.recorder = new MediaRecorder(this.secondStream, options);

            this.recorder.ondataavailable = function(evt) {
                if (evt.data && evt.data.size > 0) {
                    self.data.push(evt.data);
                    console.log('chunk size: ' + evt.data.size);
                }
            }

            this.recorder.onstop = function(evt) {
                console.log('recorder stopping');
                var blob = new Blob(self.data, {type: "video/mp4"});
                self.download(blob, "mp4");
                self.sendMail(videoBlob);
            }

            console.log("finished setup, starting")
            this.recorder.start(1200);

            function sleep(ms) { return new Promise(resolve => setTimeout(resolve, ms));}

            async function looper() {
                // I am trying to pick one second every 20 more or less
                await sleep(500);
                self.recorder.pause();
                await sleep(18000);
                self.recorder.resume();
                looper();
            }
            looper();
        },


  


  Issues

  


  Only one call to getUserMedia()

  


  I am already using this.secondstream elsewhere, and I need the settings to stay as they are for the other functionality.
  
On Chrome and Edge, I could just call getUserMedia() again with different settings, and the issue would be solved, but on IOS calling getUserMedia() a second time kills the first stream.
  
The settings that I was planning to use (works for Chrome and Edge) :

  


  navigator.mediaDevices.getUserMedia({
    audio: false,
    video: { 
        width: 360, height: 240, facingMode: "user", 
        frameRate: { min:0, ideal: 0.05, max:0.1 } 
    },
}


  


  The timelapse library I am using does not support mp4 (ffmpeg as alternative ?)

  


  I am forced to use mp4 on IOS apparently, but this does not allow me to use the library I was relying on so I need an alternative.
  
I am thinking of using ffmpeg but cannot find any documentation to make it interact with the blob before the download.
  
I do not want to edit the video after downloading it, but I want to be able to download the already edited version, so no terminal commands.

  


  MediaRecorder pause and resume are not ideal

  


  On Chrome and Edge I would keep one frame every 20 seconds by setting the frameRate to 0.05, but this does not seem to work on IOS for two reasons.
  
First one is related to the first issue of not being able to change the settings of getUserMedia() without destroying the initial stream in the first place.
  
And even after changing the settings, It seems that setting the frame rate below 1 is not supported on IOS. Maybe I wrote something else wrong, but I was not able to open the downloaded file.
  
Therefore I tried relying on pausing and resuming the MediaRecorder, but this brings forth another two issues :
  
I am currently saving 1 second every 20 seconds and not 1 frame every 20 seconds, and I cannot find any workarounds.
  
Pause and Resume take a little bit of time, making the code unreliable, as I sometimes pick 2/20 seconds instead of 1/20, and I have no reliability that the loop is actually running every 20 seconds (might be 18 might be 25).