Recherche avancée

Sur d’autres sites (10853)

• Get video duration of file hosted on Amazon S3

  26 octobre 2016, par Michi

  I’m starting a portal which distributes videos. The idea is to upload the videos to Amazon S3 and gather the necessary data using PHP from my server. So far everything works fine... the only thing I could not manage to get is the duration of the video :-( Could anybody give me a hint on how to accomplish it ?

  Thanks,
  Miguel

  UPDATE :

  I finally opted to do it using FFmpeg. I have already installed FFmpeg on the server and I’m now trying to execute the command in the shell prior to execute it with PHP. I’m passing it the URL from Amazon (I tried both the cloudfront URL and the S3 URL) but it says that there is not such a directory or file. I’ve seen examples on the web using external files so I expected it to work.

  The command I’m using is

  ffmpeg -i https://s3-eu-west-1.amazonaws.com/path/to/file.m4v

  Is there something I need to configure in order to use external URLs ?

• Get video duration of file hosted on Amazon S3

  10 janvier 2020, par Michi

  I’m starting a portal which distributes videos. The idea is to upload the videos to Amazon S3 and gather the necessary data using PHP from my server. So far everything works fine... the only thing I could not manage to get is the duration of the video :-( Could anybody give me a hint on how to accomplish it ?

  Thanks,
  Miguel

  UPDATE :

  I finally opted to do it using FFmpeg. I have already installed FFmpeg on the server and I’m now trying to execute the command in the shell prior to execute it with PHP. I’m passing it the URL from Amazon (I tried both the cloudfront URL and the S3 URL) but it says that there is not such a directory or file. I’ve seen examples on the web using external files so I expected it to work.

  The command I’m using is

  ffmpeg -i https://s3-eu-west-1.amazonaws.com/path/to/file.m4v

  Is there something I need to configure in order to use external URLs ?

• Performance optimizations you can apply today to load the Piwik JavaScript tracker faster

  20 avril 2017, par InnoCraft — Community, Development

  When you track your website with Piwik or any other analytics solution, you need to embed a JavaScript file in order to track page views, events, clicks, and more. At InnoCraft, it is our daily business to help Piwik users to make the most out of their Piwik. We often see similar problems of websites loading unnecessarily slower because the tracking file is not loaded as fast as it should be. There are many ways you can improve the performance but avoiding the most important mistakes will help you to not lose revenue and conversions because of this today. Below you find a few steps that will boost the loading of your Piwik JavaScript tracking file.

  Cache piwik.js

  The most important step is to make sure to configure your server in a way so the piwik.js JavaScript tracker file will be cached once it has been loaded and not requested again on subsequent page views. Learn more about browser caching.

  Enable GZIP

  We recommend enabling GZIP as it reduces the size the user needs to load when the piwik.js file is requested. For the standard Piwik tracker, this will reduce the size from about 60KB to 20KB.

  Preload DNS

  Often a Piwik is hosted on a different domain and when the browser loads the JavaScript tracker file, it needs to first perform a DNS lookup to find the IP address for this domain. By adding the below snipped for your Piwik domain, it can boost the performance of loading the tracker file by 10ms to 50ms.

  <link rel="dns-prefetch" href="//example.innocraft.cloud">

  Preload resource

  To boost the loading of the Piwik tracking file, you can add the following HTML into the header of your website :

  <link rel="preload" href="https://yourpiwikdomain.com/piwik.js" onload="embedTracker()" type="script" crossorigin>

  In Chrome, Opera, and soon in more browsers this will load the JavaScript tracker file without blocking the “onload” event. As a result, as soon as you embed the tracking code, the JavaScript tracker might be already loaded. How “preloading” affects your website always depends and maybe you rather want to preload more important resources than the tracking code, but it is an option to consider. If you load your JavaScript tracker file in the <head> of your website, this should not be needed.

  Advanced options

  If you want to go even further, you can think about serving the JavaScript tracking file via a CDN, merging the JavaScript tracker file content with your other JavaScript files, making use of service workers (and even track data offline), and more. Feel free to get in touch with us if you have any questions.

  More performance improvements

  Read our first blog in the series at Different ways of embedding the Piwik tracking code for faster website performance