
Recherche avancée
Autres articles (63)
-
Submit enhancements and plugins
13 avril 2011If you have developed a new extension to add one or more useful features to MediaSPIP, let us know and its integration into the core MedisSPIP functionality will be considered.
You can use the development discussion list to request for help with creating a plugin. As MediaSPIP is based on SPIP - or you can use the SPIP discussion list SPIP-Zone. -
Use, discuss, criticize
13 avril 2011, parTalk to people directly involved in MediaSPIP’s development, or to people around you who could use MediaSPIP to share, enhance or develop their creative projects.
The bigger the community, the more MediaSPIP’s potential will be explored and the faster the software will evolve.
A discussion list is available for all exchanges between users. -
MediaSPIP Player : problèmes potentiels
22 février 2011, parLe lecteur ne fonctionne pas sur Internet Explorer
Sur Internet Explorer (8 et 7 au moins), le plugin utilise le lecteur Flash flowplayer pour lire vidéos et son. Si le lecteur ne semble pas fonctionner, cela peut venir de la configuration du mod_deflate d’Apache.
Si dans la configuration de ce module Apache vous avez une ligne qui ressemble à la suivante, essayez de la supprimer ou de la commenter pour voir si le lecteur fonctionne correctement : /** * GeSHi (C) 2004 - 2007 Nigel McNie, (...)
Sur d’autres sites (9787)
-
How to combine pictures with an audio into a video by ffmpeg ? [duplicate]
3 septembre 2019, par Saeron MengThis question already has an answer here :
I recorded my voice for a powerpoint (or a bunch of pictures). Now I have all materials and a list of starttimes and endtimes of each picture, but I don’t know how I should use the command line to apply ffmpeg so as to combine those to a video.
I have searched on the Internet, some of the websites tell me to create a txt file containing the starttime and endtime of each picture and use the
concat
option of ffmpeg. But I don’t know how to write the txt and achieve it.Previously, I have an xml file containing starttimes and endtimes, to indicate my pictures :
<page title="1" height="540" width="960" starttimestamp="794.852" speedup="true" step="65535" stoptimestamp="1008.887" loc="hls/128345566_0.png"></page>
<page title="2" height="540" width="960" starttimestamp="1008.887" speedup="false" step="0" stoptimestamp="1078.888" loc="hls/128345566_1.png"></page>
<page title="3" height="540" width="960" starttimestamp="1078.888" speedup="false" step="0" stoptimestamp="1081.206" loc="hls/128345566_2.png"></page>How to write the concat list and apply ffmpeg ? (just format will be okay)
-
The complete guide on tracking your websites and web apps into multiple Piwiks and how to do it easily & efficiently
23 février 2017, par InnoCraft — Community, DevelopmentGetting the tracking of your website and apps right is crucial to your success as you need to ensure the measured data is meaningful and correct. That’s why we, at InnoCraft, help our clients setting up their web tracking and digital measurement strategy. Some challenges include tracking your analytics data into multiple Piwik services as well as the tracking of single-page websites and web applications (covered in a previous article). In this blog post, we explain how to track your data into multiple Piwik websites correctly.
Embedding the tracking code
First of all you need to embed your JavaScript tracking code into your website or app as usual. If you haven’t done this yet : Log in to your Piwik, click on “Administration” in the top right and go to “Tracking Code”. There you have various options to adjust your tracking code to your needs.
Tracking the same data into different websites
Let’s assume you have set up the regular JavaScript tracking code and you want to track the same data into a second Piwik website. This second Piwik website can be either on the same Piwik installation or on a different Piwik. To do this, add the following line to your tracking code :
_paq.push(['addTracker', 'https://$yourPiwikDomain/piwik.php', idSite]);
It should look like this :
var u = '//$yourPiwikDomain';
_paq.push(['addTracker', u + '/piwik.php', var idSite = 2]); // adds an additional tracker
_paq.push(['setSiteId', '1']); // configures your regular Piwik tracker
_paq.push(['setTrackerUrl', u + 'piwik.php']);This will track the same data into website 1 and website 2 of your Piwik installation. You can also change the domain in
addTracker
to point it to a different Piwik installation :_paq.push(['addTracker', '//$differentPiwikDomain/piwik.php', var idSite = 2]);
All Piwik tracker methods that you call afterwards will be applied to all trackers. Say you call
_paq.push(['disableCookies']); _paq.push(['trackPageView']);
, then both methods will be called on all tracker instances assuring they will behave the same and will track the same data into both Piwik websites.Tracking different data into different websites
If you want to track only certain data into one website, and different data into an additional website, you need to configure the trackers differently. For example, you want to enable link tracking only for one tracker, but not for the other. The problem is that calling
_paq.push(['enableLinkTracking']);
enables link tracking on all of your trackers. To workaround this limitation, you can configure your trackers differently like this :window.piwikAsyncInit = function () {
Piwik.on('TrackerSetup', function (tracker) {
if (tracker.getSiteId() == 2
|| tracker.getTrackerUrl() === '//$yourPiwikDomain/piwik.php') {
tracker.enableLinkTracking();
}
});
};Now it enables link tracking only for the tracker that is configured for a certain website ID or Piwik domain.
Accessing a previously generated tracker instance
When you configure a tracker via
_paq.push
, you create a so called “Async tracker” because Piwik will be loaded asynchronously and create the tracker instance as soon as it is loaded. If you need to get the instance of such a tracker, you can use the methodPiwik.getAsyncTracker(trackerUrl, idSite)
. This can be useful if you have a single-page website and want to track different data into different websites :window.addEventListener('hashchange', function() {
if ('undefined' === typeof Piwik) {
// Piwik might not be loaded yet
return;
}
var tracker1 = Piwik.getAsyncTracker('//$yourPiwikDomain/piwik.php', var idSite = 1);
var tracker2 = Piwik.getAsyncTracker('//$yourPiwikDomain/piwik.php', var idSite = 2);
tracker1.setCurrentUrl('/' + window.location.hash.substr(1));
tracker2.setCurrentUrl('/mywebsite/' + window.location.hash.substr(1));
});Tracking different data into multiple Piwik installations without using “_paq”
Some users prefer to not use
_paq.push
and instead directly create tracker instances themselves using the methodPiwik.getTracker(trackerUrl, idSite)
like this :window.piwikAsyncInit = function () {
var tracker1 = Piwik.getTracker('//$yourPiwikdomain/piwik.php', var idSite = 1);
tracker1.disableCookies();
var tracker2 = Piwik.getTracker('//$yourPiwikdomain/piwik.php', var idSite = 2);
tracker2.enableLinkTracking();
tracker1.trackPageView();
tracker2.trackPageView();
};We usually don’t recommend creating trackers manually as it is more complicated and you need to make sure to configure trackers in the right order. For example to prevent the setting of any cookies, it is recommended to call
disableCookies
before calling any other methods. If you want to create your trackers manually and you use any of the following methods, make sure to call them in this order :disableCookies(), setAPIUrl(), enableCrossDomainLinking(), setCookiePath(), setCookieDomain(), setDomains(), setUserId(), enableLinkTracking()
Roll-Up Reporting – the easy and efficient way
Often users track data into multiple websites because they need aggregated data over all their websites. They want to see all statistics for a single website, but also which pages were viewed across all their websites, or how much traffic they got from a specific website or search engine across all websites. This means they add a second tracker to all their websites and track data not only into the regular Piwik website, but also into one additional website that gives them statistics over all websites. This has several disadvantages :
- Complexity in getting the tracking code right and the time needed to integrate and maintain it
- Slower website performance because everything needs to be tracked into several websites. This can decrease your conversions and sales
- Slower Piwik performance because it has to handle twice as much traffic. This means tracking becomes slower, generating the report becomes slower, and the database gets twice as big
Luckily, there is a better solution called Roll-Up Reporting. With Roll-Up Reporting, you can get aggregated data over all websites and / or for a group of websites without any of these disadvantages. It lets you create as many Roll-Ups as you wish and you can choose which websites’ data should be aggregated together into a new website.
We had customers who were able to remove one Piwik tracker because of this feature which resulted in less server costs, a faster website, and a faster Piwik. On top of all these advantages, it also lets you view the Visitor Log, Real-time Map, and other widgets and reports across several websites.
Questions ?
If you got any questions, please let us know and get in touch with us. You can find more information about the Piwik JavaScript tracker on the Piwik Developer Zone. There is a section dedicated to Multiple Piwik Trackers.
-
The Ultimate Guide to HeatMap Software