Recherche avancée

Sur d’autres sites (4784)

• Non-monotonous DTS in output for audio stream using ffmpeg concat

  24 mai 2015, par Apollo Marquis

  This was asked in FFMPEG - Non-Monotonous DTS on concat. But the poster simply opted for MP4Box after getting no reply. However, I would like to stick with ffmpeg which I think is quicker.

  I am concatenating files from a text file list of mp4 files that have been encoded at the same time using the same codecs so there should be no incompatibility between the files.

  I am not even sure what Non-monotonous DTS is (anyone ?) but I am worried it may produce some glitches in the concatenated files. They seem ok but there is some evidence of artefacts in the sound. Can I tweak my command line to get rid of this error, and will it speed up the concatenation process ?
  I am using Python subprocess call and the file passed into this function is the list of files. The function decorator is just a timer function for profiling.
  I have tried this with my system ffmpeg not just the static build, and it has the same problem.

  @fn_timer
  
  def concat(file):
  
      proc = call(['/opt/jane_ng/jane_nodejs/ffmpeg-git-20150308-64bit-static/ffmpeg', '-f', 'concat', '-i', file, '-c', 'copy', '-y', 'testConcat.mp4'])

  When I run this, I get the following output :

  ffmpeg version N-45007-g9d7e42e-   http://johnvansickle.com/ffmpeg/    Copyright (c) 2000-2015 the FFmpeg developers
  
    built with gcc 4.9.2 (Debian 4.9.2-10)
  
    configuration: --enable-gpl --enable-version3 --disable-shared --disable-debug --enable-runtime-cpudetect --enable-libmp3lame --enable-libx264 --enable-libx265 --enable-libwebp --enable-libspeex --enable-libvorbis --enable-libvpx --enable-libfreetype --enable-fontconfig --enable-libxvid --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libtheora --enable-libvo-aacenc --enable-libvo-amrwbenc --enable-gray --enable-libopenjpeg --enable-libopus --enable-libass --enable-gnutls --enable-libvidstab --cc=gcc-4.9
  
    libavutil      54. 20.100 / 54. 20.100
  
    libavcodec     56. 26.100 / 56. 26.100
  
    libavformat    56. 25.101 / 56. 25.101
  
    libavdevice    56.  4.100 / 56.  4.100
  
    libavfilter     5. 12.100 /  5. 12.100
  
    libswscale      3.  1.101 /  3.  1.101
  
    libswresample   1.  1.100 /  1.  1.100
  
    libpostproc    53.  3.100 / 53.  3.100
  
  [concat @ 0x31bdd80] Could not find codec parameters for stream 2 (Unknown: none): unknown codec
  
  Consider increasing the value for the 'analyzeduration' and 'probesize' options
  
  Input #0, concat, from '/opt/combinatoria/generator/concatFiles/concat.txt':
  
    Duration: N/A, start: 0.000000, bitrate: 1625 kb/s
  
      Stream #0:0: Video: h264 (Main) (avc1 / 0x31637661), yuv420p(tv), 960x540 [SAR 1:1 DAR 16:9], 1561 kb/s, 25 fps, 25 tbr, 90k tbn, 50 tbc
  
      Stream #0:1: Audio: aac (HE-AAC) (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 64 kb/s
  
      Stream #0:2: Unknown: none
  
  Output #0, mp4, to 'testConcat.mp4':
  
    Metadata:
  
      encoder         : Lavf56.25.101
  
      Stream #0:0: Video: h264 ([33][0][0][0] / 0x0021), yuv420p, 960x540 [SAR 1:1 DAR 16:9], q=2-31, 1561 kb/s, 25 fps, 25 tbr, 90k tbn, 90k tbc
  
      Stream #0:1: Audio: aac ([64][0][0][0] / 0x0040), 44100 Hz, stereo, 64 kb/s
  
  Stream mapping:
  
    Stream #0:0 -> #0:0 (copy)
  
    Stream #0:1 -> #0:1 (copy)
  
  Press [q] to stop, [?] for help
  
  [mp4 @ 0x3255080] Non-monotonous DTS in output stream 0:1; previous: 253952, current: 250488; changing to 253953. This may result in incorrect timestamps in the output file.
  
  [mp4 @ 0x3255080] Non-monotonous DTS in output stream 0:1; previous: 253953, current: 252536; changing to 253954. This may result in incorrect timestamps in the output file.
  
  [mp4 @ 0x3255080] Non-monotonous DTS in output stream 0:1; previous: 754296, current: 751464; changing to 754297. This may result in incorrect timestamps in the output file.
  
  [mp4 @ 0x3255080] Non-monotonous DTS in output stream 0:1; previous: 754297, current: 753512; changing to 754298. This may result in incorrect timestamps in the output file.
  
  [mp4 @ 0x3255080] Non-monotonous DTS in output stream 0:1; previous: 974696, current: 971964; changing to 974697. This may result in incorrect timestamps in the output file.
  
  [mp4 @ 0x3255080] Non-monotonous DTS in output stream 0:1; previous: 974697, current: 974012; changing to 974698. This may result in incorrect timestamps in the output file.
  
  [mp4 @ 0x3255080] Non-monotonous DTS in output stream 0:1; previous: 1340604, current: 1337112; changing to 1340605. This may result in incorrect timestamps in the output file.
  
  [mp4 @ 0x3255080] Non-monotonous DTS in output stream 0:1; previous: 1340605, current: 1339160; changing to 1340606. This may result in incorrect timestamps in the output file.
  
  [mp4 @ 0x3255080] Non-monotonous DTS in output stream 0:1; previous: 1746712, current: 1742832; changing to 1746713. This may result in incorrect timestamps in the output file.
  
  [mp4 @ 0x3255080] Non-monotonous DTS in output stream 0:1; previous: 1746713, current: 1744880; changing to 1746714. This may result in incorrect timestamps in the output file.
  
  [mp4 @ 0x3255080] Non-monotonous DTS in output stream 0:1; previous: 2119664, current: 2116800; changing to 2119665. This may result in incorrect timestamps in the output file.
  
  [mp4 @ 0x3255080] Non-monotonous DTS in output stream 0:1; previous: 2119665, current: 2118848; changing to 2119666. This may result in incorrect timestamps in the output file.
  
  [mp4 @ 0x3255080] Non-monotonous DTS in output stream 0:1; previous: 2274496, current: 2272032; changing to 2274497. This may result in incorrect timestamps in the output file.
  
  [mp4 @ 0x3255080] Non-monotonous DTS in output stream 0:1; previous: 2274497, current: 2274080; changing to 2274498. This may result in incorrect timestamps in the output file.
  
  [mp4 @ 0x3255080] Non-monotonous DTS in output stream 0:1; previous: 2685728, current: 2683044; changing to 2685729. This may result in incorrect timestamps in the output file.
  
  [mp4 @ 0x3255080] Non-monotonous DTS in output stream 0:1; previous: 2685729, current: 2685092; changing to 2685730. This may result in incorrect timestamps in the output file.
  
  [mp4 @ 0x3255080] Non-monotonous DTS in output stream 0:1; previous: 2850980, current: 2847096; changing to 2850981. This may result in incorrect timestamps in the output file.
  
  [mp4 @ 0x3255080] Non-monotonous DTS in output stream 0:1; previous: 2850981, current: 2849144; changing to 2850982. This may result in incorrect timestamps in the output file.
  
  [mp4 @ 0x3255080] Non-monotonous DTS in output stream 0:1; previous: 3033464, current: 3030552; changing to 3033465. This may result in incorrect timestamps in the output file.
  
  [mp4 @ 0x3255080] Non-monotonous DTS in output stream 0:1; previous: 3033465, current: 3032600; changing to 3033466. This may result in incorrect timestamps in the output file.
  
  [mp4 @ 0x3255080] Non-monotonous DTS in output stream 0:1; previous: 3384856, current: 3381588; changing to 3384857. This may result in incorrect timestamps in the output file.
  
  [mp4 @ 0x3255080] Non-monotonous DTS in output stream 0:1; previous: 3384857, current: 3383636; changing to 3384858. This may result in incorrect timestamps in the output file.
  
  [mp4 @ 0x3255080] Non-monotonous DTS in output stream 0:1; previous: 3760468, current: 3757320; changing to 3760469. This may result in incorrect timestamps in the output file.
  
  [mp4 @ 0x3255080] Non-monotonous DTS in output stream 0:1; previous: 3760469, current: 3759368; changing to 3760470. This may result in incorrect timestamps in the output file.
  
  [mp4 @ 0x3255080] Non-monotonous DTS in output stream 0:1; previous: 3990792, current: 3988404; changing to 3990793. This may result in incorrect timestamps in the output file.
  
  [mp4 @ 0x3255080] Non-monotonous DTS in output stream 0:1; previous: 3990793, current: 3990452; changing to 3990794. This may result in incorrect timestamps in the output file.
  
  [mp4 @ 0x3255080] Non-monotonous DTS in output stream 0:1; previous: 4295604, current: 4291812; changing to 4295605. This may result in incorrect timestamps in the output file.
  
  [mp4 @ 0x3255080] Non-monotonous DTS in output stream 0:1; previous: 4295605, current: 4293860; changing to 4295606. This may result in incorrect timestamps in the output file.
  
  [mp4 @ 0x3255080] Non-monotonous DTS in output stream 0:1; previous: 4750564, current: 4746924; changing to 4750565. This may result in incorrect timestamps in the output file.
  
  [mp4 @ 0x3255080] Non-monotonous DTS in output stream 0:1; previous: 4750565, current: 4748972; changing to 4750566. This may result in incorrect timestamps in the output file.
  
  [mp4 @ 0x3255080] Non-monotonous DTS in output stream 0:1; previous: 5025452, current: 5022108; changing to 5025453. This may result in incorrect timestamps in the output file.
  
  [mp4 @ 0x3255080] Non-monotonous DTS in output stream 0:1; previous: 5025453, current: 5024156; changing to 5025454. This may result in incorrect timestamps in the output file.
  
  [mp4 @ 0x3255080] Non-monotonous DTS in output stream 0:1; previous: 5271964, current: 5269068; changing to 5271965. This may result in incorrect timestamps in the output file.
  
  [mp4 @ 0x3255080] Non-monotonous DTS in output stream 0:1; previous: 5271965, current: 5271116; changing to 5271966. This may result in incorrect timestamps in the output file.
  
  [mp4 @ 0x3255080] Non-monotonous DTS in output stream 0:1; previous: 5707340, current: 5704776; changing to 5707341. This may result in incorrect timestamps in the output file.
  
  [mp4 @ 0x3255080] Non-monotonous DTS in output stream 0:1; previous: 5707341, current: 5706824; changing to 5707342. This may result in incorrect timestamps in the output file.
  
  [mp4 @ 0x3255080] Non-monotonous DTS in output stream 0:1; previous: 6003784, current: 6001128; changing to 6003785. This may result in incorrect timestamps in the output file.
  
  [mp4 @ 0x3255080] Non-monotonous DTS in output stream 0:1; previous: 6003785, current: 6003176; changing to 6003786. This may result in incorrect timestamps in the output file.
  
  [mp4 @ 0x3255080] Non-monotonous DTS in output stream 0:1; previous: 6371816, current: 6368040; changing to 6371817. This may result in incorrect timestamps in the output file.
  
  [mp4 @ 0x3255080] Non-monotonous DTS in output stream 0:1; previous: 6371817, current: 6370088; changing to 6371818. This may result in incorrect timestamps in the output file.
  
  [mp4 @ 0x3255080] Non-monotonous DTS in output stream 0:1; previous: 6875944, current: 6872544; changing to 6875945. This may result in incorrect timestamps in the output file.
  
  [mp4 @ 0x3255080] Non-monotonous DTS in output stream 0:1; previous: 6875945, current: 6874592; changing to 6875946. This may result in incorrect timestamps in the output file.
  
  [mp4 @ 0x3255080] Non-monotonous DTS in output stream 0:1; previous: 7042528, current: 7040124; changing to 7042529. This may result in incorrect timestamps in the output file.
  
  [mp4 @ 0x3255080] Non-monotonous DTS in output stream 0:1; previous: 7042529, current: 7042172; changing to 7042530. This may result in incorrect timestamps in the output file.
  
  [mp4 @ 0x3255080] Non-monotonous DTS in output stream 0:1; previous: 7314556, current: 7311780; changing to 7314557. This may result in incorrect timestamps in the output file.
  
  [mp4 @ 0x3255080] Non-monotonous DTS in output stream 0:1; previous: 7314557, current: 7313828; changing to 7314558. This may result in incorrect timestamps in the output file.
  
  [mp4 @ 0x3255080] Non-monotonous DTS in output stream 0:1; previous: 7541156, current: 7537572; changing to 7541157. This may result in incorrect timestamps in the output file.
  
  [mp4 @ 0x3255080] Non-monotonous DTS in output stream 0:1; previous: 7541157, current: 7539620; changing to 7541158. This may result in incorrect timestamps in the output file.
  
  [mp4 @ 0x3255080] Non-monotonous DTS in output stream 0:1; previous: 7795620, current: 7791588; changing to 7795621. This may result in incorrect timestamps in the output file.
  
  [mp4 @ 0x3255080] Non-monotonous DTS in output stream 0:1; previous: 7795621, current: 7793636; changing to 7795622. This may result in incorrect timestamps in the output file.
  
  [mp4 @ 0x3255080] Non-monotonous DTS in output stream 0:1; previous: 8063972, current: 8059716; changing to 8063973. This may result in incorrect timestamps in the output file.
  
  [mp4 @ 0x3255080] Non-monotonous DTS in output stream 0:1; previous: 8063973, current: 8061764; changing to 8063974. This may result in incorrect timestamps in the output file.
  
  [mp4 @ 0x3255080] Non-monotonous DTS in output stream 0:1; previous: 8063974, current: 8063812; changing to 8063975. This may result in incorrect timestamps in the output file.
  
  [mp4 @ 0x3255080] Non-monotonous DTS in output stream 0:1; previous: 8350532, current: 8347248; changing to 8350533. This may result in incorrect timestamps in the output file.
  
  [mp4 @ 0x3255080] Non-monotonous DTS in output stream 0:1; previous: 8350533, current: 8349296; changing to 8350534. This may result in incorrect timestamps in the output file.
  
  [mp4 @ 0x3255080] Non-monotonous DTS in output stream 0:1; previous: 8656496, current: 8652420; changing to 8656497. This may result in incorrect timestamps in the output file.
  
  [mp4 @ 0x3255080] Non-monotonous DTS in output stream 0:1; previous: 8656497, current: 8654468; changing to 8656498. This may result in incorrect timestamps in the output file.
  
  [mp4 @ 0x3255080] Non-monotonous DTS in output stream 0:1; previous: 8902276, current: 8899380; changing to 8902277. This may result in incorrect timestamps in the output file.
  
  [mp4 @ 0x3255080] Non-monotonous DTS in output stream 0:1; previous: 8902277, current: 8901428; changing to 8902278. This may result in incorrect timestamps in the output file.
  
  [mp4 @ 0x3255080] Non-monotonous DTS in output stream 0:1; previous: 9159476, current: 9156924; changing to 9159477. This may result in incorrect timestamps in the output file.
  
  [mp4 @ 0x3255080] Non-monotonous DTS in output stream 0:1; previous: 9159477, current: 9158972; changing to 9159478. This may result in incorrect timestamps in the output file.
  
  [mp4 @ 0x3255080] Non-monotonous DTS in output stream 0:1; previous: 9468220, current: 9465624; changing to 9468221. This may result in incorrect timestamps in the output file.
  
  [mp4 @ 0x3255080] Non-monotonous DTS in output stream 0:1; previous: 9468221, current: 9467672; changing to 9468222. This may result in incorrect timestamps in the output file.
  
  [mp4 @ 0x3255080] Non-monotonous DTS in output stream 0:1; previous: 9748248, current: 9744336; changing to 9748249. This may result in incorrect timestamps in the output file.
  
  [mp4 @ 0x3255080] Non-monotonous DTS in output stream 0:1; previous: 9748249, current: 9746384; changing to 9748250. This may result in incorrect timestamps in the output file.
  
  frame= 5637 fps=0.0 q=-1.0 Lsize=   45617kB time=00:03:45.60 bitrate=1656.4kbits/s    
  
  video:43701kB audio:1792kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.272048%
  
  Total time running concat: 0.451297044754 seconds

  This process is absolutely key to my current project so any help or clarification would be really appreciated.

• How to configure and validate a Funnel in Piwik Analytics

  16 janvier 2017, par InnoCraft — Community

  In the last blog post we have covered how the conversion Funnel plugin enriches your Piwik experience. This post will focus on how to configure and validate your funnel in Piwik so you get the correct data when you view the funnel reports. When you set up a funnel, it is crucial to have it configured correctly as the funnel report will be only as good as its configuration. When we built this Funnel feature, we focused on making the configuration and validation real simple because it is so important to get it right.

  To recap quickly : A Funnel defines a series of steps that you expect your visitors to take on their way to converting a goal or a sale. Funnels, a premium feature for Piwik developed by InnoCraft, lets you define funnels so you can improve your websites and mobile apps based on this data. Learn more about Funnel.

  Configuring a funnel

  As you will notice Funnels integrates nicely into the Piwik Goals management. You can configure a funnel whenever you create or update a goal. You can access the Goals Management either via “Administration => Goals” or via the reporting menu “Goals => Manage”. Then click on either “Add a new goal” or select an existing goal to edit it. At the bottom of the goal form, you will see a new row letting you configure a funnel. As with all our premium features we focused on displaying lots of inline help and explain directly in the UI what a funnel is about, what the steps are in order to configure a funnel, how a funnel helps you and more. This lets you use the Funnel feature even if you have never created or analyzed a funnel before.

  Preparing your Funnel configuration

  Before starting to configure a Funnel we usually have a brainstorm session identifying the funnels on a website or app and the paths we expect users to take there. Once we have identified each step, we click through those identified pages in our website and we note the URLs for each page as the URLs will be needed when you configure a funnel.

  Setting up a Goal

  Once we have finished the planning phase it is time to log into Piwik. We start by either adding a new goal or selecting an existing goal. If you are unfamiliar with setting up goals, have a look at the Piwik Goals user guide. At the bottom of a goal form when you create or update a goal, you can configure your funnel. The UI will first explain you everything about Funnels, what they are, how they help you and which steps you need to take in order to configure it.

  Configuring Funnel steps

  We start by configuring the steps we have identified in the planning phase. Those are the steps we expect our users to take when they convert a goal or purchase something. Now we need to add a step for each page we expect users to take, each step consists of a name and a pattern.

  The name will be shown to you in the funnel reporting so think of a good name that describes each step best, for example “Product”, “Cart”, “Checkout” and “Order”.

  The pattern is needed to define when a visitor will enter this step. Here it comes in handy to have already notes for each URL from the planning phase. You can select lots of different patterns based on “URL Path”, “URL” and “URL parameter”. For example “URL starts with”, “Path ends with”, “URL contains”, “URL matches the regular expression”, and more. Most tools make this configuration unnecessarily hard because they only allow you to choose from one or two patterns (only complicated pattern like regular expressions) and they don’t let you validate whether the URL you have in mind actually matches the pattern. There are three ways to validate your step configurations.

  

  Validating funnel steps

  When we configure a funnel, we validate our steps in the following three ways.

  1. Via the help icon next to the step configuration

  When you click on the help icon, you will receive valuable tips about configuring steps, what “required” means and how to match popular pages. It will also show you a list of all URLs that were tracked in your Piwik in the past and match your specified pattern. For example say you specify a pattern “Path starts with /products”, then Piwik will list all URLs that were tracked in the past matching this pattern. This lets you validate whether your pattern actually matches the URLs you had in mind. It will also show you if the pattern doesn’t match any known URL which can indicate that your configuration may be wrong.

  

  2. Via the URL validator

  Below the steps configuration you find a form field that lets you enter any URL.

  

  We recommend to enter each URL that you have noted before in the planning phase. Once you enter a URL, the configurations will be validated immediately and the result will be shown to you in the step configuration. When a step matches your specified URL, the background will become green, when a step does not match the URL, the background will be red.

  

  If the URL does not match the expected step, simply change your step configuration and the steps will be re-validated as you change the configuration. This way you will see instantly as soon as you got the configuration right.

  What you don’t want is that either all of your steps don’t match (red background) or that several steps match a certain URL (green background). When several step match one URL, then one visitor might enter several funnel steps on just one page. This usually indicates a problem with the step configuration.

  3. Manual funnel validation

  After we have created or updated the goal (more about this soon), we always test a funnel configuration manually. This means we now open our website and click through the pages that we hand in mind and check afterwards whether the steps we took actually appear in the funnel report as expected. This is just another safety net to make sure your funnel configuration is right.

  It is really crucial to have a correct funnel configuration as otherwise the shown data in the funnel reports might not be as helpful. That’s why we focused so much on making the validation part real easy.

  Activating and saving the funnel

  Once you are happy with your configuration, it is time to activate your funnel. As soon as you activate your funnel, a report for this funnel will be generated and the links and reports for this funnel will be visible in the UI. If you are later no longer interested in the funnel, simply deactivate the funnel so it won’t appear in the reporting UI anymore.

  

  To save your funnel configuration simply click on either “Add goal” or “Update goal”. The funnel will be automatically saved whenever you update your goal.

  Goals Management

  The funnel plugin also enriches the list of goals in the Piwik goal management. At a glance you can see whether a funnel for a goal is configured and activated (green tick in the funnel column), whether a funnel is configured but not activated (grey tick in the funnel column) or whether no funnel is configured for a goal (no tick at all).

  

  How to get Funnels and related features

  You can get Funnels on the Piwik Marketplace. If you want to learn more about Funnels you might be also interested in the Funnel User Guide and the Funnel FAQ.

  Similar to Funnels we also offer Users Flow which lets you visualize the flow of your users and visitors across several interactions.

• What’s new in Piwik 2.16.0 ?

  1er février 2016, par Matthieu Aubry — About, Development, Uncategorized

  In this blog post we showcase what is new in Piwik 2.16.0 and why you should upgrade your Piwik to this latest release !

  Piwik 2.16.0 is currently in Release Candidate and you can already use it by following these simple instructions. Piwik 2.16.0 will be officially released in a few days.

  To see the list of all 250+ changes, read the Piwik 2.16.0 changelog.

  Long Term Support for Piwik 2.X

  Piwik 2.16.0 is our Long Term Support version for Piwik 2. Learn more about Piwik LTS.

  New : Custom Dimensions feature

  With Custom Dimensions you can assign any custom data to your visitors or actions (like pages, events, …) and then visualize the reports of how many visits, conversions, pageviews, etc. there were for each Custom Dimension. They are similar to Custom Variables see the comparison of Custom Dimensions and Custom Variables.

  The new Custom Dimensions plugin is available on the Piwik Marketplace.

  Learn more about creating, tracking, reporting, managing, segmenting custom dimensions in the Custom Dimensions user guide.

  

  

  

  View the list of all visitors who reached a specific goal

  All Goal reports now include a link below the Goal report summary, that lets you see in one click all users that have converted any of your Goals :

  

  Events reports : option to view all columns : min, max and avg values

  By default in Actions > Events report, the columns displayed are “Total events” (Total number of events) and “Total value” (the sum of event values). It is now possible to click on the footer icon to view more detailed columns about event values : minimum event value, maximum event value, and average event value.

  

  Allow zoom to country in realtime visitor map

  In the real time map in Piwik (which displays your users activity appearing in real time !), it is now possible to zoom on a given country :

  

  Export all Records : new ‘all’ option in the Row limit selector

  It is now possible to export all of the data in your reports directly from the user interface ! Select ‘all’ in the row limit selector before exporting your data reports :

  

  New themes on the Marketplace !

  Feel like a change of colors ? Try out the new community submitted Piwik Themes on the Marketplace ! Learn how to install a new theme in Piwik (in only a few clicks).

  

  Let Super User view and edit segments created by other users

  As a Super User of Piwik, it can be very useful to view all Custom Segments created by all users. Starting in Piwik 2.16.0 any Super User can now view all Segments for a given website in the Segment selector :

  • Segments that are shared with All users will now appear below a section “Shared with you :” (a segment can be shared to all users by any admin user by selecting “This segment is visible to All Users” in the Segment editor)
  • Segments that are not shared with anyone are now also visible under the section “Visible to you because you have Super User access :”

  

  New segment ‘deviceBrand’ to segment by Device Brand

  You can now segment by device brands such as Apple, Samsung, LG, Google, Nokia, Sony, Lenovo, Alcatel, etc. The complete list of device brands you can use is listed on the Segmentation developer guide.

  

  New segment ‘actionType’ to view only particular Actions types (pagesviews, downloads, outlinks, events…)

  Use the new “Action type” segment to view only particular actions such as : pageviews, contents, sitesearches, events, outlinks and downloads.

  

  New segment : ‘actionUrl’ to view any actions that matches a given URL

  Use the new “Action URL” segment to view any action that matches a given URL, whether they are Pageviews, Site searches, Contents, Downloads or Events.

  

  New segment operators : “Starts with” and “Ends with”

  The new segment operators “Starts with” and “Ends with” can come handy when creating Custom Segments, and complement well the existing segment operators : Contains, Does not contain, Equals, Not equals, Greater than or equal to, Less than or equal to.

  

  Learn more about Segmentation in our user guides or in the Segmentation developer guide.

  Making Piwik more accessible

  Web accessibility refers to the inclusive practice of removing barriers that prevent interaction with, or access to applications or websites, by people with disabilities. When sites are correctly designed, developed and edited, all users have equal access to information and functionality.

  In Piwik 2.16.0, and with the help of high school students from the Catalyst Academy, we have made several improvements that make Piwik more accessible :

  • Menu now include the ARIA metadata (to make menus easier to navigate and use)
  • Page titles and various key tooltips have been improved (to give a better context to the data)
  • Keyboard access has been much improvement and Piwik is starting to be usable with the keyboard ! (this is very useful as many users are not able to use a mouse, and they should be able to view Piwik reports with the keyboard only)
  • ‘Skip to main content’ link (when pressing the TAB key) now skips the cursor to the page content.
  • Search bar was further improved : try it by pressing the ‘f’ key (useful to open any Piwik report or page without using the mouse)

  New user preference : display times either as 24h format or AM/PM format

  Users can now select whether times should be displayed in 24h format (16:20) or in AM/PM format (4:20pm)

  

  Other admins and Super Users are not visible to users with ‘admin’ permissions anymore

  Piwik 2.16.0 just became even more respectful of your privacy : any user you created and assigned an “admin” permission will not be able to view all other usernames anymore. This change was requested by many Piwik users who rightfully preferred not to disclose all usernames to any ‘admin’ user.

  As a result of this change, when a user with ‘admin’ permission (admin user) wants to give additional permission to another user (target user), the admin user will now need to know the target username and enter it in the Manage Users interface :

  

  New Config file viewer

  A new menu entry Administration > Diagnostics > Config file, lets Super Users view all config values in the UI :

  This new screen serves several purposes :

  • help Piwik administrators discover and learn about all the possible config file settings that Piwik offers.
  • let Super Users and Admins easily view any overridden config.ini.php INI setting without having to open the config file on the server.

  

  New report ‘Personal settings > Custom Variables’ displays custom variable usage

  A new report visible to Super Users lets you see how your Custom Variables slots are being used, which ones are still unused, and how many times a given custom variable name was used.

  

  Learn more about Custom Variables.

  Improvements to Heartbeat feature to accurately count time spent on the last page

  The heartbeat feature which lets you accurately track how long do visitors spend on your website, has been improved in 2.16.0. If you would like to measure how long do people spend on your pages (even if they don’t interact with your website or app), then consider using the heartbeat feature. Learn more in our guide Accurately measure the time spent on each page.

  

  New AnonymousPiwikUsageMeasurement plugin
  

  AnonymousPiwikUsageMeasurement plugin was created for those who would like to measure how their Piwik services is being used. This plugin also sends anonymised tracking data to our demo-anonymous.piwik.org which will help us learn how your Piwik is used and how we could improve the application. Learn more about AnonymousPiwikUsageMeasurement plugin.

  

  Show a warning when Piwik is used as a SuperUser via HTTP

  It is highly recommended to use HTTPS (SSL) for your Piwik server. If you are logged in as a Super User and viewing any Administration pages, you will now see a warning notification message at the top of the screen inviting you to use HTTPS :

  

  MySQL 5.7+ support

  The awesome Piwik community has helped us identify several issues with MySQL 5.7 support and Piwik is now fully compatible with the latest MySQL version 5.7+. Piwik is officially compatible with MySQL >= 4.1 and up to Mysql 5.7 ! Piwik is also compatible with MariaDB.

  

  Better detection of new devices and robots

  Our Device Detector library can now detect many new types of devices : smart TVs, new tablets and mobile phones, and more. New bots were added to our list of bots to keep your analytics report meaningful.

  Learn more : What Device Detector is able to detect, About Device Detector.

  New Referrer Spammers

  Every week we keep updating our community-list of referrer spammers. More than 50 new spammers were added since the last Piwik release !

  Note that the list of referrer spammer is automatically updated every week in your Piwik, so you need to wait at most one week to benefit from the very latest list.

  Learn more about Stopping Referrer Spam in Analytics reports.

  

  Ability to support new SMS providers to send Scheduled Reports by text message

  When you create scheduled reports in Piwik, you can specify one or several email addresses (to send reports by email) and you can also configure phone numbers (so your reports are sent to your phone via text message). So far we only support one SMS Provider “Clockwork SMS” but it is now possible for anyone to create a very simple plugin that adds a new SMS Provider to Piwik.

  A new SMS Provider plugin was released on the Marketplace : FreeMobileMessaging. If you have a favorite SMS Provider, we encourage you to create a new plugin for it !

  Piwik PRO mentions

  A few new mentions of Piwik PRO were added into Piwik to let users know that they can get Professional Help, and additional services and products. For example a new widget was added to the default dashboard. If you provide your Piwik service to your own clients, maybe you would like to remove the Piwik PRO widget and other ads, see this FAQ : How do I remove from Piwik the links to “Piwik PRO” or to “Professional Services” ?

  Stability, Reliability and Performance

  Dozens of other bugs were fixed (including several Major bugs) and many small improvements are included in this release. All these changes make Piwik more stable and reliable, as well as easier to troubleshoot and maintain. We are proud to be able to offer Piwik 2.16.0 as our Long Term Support release !

  If you have any feedback, questions, suggestion, or bug to report, please join our Piwik Community Forums.

  We hope you will love this 2.16.0 release as much as we loved making it.

  Happy Analytics !