Recherche avancée

Sur d’autres sites (7778)

• How to install a Matomo premium feature

  31 janvier 2018, par InnoCraft

  You may have noticed over the last few months that many fantastic new features have been launched on the Matomo Marketplace. As some of them are paid premium features, you may wonder if the process to install them is straightforward, if you can test them before, and whether there is any support behind it. No worries – we’ve got you covered ! This blog post will answer some questions you may have about getting your first premium plugin.

  So why are there some premium features ?

  Researching, building, documenting, testing and maintaining quality products take years of experience and months of hard work by the team behind the scenes. When you purchase a premium plugin, you get a fully working product and you directly help the Matomo core engineers to grow and fund the new Free Matomo versions and cool features.

  However, it is important for us to mention that Matomo will always be free, it is a Free software under GPLv3 license and it will always be the same.
  Want to know more about this ? Check out our FAQ about why there are premium features.

  Can I test a premium feature before a purchase ?

  Absolutely. There are two ways in order to do that :

  1. InnoCraft Matomo Cloud
  2. Matomo Marketplace

  1. InnoCraft Matomo Cloud

  The easiest way is to create a free trial account (one minute of your time) on our Matomo cloud service. You will then have the possibility to test all the premium features during a 30-day trial period. No credit card is required.

  

  Every premium feature can be trialled for free on the Matomo Cloud

  2. Matomo Marketplace

  The second way is to get the premium feature from the Matomo Marketplace. We have an easy and hassle-free 30-day money back guarantee period on each feature. This means that if you are not happy with a premium feature and you are within the 30-day period, then you will get a full refund for it. Guaranteed !

  How to purchase and install a premium feature ?

  Step 1 : Purchasing the feature

  In order to get a premium feature, just add it to the cart :

  

  Once done, go to your cart and complete the checkout process to confirm the order.

  When the order is confirmed, you immediately get your license key on the order confirmation page. You also receive the license key by email.

  Step 2 : Activating the feature in your Matomo

  Now that you have received the license key, it is time to activate the plugin in your Matomo :

  • Log in to your Matomo and go to “Administration => Marketplace
  • Copy / paste the license key into the license field at the top of the page and click “Activate”

  

  • The key will now be activated and you will see a couple of new buttons.

  

  • To install the premium feature(s) you just purchased in one click, simply click on “Install purchased plugins”. Alternatively, you can scroll down in the Marketplace to the premium feature you purchased and click on “Install”. You can also download the ZIP file on https://shop.matomo.org/my-account/downloads

  And that’s it. The installation of a premium feature is as easy as copy/pasting the license key and clicking a button. Because one license key is linked to all purchased premium features, you only need to enter the license key once. The next time you purchase a premium feature, you simply click on “Install” to have it up and running.

  Updating a premium feature

  Updates for premium features work just like regular plugin updates. When there is a new update available, you will see a notification in the Matomo UI and also receive an email (if enabled under “General Settings”). To upgrade the feature simply click on “Update” and you’re done.

  Which support is provided for each of those premium features ?

  Premium features represent most of our day to day activity, so you can be 100% sure that we will do our maximum in order to answer any of your questions regarding them. To be 100% transparent, we often receive answers from our customers telling us how impressed they are by the quality of the service we are offering.

  Have any questions ?

  We are happy to answer any questions you may have so feel free to get in touch with us.

  Thanks !

  The post How to install a Matomo premium feature appeared first on Analytics Platform - Matomo.

• avcodec_encode_video2 crash on MinGW32 (but not on MinGW64)

  27 février 2018, par ksb496

  I have been testing for years a software that I am developing, compiled only for 64-bit systems through Qt-MinGW64, without experiencing any kind of issue regarding video encoding (which is one of the features of such application). Recently, I have been attempting to build the corresponding x86 version of my software by compiling it with Qt-MingGW32.

  However, after bulding the same ffmpeg and x264 library versions to create the 32-bit versions and successfully linking them to my project, the application keeps crashing after few frames are encoded, due to segmentation fault error. This is very strange because, as I indicated before, it works flawlessly when compiled for 64-bit systems.

  I have also lost a considerable amount hours trying to combine a big amount of different versions of both ffmpeg and x264 libraries, but with no luck either. Neither it works when disabling threads both for x264 and ffmpeg libraries, hence it does not seem to be a win32 threading issue. Therefore, I have concluded that the error is most likely in my code, which by some chance beyond my comprehension tells ffmpeg to allocate the right amount of memory in the x64 version, but not in the x86 version.

  It must be pointed out also that before the avcodec_encode_video2 call, I do the following calls, among others, in order to allocate the memory associated to the corresponding items (AVFrame, AVCodec, etc.), such as

  avcodec_open2( my_codec_context, my_codec, &opt );
  
  my_av_frame=av_frame_alloc();

  More precisely, the details involving the code structure that I am using can be found here.

  Therefore, the error appears to be more subtle than just issues regarding uninitialized memory.

  Many thanks in advance.

  UPDATE :

  I have discovered the focus of the problem. For some reason, FFmpeg/x264 libraries behave abnormally in Win32 GUI applications compiled with Qt-MinGW32, while they run correctly in Win32 console applications, also compiled with Qt-WinGW32. I have proven this claim performing two dummy tests, in which the exact same piece of code is run through a console application and on a GUI application, succeeding in the first case and failing in the latter one. The code for such tests can be found below, along with the x264 and FFmpeg libraries used in my projects, together with instructions to build them in msys2 with MinGW32 :

  https://takeafile.com/?f=hisusinivi

  I have no idea whether it can be solved by simply tweaking the code or it is a serious bug involving an incompatibility issue. If it is the latter, should it be reported to the Qt/FFmpeg/x264 staff as a major bug ?

• Why does ffmpeg return a different framecount than ffprobe for the same file ?

  5 mars 2018, par Greg

  I’m trying to count the number of frames in a video but ffmpeg and ffprobe are giving me two different answers.

  $ time ffprobe -v error -count_frames -select_streams v:0 -show_entries stream=nb_read_frames -of default=nokey=1:noprint_wrappers=1 myvideo.mp4
  
  2858
  
  
  
  real    0m2.987s
  
  user    0m2.740s
  
  sys     0m0.172s

  When I check the same file with ffmpeg I get 2 more frames...

  $ time ffmpeg -y -i myvideo.mp4 -vcodec copy -acodec copy -f null /dev/null 2>&1 | grep 'frame=' | awk '{print $2}'
  
  2860
  
  
  
  real    0m0.127s
  
  user    0m0.080s
  
  sys     0m0.032s

  I used ffprobe to output all of the frames and count the number of "[FRAME]"s in the resultant output...

  ffprobe -i myvideo.mp4 -show_frames -v error | grep -o '\[FRAME\]' | wc -l
  
  2858

  Which as you can see shows the number ffprobe thought there were.

  Obviously I would prefer to use ffmpeg here because it is significantly faster than ffprobe and I am dealing with thousands of videos that need parsing and indexing. However the failure isn’t consistent across multiple videos ; sometimes it’s 1 out, other times it’s 2 or more...

  Unfortunately, I have been counting frames for the past two years using the ffmpeg method, so I have a significant library of videos to reprocess now ... he gulps... I guess its a good way to verify the readability of the files on the cluster... even so, its going to take probably a few weeks to recalculate all of the existing video frame sizes.