Recherche avancée

Sur d’autres sites (7357)

• Matomo NAMED 2023 Hi-Tech Awards finalist

  1er août 2023, par Lance — Press Releases

  WELLINGTON, N.Z., April 20, 2023 – InnoCraft, the makers of world-leading open-source web analytics platform Matomo, has been named an ASX Hi-Tech Emerging Company of the Year finalist in the 2023 Hi-Tech Awards. 



  Matomo founder Matthieu Aubry says, “At Matomo, we believe in empowering individuals and organizations to make informed decisions about their digital presence. By providing an open-source website analytics platform, we have created a more transparent and trustworthy digital ecosystem. We are proud to be recognised as a finalist for the Hi-Tech Awards, and we will continue to work towards a more open and ethical digital landscape, and grow the business in New Zealand and worldwide.”



  About Matomo

  Matomo, launched in 2007 as an open-source, privacy-friendly Google Analytics alternative, is trusted by over 1.5 million websites in 220 countries and has been translated in over 50 languages. Matomo tracks and analyses online visits and traffic to give users a deeper understanding of their website visitors to drive conversions and revenue ; while keeping businesses compliant with privacy laws worldwide, such as the EU’s General Data Protection Regulation (GDPR) and The California Consumer Privacy Act (CCPA).

  Aubry says Matomo is performing extremely well internationally as consumers and organizations look for privacy-focused analytics solutions, with several European countries already ruling the use of Google Analytics illegal due to data transfers to the US. In addition, Matomo’s user increase was recognized earlier this year with W3Tech’s award for the best web analytics software in its Web Technologies of the Year 2022 – with previous winners including Google Analytics and Facebook Pixel.



  A record number of companies entered the 2023 Hi-Tech Awards, with entries coming in from across the country and from all areas of the Hi-Tech sector. This depth is reflected in the line-up of finalists this year, according to David Downs, Chair of the Hi-Tech Trust, who says the standard of entries continue to grow every year.

”

  The hi-tech sector continues to flourish and it’s fantastic to see the success that so many of our companies enjoy on the international stage. This sector continues to prove its resilience and is at the forefront of our export economy in turbulent times,” says Downs.



  The Hi-Tech Awards Gala Dinner will take place on Friday, the 23rd of June, in Christchurch. 


   

• Piwik 1.12, New Features, API Improvements, Stability — The Last Piwik 1.X Release

  30 mai 2013, par Piwik team — Development

  We are very excited to announce the immediate availability of Piwik v1.12 !

  • Download Link
  • How to update Piwik ?
  • List of all tickets closed : Changelog

  Piwik v1.12 is a major new release with four big new features, seven smaller new features, several API improvements and all together 82 tickets fixed. This is also the last major 1.X release, which means after this release we will be working on releasing Piwik 2.0. This also means that you should upgrade to PHP 5.3 or higher if you haven’t already, since Piwik 2.0 will only support PHP 5.3 and above.

  Finally, this release contains two breaking changes to the API. If you use the Piwik API click here or scroll down to see if you’re affected.

  Table of Contents :

  1. New Big Feature – Beta Release Channel
  2. New Big Feature – Segment Editor
  3. New Big Feature – Page Speed Reports
  4. New Big Feature – Device Detection Reports
  5. Other Improvements
  6. API Changes and Improvements
  7. What we’re working on
  8. Participate in Piwik
  9. Summary

  New Big Feature – Beta Release Channel

  

  For those of you who want to help test Piwik 2.0-beta releases as soon as they come up, we’ve made it easier to use our beta releases. Navigate to the Settings > General Settings page and click the The latest beta release radio button. You will then be able to upgrade to beta releases.

  This isn’t truly a major feature, but we think it’s just as important because it will allow us to create more beta releases and thus catch more bugs before we make a final release. This means more releases and more stability for you.

  New Big Feature – Segment Editor

  

  The Segment Editor is a long-awaited new feature that allows you to view, save and edit your segments.

  Piwik has supported segmentation (filtering visits and reports by arbitrary criteria, like browser family) for quite some time now, but it has never been possible to visually create and modify them. Nor could they be saved for later recall.

  Thanks to the eighty individuals and company who funded this feature, it is now possible to :

  • visually segment your visitors, instead of creating URLs.
  • save segments and easily switch between them, instead of remembering URLs.
  • get suggestions for segments that might be helpful to view.
  • learn more in the Segmentating Analytics reports user documentation..

  New Big Feature – Page Speed Reports

  You can now see how long it took your webserver to generate and send pages over HTTP through the new Avg. Generation Time metric.

  This metric can be viewed on both the Pages and Page Titles reports :

  

  And the average page generation time for all the pages in your website/webapp is displayed on the visitors overview :

  

  You can use this new information to benchmark your webapp and web server.

  New Big Feature – Device Detection Reports

  Piwik 1.12 also includes a new plugin that provides reports on the device types (tablet, desktop, smartphone, etc.), device brands (Apple, Google, Samsung, etc.) and device models (iPad, Nexus 7, etc.) your visitors use to access your website :

  

  The new plugin also enhances Operating system detections (detecting sub versions of Linux, Windows, and more).

  Note : This plugin is not enabled by default, but will be in Piwik 2.0. If you want to view these reports now, you can activate the plugin in the Installed Plugins admin page. Navigate to Visitors > Devices to see the new reports. You may also use the new (beta) ‘Device type’.

  The new plugin was developed with the support of Clearcode.cc our technology partner

  

  Other improvements

  Majestic SEO Metrics

  

  We’ve added two new SEO metrics to the SEO widget, both of which are calculated by MajesticSEO.com. These metrics will tell you the number of external backlinks (the number of links to your site from other sites) and the number of referrer domains (the number of domains that link to your site).

  We thank the team at Majestic for their support and hard work in bringing you these metrics to your Piwik dashboards !

  Real-time Visitor Count Dashboard Widget

  

  There is now a simple new widget you can use to see the number of visitors, visits and actions that occurred in the last couple minutes. We call it the Real Time Visitor Counter !

  New segment parameter : siteSearchKeyword.

  There is now a new segment parameter you can use to segment your visits : siteSearchKeyword. This parameter will let you select visits that had site searches with a specific keyword.

  Ignore URL letter case when importing log files.

  We’ve added a new option to the log import script, –force-lowercase-path. When used, the importer will change URL paths to lowercase before tracking them. This way http://domain.com/MY/BLOG will be treated the same as http://domain.com/my/blog.

  Updated ISP Names

  

  We’ve also modified the Providers report so prettier and more up-to-date names of ISPs are displayed.

  Customize the background/text/axis color of graphs.

  

  It is now possible to change the background color, text color and/or axis color of the graph images generated by the ImageGraph plugin. To access this functionality, use the following URL query parameters when generating an image :

  • backgroundColor
  • textColor
  • axisColor

  For example :

  http://demo.piwik.org/index.php?module=API&method=ImageGraph.get&idSite=7&apiModule=UserSettings&apiAction=getBrowser&token_auth=anonymous&period=day&date=2013-03-21,2013-04-19&language=en&width=779&height=150&fontSize=9&showMetricTitle=0&aliasedGraph=1&legendAppendMetric=0&backgroundColor=efefef&gridColor=dcdcdc&colors=cb2026

  Send your users to a custom URL after they logout.

  If you manage a Piwik installation with many users and you want to send them to a custom page or website after they log out of Piwik, you can now specify the URL to redirect users after they log out.

  API Changes and Improvements

  BREAKING CHANGE – renamed segment parameters.

  The following segment parameters have been renamed :

  • continent renamed to : continentCode
  • browserName renamed to : browserCode
  • operatingSystem renamed to : operatingSystemCode
  • lat renamed to : latitude
  • long renamed to : longitude
  • region renamed to : regionCode
  • country renamed to : countryCode
  • continent renamed to : continentCode

  If you use one of the old segment parameter names, Piwik will throw an exception, so you should notice when you’re using an old name.

  BREAKING CHANGE – changes to the input & output of the Live.getLastVisitsDetails method.

  The following changes were made to the Live.getLastVisitsDetails API method :

  • The method no longer uses the maxIdVisit query parameter. It has been replaced by the filter_offset parameter.
  • Site search keywords are now displayed in a <siteSearchKeyword> element. They were formerly in <pageTitle> elements.
  • Custom variables with page scope now have ‘Page’ in their element names when displayed. For example, <customVariablePageName1>, <customVariablePageName2>, etc.

  Filter results of MultiSites.getAll by website name.

  It is now possible to filter the results of MultiSites.getAll by website name. To do this, set the pattern query parameter to the desired regex pattern.

  Get suggested values to use for a segment parameter.

  The new API method API.getSuggestedValuesForSegment can now be used to get suggested values for a segment parameter. This method will return a list of the most seen values (in the last 60 days) for a certain segment parameter. So for browserCode, this would return the codes for the browsers most visitors used in the last 60 days.

  Use extra tracking query parameters with the JS tracker (such as ‘lat’ & ‘long’).

  We’ve added a new method to the JavaScript tracker named appendToTrackingUrl. You can use this method to add extra query parameters to a tracking request, like so :

  _paq.push(['appendToTrackingUrl', 'lat=X&long=Y']);

  What we’re working on

  As we said above, Piwik v1.12 is the last in the 1.X series of releases. This means we are now officially working on Piwik 2.0.

  Piwik 2.0 will be a big release, to be sure, but it’s going to bring you more than just a couple new features and a bag of bug fixes. For Piwik 2.0 we will be revisiting the user needs and the ideals that originally prompted us to create Piwik in order to build our vision of the future of web analytics.

  Piwik 2.0 won’t just be a bigger, better web app, but a new platform for observing and analyzing the things that matter to you.

  Participate in Piwik

  Are you a talented developer or an experienced User Interface designer ? Or maybe you like to write documentation or are a marketing guru ?

  If you have some free time and if you want to contribute to one of the most awesome open source projects around, please get in touch with the Piwik team, or read this page to learn more…

  Summary

  For the full list of changes in Piwik 1.12 check out the Changelog.

  Thank you to the core developers, all the beta testers and users, our official supporters, the translators & everyone who reported bugs or feature requests. Also thank you to softwares we use, and the libraries we use.

  If you are a company and would like to help an important project like Piwik grow, please get in touch, it means a lot to us. You can also participate in the project —

  –> if you like what you read, please tell your friends and colleagues or write on your website, blog, forums, stackoverflow, etc. <–
  

  Peace. Enjoy !

• JavaFX MediaPlayer unable to play local m3u8 file

  3 mai 2017, par Lennart

  I want to show a live stream of a web cam in my JavaFX application using the MediaPlayer/MediaView. My attempt was to use ffmpeg to record a HLS and to play the resulting m3u8 file, but that throws the following exception (VLC plays the video without problems) :

  MediaException: UNKNOWN : com.sun.media.jfxmedia.MediaException: Could not create player! : com.sun.media.jfxmedia.MediaException: Could not create player!
  
      at javafx.scene.media.MediaException.exceptionToMediaException(MediaException.java:146)
  
      at javafx.scene.media.MediaPlayer.init(MediaPlayer.java:511)
  
      at javafx.scene.media.MediaPlayer.<init>(MediaPlayer.java:414)
  
      at de.fraunhofer.iosb.ias.flow.assessment.management.monitor.MonitorViewController.testStream(MonitorViewController.java:203)
  
      ... 58 more
  
  Caused by: com.sun.media.jfxmedia.MediaException: Could not create player!
  
      at com.sun.media.jfxmediaimpl.NativeMediaManager.getPlayer(NativeMediaManager.java:274)
  
      at com.sun.media.jfxmedia.MediaManager.getPlayer(MediaManager.java:118)
  
      at javafx.scene.media.MediaPlayer.init(MediaPlayer.java:467)
  
      ... 60 more
  
  </init>

  I debugged the player creation and the error occurs inside the constructor of GSTMediaPlayer when GSTMediaPlayer.gstInitPlayer() is called. This native method returns the error code 257, which javafx maps to MediaError.ERROR_MEDIA_NULL.

  I used the following ffmpeg command to record the video :

  ffmpeg -hide_banner -y -rtbufsize 250MB -f dshow -pixel_format yuv420p -video_size 960x720 -i video="Logitech HD Pro Webcam C920" -c:v libx264 -crf 20 -pix_fmt yuv420p out.m3u8

  I’m pretty sure that the encoding matches the requirements of javafx, because if I change the output container from m3u8 to mp4, the video is played without problems using the exact same ffmpeg command.

  This is the output of ffprobe for the m3u8 file :

  Input #0, hls,applehttp, from 'out.m3u8':
  
    Duration: 00:00:24.23, start: 1.466667, bitrate: 0 kb/s
  
    Program 0
  
      Metadata:
  
        variant_bitrate : 0
  
      Stream #0:0: Video: h264 (High) ([27][0][0][0] / 0x001B), yuv420p, 960x720, 30 fps, 30 tbr, 90k tbn, 60 tbc

  And for the mp4 file :

  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'out.mp4':
  
    Metadata:
  
      major_brand     : isom
  
      minor_version   : 512
  
      compatible_brands: isomiso2avc1mp41
  
      encoder         : Lavf57.41.100
  
    Duration: 00:01:04.93, start: 0.000000, bitrate: 1676 kb/s
  
      Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p, 960x720, 1673 kb/s, 30 fps, 30 tbr, 10000k tbn, 60 tbc (default)
  
      Metadata:
  
        handler_name    : VideoHandler

  The resulting m3u8 file looks like this :

  #EXTM3U
  
  #EXT-X-VERSION:3
  
  #EXT-X-TARGETDURATION:9
  
  #EXT-X-MEDIA-SEQUENCE:0
  
  #EXTINF:8.333322,
  
  out0.ts
  
  #EXTINF:8.333333,
  
  out1.ts
  
  #EXTINF:7.133322,
  
  out2.ts
  
  #EXTINF:0.433333,
  
  out3.ts
  
  #EXT-X-ENDLIST

  Update : After I found this reference m3u file, I think that the problem is that the file is stored locally and isn’t delivered via HTTP. The video plays fine with this :

  Media media = new Media("http://download.oracle.com/otndocs/products/javafx/JavaRap/prog_index.m3u8");
  
  MediaPlayer player = new MediaPlayer(media);
  
  player.setAutoPlay(true);
  
  mediaView.setMediaPlayer(player);

  But after I downloaded the reference m3u and all of its segments and tried to open the local file like this, the error occurred again :

  File video = new File("H://Projects//Tools//ref//prog_index.m3u8");
  
  Media media = new Media(video.toURI().toString());
  
  MediaPlayer player = new MediaPlayer(media);
  
  player.setAutoPlay(true);
  
  mediaView.setMediaPlayer(player);

  I tried to change my m3u file so that the segements are referenced with absolute paths. I tried different notations (H:\f\out0.ts, H:/f/out0.ts, H://f//out0.ts, file:/H:/f/out0.ts, file:///H:/f/out0.ts), but I couldn’t get it to work.