Sur d’autres sites (9896)

• Different ways of embedding the Piwik tracking code for faster website performance

  18 avril 2017, par InnoCraft — Community, Development

  Many studies have shown that performance matters a lot. For each 100ms a websites takes longer to load, a business may lose about 0.1% to 1% in revenue. It also matters because Google judges page speed as a ranking factor for search results page. At InnoCraft, we help our clients optimizing their Piwik integration and recommend different ways of embedding the tracking code tailored to their needs. The best way to embed the tracking code depends on your website, what you want to achieve, and how important tracking is to you.

  This technical blog post mainly focuses on improving the time to load your website. This is an important metric as for example Google usually measures the time it took to load a page. Many businesses therefore want to get to the page load event as quickly as possible.

  The regular way of embedding the tracking code

  By default, Piwik is embedded in the header or footer of your website. This is a sensible default. While it is loaded asynchronously and deferred, it still does delay the onload event. Depending on the performance of your Piwik, how fast your website loads, how your website’s resources are embedded, and other factors you may want to consider alternatives. Three of them I will introduce below.

  Embedding the tracker after the load event

  To ensure that your website will always load even if the Piwik server is un-available, you may want to load the tracking code only after the website is loaded like this :

  var _paq = _paq || [];
  
  _paq.push(["trackPageView"]);
  
  _paq.push(["enableLinkTracking"]);
  
  
  
  function embedTrackingCode() {
  
     var u="https://your.piwik.domain/";
  
     _paq.push(["setTrackerUrl", u+"piwik.php"]);
  
     _paq.push(["setSiteId", "1"]);
  
  
  
     var d=document, g=d.createElement("script"), s=d.getElementsByTagName("script")[0]; g.type="text/javascript";
  
     g.defer=true; g.async=true; g.src=u+"piwik.js"; s.parentNode.insertBefore(g,s);    
  
  }
  
  
  
  if (window.addEventListener) { 
  
      window.addEventListener("load", embedTrackingCode, false); 
  
  } else if (window.attachEvent) { 
  
      window.attachEvent("onload",embedTrackingCode); 
  
  } else {
  
      embedTrackingCode();
  
  }

  The downside is you won’t track all of your visitors because some will have already left your website by the time your website is fully loaded. Especially when you have a JavaScript-heavy website or when your website takes longer to load in general. To detect the load event correctly cross browser, you may want to use a library like jQuery.

  Delaying the tracking

  Another technique is to load the tracking with a little delay at the end of your website like this :

  setTimeout(function () {
  
      embedTrackingCode();
  
  }, 5);

  This time the tracking script will still track most of your visitors but does not slow down loading the rest of your website as much as it would do by default (at least perceived). In some cases, you will notice a performance improvement when looking at the “time to load” but it depends on your website.

  Not loading the JavaScript Tracker at all

  With Piwik you also have the option to not embed the tracking code into your websites at all and instead generate reports from the webserver logs using Piwik Log Analytics. This works very well but some data might not be available like the device resolution which can be only captured using JavaScript. On the bright side this solution also captures users with ad blockers or tracking blockers.

  Questions ?

  We invite you to test different ways to see what makes sense for you and how it affects your website performance as well as the perceived performance. If you have any questions, feel free to get in touch with us.

  Read on

  The last post in this series is Performance optimizations you can apply today to load the Piwik JavaScript tracker faster.

• Unable to play mp4 file with JavaFX MediaPlayer

  20 juillet 2016, par Lennart

  I want to capture the computers screen and play resulting video with the MediaPlayer of JavaFX (jdk1.8.0_91).

  I found the supported encoding and container types and I think that mp4 with H.264/AVC and AAC is the best choice.

  I’m using FFmpeg with the DirectShow device Screen Capture Recorder to capture the screen and save the resulting video as mp4 file. I used the following command :

  ffmpeg -rtbufsize 1500M -framerate 25 -f dshow -i video="screen-capture-recorder":audio="virtual-audio-capturer" -r 25 -c:v libx264 -pix_fmt yuv420p output.mp4

  But the MediaPlayer isn’t able to play the video and throws a MediaException instead :

  MediaException: UNKNOWN : [com.sun.media.jfxmediaimpl.platform.gstreamer.GSTMediaPlayer@133b675a] ERROR_MEDIA_INVALID: ERROR_MEDIA_INVALID
  
      at javafx.scene.media.MediaException.getMediaException(MediaException.java:160)
  
      at javafx.scene.media.MediaPlayer$_MediaErrorListener.onError(MediaPlayer.java:2615)
  
      at com.sun.media.jfxmediaimpl.NativeMediaPlayer$EventQueueThread.HandleErrorEvents(NativeMediaPlayer.java:691)
  
      at com.sun.media.jfxmediaimpl.NativeMediaPlayer$EventQueueThread.run(NativeMediaPlayer.java:425)

  I previously used a video from Youtube (downloaded with some random Youtube downloader) for testing and it worked. I displayed the video codecs with the VLC player and it shows the same data (except for the frame rate and resolution) :

  
  Left is the Youtube video and right the FFmpeg output.

  Solution :
  The problem was the resolution of the video. I found an open jdk bug that says that the maximum resolution is 1920x1088 due to limitations of the used decoder. The video played fine after I scaled it.

• Not able to install ffmpeg vlc rubberband anything in my centOS stream 9 [closed]

  16 septembre 2023, par Yash Goyal

  sudo dnf install ffmpeg

  


  Last metadata expiration check : 0:15:12 ago on Saturday 16 September 2023 05:22:51 PM.
Error :
Problem : package ffmpeg-5.1.3-1.el9.x86_64 from rpmfusion-free-updates requires libavfilter.so.8()(64bit), but none of the providers can be installed

  


  

  • package ffmpeg-5.1.3-1.el9.x86_64 from rpmfusion-free-updates requires libavfilter.so.8(LIBAVFILTER_8)(64bit), but none of the providers can be installed

  


  • package libavfilter-free-5.1.3-1.el9.x86_64 from epel requires librubberband.so.2()(64bit), but none of the providers can be installed

  


  • package ffmpeg-libs-5.1.3-1.el9.x86_64 from rpmfusion-free-updates requires librubberband.so.2()(64bit), but none of the providers can be installed

  


  • conflicting requests

  


  • nothing provides ladspa needed by rubberband-3.1.3-1.el9.x86_64 from epel
(try to add '—skip-broken' to skip uninstallable packages or '—nobest' to use not only best candidate packages)
[root@yashgoyal yash]# sudo dnf install ffmpeg —skip-broken
Last metadata expiration check : 0:15:17 ago on Saturday 16 September 2023 05:22:51 PM.
Dependencies resolved.

  


  


  Problem : package ffmpeg-5.1.3-1.el9.x86_64 from rpmfusion-free-updates requires libavfilter.so.8()(64bit), but none of the providers can be installed

  


  

  • package ffmpeg-5.1.3-1.el9.x86_64 from rpmfusion-free-updates requires libavfilter.so.8(LIBAVFILTER_8)(64bit), but none of the providers can be installed

  


  • package libavfilter-free-5.1.3-1.el9.x86_64 from epel requires librubberband.so.2()(64bit), but none of the providers can be installed

  


  • package ffmpeg-libs-5.1.3-1.el9.x86_64 from rpmfusion-free-updates requires librubberband.so.2()(64bit), but none of the providers can be installed

  


  • conflicting requests

  


  • nothing provides ladspa needed by rubberband-3.1.3-1.el9.x86_64 from epel
================================================================================
Package Arch Version Repository Size
================================================================================
Skipping packages with broken dependencies :
ffmpeg x86_64 5.1.3-1.el9 rpmfusion-free-updates 1.7 M
ffmpeg-libs x86_64 5.1.3-1.el9 rpmfusion-free-updates 7.8 M
libavfilter-free x86_64 5.1.3-1.el9 epel 1.4 M
rubberband x86_64 3.1.3-1.el9 epel 364 k

  


  


  Transaction Summary

  


  Skip 4 Packages

  


  Nothing to do.
Complete !

  


  this is the problem i am facing i tried everything that is available on internet but not able to fix it