Sur d’autres sites (4718)

• Revert "Merge commit ’3bc2e89c76e88ae6f1fd5287e0b11abcfc3c601c’" (Bump libavutil...

  16 décembre 2013, par Michael Niedermayer

  Revert "Merge commit ’3bc2e89c76e88ae6f1fd5287e0b11abcfc3c601c’" (Bump libavutil major version to account for the LLS API/ABI changes.)
  This reverts commit 792845e436ddc5f3ce11ba02535a3372919061f2, reversing
  
  changes made to 1d6666a6b828cca6c6b355a9b62f25607b1ced08.
  Bumping libavutil requires all libraries that use libavutil to have their
  
  major version bumped (yes breakage has been confirmed this is not a hypotheses)
  One case of breakage is due to new types being added to AVOptions and
  
  applications that linked to old libavutil and libswresample
  
  then trying to use old libavutil (its soname changed so the old isnt updated)
  
  and new swresample (its soame didnt change so it is updated)
  
  the new swresample contains AVOption types that the old libavutil doesnt
  
  know of thus the application attempting to access these avoptions
  
  fails
  AVOptions are used by all libs so the issue can potentially happen with
  
  any other lib, libswresample was just the first that showed the problem
  
  ive not checked if the other libs are affected currently by the same issue
  
  or not
  Also in addition to AVOptions, AVFrames are also defined in
  
  libavutil, bumping it without all libs that use AVFrames could lead to
  
  serious inconsistencies when 2 libs/app end up using 2 different libavutils
  The alternative of bumping all is still possible after this revert, if it
  
  turns out to be the preferred solution
  

  • [DH] doc/APIchanges
  • [DH] libavutil/version.h

• avcodec : move end zeroing code from av_packet_split_side_data() to avcodec_decode_sub...

  21 novembre 2013, par Michael Niedermayer

  avcodec : move end zeroing code from av_packet_split_side_data() to avcodec_decode_subtitle2()
  This code changes the input packet, which is read only and can in
  
  rare circumstances lead to decoder errors. (i run into one of these in
  
  the audio decoder, which corrupted the packet during av_find_stream_info()
  
  so that actual decoding that single packet failed later)
  
  Until a better fix is implemented, this commit limits the problem.
  
  A better fix might be to make the subtitle decoders not depend on
  
  data[size] = 0 or to copy their input when this is not the case.
  

  • [DH] libavcodec/avpacket.c
  • [DH] libavcodec/utils.c

• Date and segment comparison feature

  31 octobre 2019, par Matomo Core Team — Analytics Tips, Development

  Get a clearer picture with the date and segment comparison feature

  What can you do with it ? What are the benefits ?

  Make informed decisions faster by easily comparing different segments and dates with each other.

  Compare report data for multiple segments next to each other

  

  Directly compare the behaviour of visitors from different segments e.g. customers with accounts vs. customers without accounts. Segment comparisons are a powerful way to compare different audience ; learn which ones perform better ; and in what way their actions differ. 

  Compare report data for two time periods next to each other

  

  See how your website performs compared to the previous month/week/year. Including seeing trends over those periods. Say, your business always picks up at the same times within a year, or there’s a sag in business for every user segment over this year and the last except one.

  By being able to compare date ranges you are able to get a quick overview of trends and period to period performance. Has a campaign worked better in September than in October ? Get an instant look by having the side-by-side comparison in Matomo.

  What is it capable of ?

  It lets you ask the question, “What is different ?”

  If you look at reports you’ll only see how people behave overall and if you look at specific segments you’ll see how they behave at face value, however, if you compare data together you’ll be quickly informed on what makes them unique. This data is still there when you don’t use the comparison feature, it’s just buried. Comparing data highlights discrepancies and leads to important questions and answers.

  For example, perhaps some class of users have very low engagement on a specific day compared to the rest of your visitors, and perhaps those users are responsible for an outsized proportion of churn. 

  Who could benefit from it, and why ?

  Everyone can benefit from using it (and probably should use it). It’s yours to experiment with ! You shouldn’t feel restricted to only comparing between the current and last period, or having questions before you start comparing. Follow your instincts and see what pops out when data from different segments is laid out next to each other.

  Where can you find it in Matomo ?

  • Segment comparison is activated by the new icon in the segment selector

  

  • Date comparison can be found in the calendar section of Matomo

  

  • The list of active comparisons is visible at the top of the page for all pages that support comparison
  • Comparisons are visible in every report that supports comparing data, and reports that do not support it will display a message saying so

  How do you use it ?

  • To compare segments, click the icon in the segment selector
  • To compare periods, click the ‘compare’ checkbox in the period selector, then select what period you want to compare it against in the dropdown (previous period, previous year, or a custom range)
  • When comparisons are active, view your reports as normal

  Take it away !

  The comparison feature is a new tool from Matomo 3.12.0 that highlights discrepancies and differences in data that can lead to more clarity and understanding, so we’d encourage everyone to use it. 

  Try it out today in your Matomo and see the power behind this new data comparison mode !