Sur d’autres sites (14623)

• Unable to play webM file on chromium with Media Source Extensions. Works in firefox and vlc

  23 octobre 2018, par raul

  I’m currently trying to implement a video player using Media Source Extensions. Currently just a very simple proof of concept, following a tutorial I found here.

  I cloned their repo with all source code from github here and am testing the implementation on Chromium and Firefox with various video files.

  Everything worked well with the example webm files in the repo for both browsers.

  Next I tried to convert a video I downloaded from some random site using ffmpeg and mse-tools to "align the clusters" of the webm file using the following commands :

  ffmpeg -i randomvideo.mp4 -c:v libvpx -c:a libvorbis output.webm
  
  mse_webm_remuxer output.webm aligned.webm

  Again, all was well on both browsers.

  Finally, I wanted to convert a very simple animation I created in blender (rendered with h264 in mp4).

  I tried converting the resulting file using the same process as above and the file played normally on firefox, but did not load on chromium.

  I assume I am commiting some error when converting the file, but inspecting the attributes of the final file with vlc and ffprobe, I could not find any obvious problems.

  Any ideas as to what I am doing wrong ?

  One final test I did was to go to this site to get some sample webm files.

  I downloaded the "Big Buck Bunny Trailer in WebM" and "Elephants Dream as WebM File".

  Both files worked in firefox, but the "Elephants Dream" file would not play in chromium.

  I am on a linux machine (Arch Linux distro) with the following versions of the browsers :

  Chromium Version 69.0.3497.100 (Official Build) Arch Linux (64-bit)

  Firefox 62.0.3 (64-bit)

  I have shared the file I created from the blender animation (very small - only 36 KB) on google drive here in case anyone wants to check it out.

• Stream from MP4 file over RTSP with ffserver

  25 octobre 2019, par sirlion

  I’m trying to stream a mp4 file over RTSP using ffserver with no luck so far. I just want to stream directly from the file, without feeding from ffmpeg (no transcoding involved). But I’ve made it work with mpg video.

  Here is my ffserver config file :

  Port 8090
  
  BindAddress 0.0.0.0
  
  MaxHTTPConnections 2000
  
  MaxClients 1000
  
  MaxBandwidth 500000
  
  CustomLog -
  
  NoDaemon
  
  
  
  RTSPPort 7654
  
  RTSPBindAddress 0.0.0.0
  
  
  
  <stream>
  
      Format rtp
  
      File "/home/g/video_streaming/sample3-mpeg2.mpg"
  
  </stream>
  
  <stream>
  
      Format rtp
  
      File "/home/g/video.mp4"
  
  </stream>

  When I launch ffserver, everything seems fine based on the log output :

  $ ./dev/ffmpeg/ffserver -f ffserver-sample.conf
  
  ffserver version N-45673-gd0c27e8 Copyright (c) 2000-2012 the FFmpeg developers
  
    built on Oct 18 2012 10:36:52 with gcc 4.6 (Ubuntu/Linaro 4.6.3-1ubuntu5)
  
    configuration:
  
    libavutil      51. 76.100 / 51. 76.100
  
    libavcodec     54. 66.100 / 54. 66.100
  
    libavformat    54. 33.100 / 54. 33.100
  
    libavdevice    54.  3.100 / 54.  3.100
  
    libavfilter     3. 19.103 /  3. 19.103
  
    libswscale      2.  1.101 /  2.  1.101
  
    libswresample   0. 16.100 /  0. 16.100
  
  Thu Oct 18 11:54:22 2012 Opening file '/home/g/video.mp4'
  
  Thu Oct 18 11:54:22 2012 Opening file '/home/g/video.mp4'
  
  Thu Oct 18 11:54:23 2012 Opening file '/home/g/video_streaming/sample3-mpeg2.mpg'
  
  Thu Oct 18 11:54:23 2012 [mpeg @ 0x1dae3c0]max_analyze_duration 5000000 reached at 5005000
  
  Thu Oct 18 11:54:23 2012 Opening file '/home/g/video_streaming/sample3-mpeg2.mpg'
  
  Thu Oct 18 11:54:23 2012 [mpeg @ 0x1dae3c0]max_analyze_duration 5000000 reached at 5005000
  
  Thu Oct 18 11:54:23 2012 FFserver started.

  Finally, if I run ffplay in order to test the server, everything works fine for the mpg file, but not for the mp4 :

  $ ffplay rtsp://192.168.1.99:7654/test2-rtsp
  
  ffplay version N-45656-g916352f Copyright (c) 2003-2012 the FFmpeg developers
  
    built on Oct 17 2012 16:14:14 with gcc 4.4.5 (Ubuntu/Linaro 4.4.4-14ubuntu5.1)
  
    configuration:
  
    libavutil      51. 76.100 / 51. 76.100
  
    libavcodec     54. 66.100 / 54. 66.100
  
    libavformat    54. 33.100 / 54. 33.100
  
    libavdevice    54.  3.100 / 54.  3.100
  
    libavfilter     3. 19.103 /  3. 19.103
  
    libswscale      2.  1.101 /  2.  1.101
  
    libswresample   0. 16.100 /  0. 16.100
  
  rtsp://192.168.1.99:7654/test2-rtsp: Invalid data found when processing input
  
  
  
  Server's output:
  
  
  
  Thu Oct 18 11:57:51 2012 FFserver started.
  
  Thu Oct 18 11:58:01 2012 192.168.1.101 - - [DESCRIBE] "rtsp://192.168.1.99:7654/test2-rtsp RTSP/1.0" 200 167
  
  Segmentation fault (core dumped)

  I don’t really know what I could be missing. I’ve just read in the official doc that streaming from a file is kind of broken. Since I don’t really know if that’s up to date, I decided to give it a try here.

  Any help or suggestions ? Alternatives ?

• Easily track Events within Matomo Analytics thanks to Matomo Tag Manager

  7 juin 2019, par Matomo Core Team — Analytics Tips

  Easily track Events within Matomo Analytics thanks to Matomo Tag Manager

  Introduction

  In this article we’ll cover what events in Matomo Analytics are ; and how you can easily set them up thanks to Matomo Tag Manager.

  Key concepts within this article

  • Events
  • Quick definition of the Tag Management System
  • Matomo config
  • Creating triggers
  • Variables

  What are events in Matomo Analytics and why are they useful ?

  Events allow you to measure interactions on your website which are not defined by default. With them you can measure clicks on some elements of a page, such as, how visitors are interacting with dropdown menus, media players, scrolling behaviours etc. You can also use them to define goals which make them a key feature in Matomo Analytics. Learn more about tracking events in Matomo.

  You can easily access the Events report in Matomo Analytics by clicking on the Behaviour category :

  

  And you may read the following message and feel a bit frustrated :

  

  “There is no data for this report” is a nice way to say, “Hey, you are tracking just a tiny part of what Matomo Analytics can do for you.”

  Matomo is a great software, but it can’t guess what you want to track.

  In order for Matomo to register those event tracking interactions, you’ll need to explain it by adding a line of code similar to this one when the interaction happens :

   

  _paq.push(['trackEvent', 'Here you enter whatever you want', 'Here too', 'and here also']);

   

  Let’s imagine you want to track a click on an HTML button, your code will look something similar to this at the moment of the interaction :

  Click Me !

  As you can imagine, two main challenges will arise for non developers :

  1. How to access the source code ?
  2. How to define the interaction ?

  Luckily, Matomo Tag Manager makes those steps easy for you. Let’s see how the same tracking is implemented with Matomo Tag Manager.

  A quick definition of what Matomo Tag Manager is

  Matomo Tag Manager lets you manage all your tracking and marketing tags in one easy-to-access place. Please visit this page to learn more about Matomo Tag Manager. In order to start using it, you’ll need to copy/paste a tracking code, named a “container”, within the section of your pages.

  Once the container is on your website, all you need to do is to follow these simple steps :

  1. Add a Matomo Tag.
  2. Assign the condition to fire the tag (what we call the trigger).
  3. Publish your work.
  4. And enjoy

  1 – Add a Matomo Event tracking code

  All you have to do here is click on “CREATE NEW TAG”

  

  Once selected, just mention how you’d like this tag to be named (it is for your internal purpose here so always use an explicit tag name) and the Matomo configuration (the default configuration setting will be fine in most of the cases) :

  

  Then Matomo Tag Manager will ask you the type of tracking you’d like to deploy, in this case, this is an event so select “Event” :

  

  Then all you need is to indicate the values you’d like to push through your event :

  

  To put it in perspective, all we did here through Matomo Tag Manager was implement the equivalent of the following line of code :

  _paq.push(['trackEvent', 'Element interactions', 'Click button', 'Click Me']);

  Let’s now see how can we do this on click code part which we call a trigger.

  2 – Assign the condition to fire the tag

  In order to execute the event we’ll need to define when it will happen. You do this by clicking on Create a new trigger now :

  

  As the interaction we’d like to track is happening when a click occurs, it will be a click trigger, and as our button is not a link, we’ll select All Elements Click :

  

  Once selected you’ll need to be precise on the condition in which the event will be triggered. In this case we do not want to have events pushed every time someone is clicking on something on our website. We only want to track when they click on this specific button. That’s the reason why our trigger is set to fire only when the click occurs on an element which has an id and has the value “cta” :

  Once you click on the green button named CREATE NEW TRIGGER, you validate the tag by clicking on CREATE NEW TAG :

  

  

  Then you can move to the last part.

  3 – Publish your work

  Tag Managers are very powerful as they allow you to easily execute any JavaScript code, CSS or even text content on your websites.

  That’s why when you create your tag it doesn’t go live straight away on your website. In order to do this you need to publish your tag and this is what the “Publish” category is designed for :

  

  After that, click on the second button if you’re confident your tag and trigger are both ready to go live :

  

  4 – Enjoy

  Well done. As your tag is now live, every click made on this button will now be pushed to your Matomo Analytics account within :
  

  1. The visitor log report :

  

  2. The events report :

  

  You may now be asking, “That’s great, but can I collect something more exciting than clicks ?” 

  Of course you can ! This is what the Matomo Tag Manager is all about.

  As long as you can express it through a trigger you can really push whatever you want to Matomo Analytics. You can track scrolling patterns, an element visible on the page like an image, an ad or the time spent on the page. The options are now open to you with Tag Manager.

  Give them a try ! Change the triggers, start playing around with variables and discover that the possibilities are endless.

  Happy analytics,
  Matomo team