Recherche avancée

Sur d’autres sites (8033)

• Piwik Analytics becomes Matomo to reflect Users’ Privacy Focus

  10 janvier 2018, par Matomo Core Team

  One of the world’s leading analytics software platforms is changing its name. Piwik is the sixth most-used web and mobile analytics computer solution worldwide. It is now changing its name to Matomo.

  The name change comes after 10 years of Piwik building its top analytics software, with great success. It is already used on over one million websites in more than 170 countries. Matomo will build on that success, and focus even more on privacy.

  ‘Privacy has become a huge concern worldwide’, says Matomo’s creator, Matthieu Aubry. ‘Privacy legislation is being developed in Europe, and we will be ahead of the game in being ready for those changes. We’ll grow in line with the law and regulation changes.’

  Matomo will lead the way in openness and transparency for its users. Its new name means honesty in Japanese.
  ‘Matomo will always be free and community-driven, just as Piwik was’, says Matthieu Aubry. ‘We have worked with hundreds of people to create the best open digital analytics solution in the world. We’re committed to giving every user full control of their data.’

  The change of name is appropriate as the Matomo platform moves into a new stage of growth. But for its community, little will obviously change. The same people will still be involved, and users will still get useful data to improve their own website. That data includes who visits their site, what they do there, how long they stay, and what they buy.
  Matomo is an all-in-one analytics solution that gives companies a 360 degree view of their users.

  ‘They can grow their business while still keeping 100% ownership of their data, and being fully compliant with privacy laws’, says Matthieu Aubry. ‘We’re more motivated than ever to building on that, so that Matomo stays ahead of the pack.’

  The platform can be fully customised with hundreds of plug-ins, integrations and configurations.

  Matomo’s updated website and new logo is now available on https://matomo.org.
  For further information, please contact the Matomo Team on hello@matomo.org

  The post Piwik Analytics becomes Matomo to reflect Users’ Privacy Focus appeared first on Analytics Platform - Matomo.

• Using ffmpeg to generate dash manifest and it cannot be played by dash.js

  18 mars 2019, par Punkhead

  I’m using ffmpeg to encode incoming stream via rtmp protocol, the code as following :

  ffmpeg -re -i rtmp://localhost:1935${StreamPath} -use_timeline 1 /
  
  -use_template 1 -window_size 10 -min_seg_duration 5000 -f dash out.mpd

  The manifest looks like this :

  <?xml version="1.0" encoding="utf-8"?>
  
  <mpd xmlns="urn:mpeg:dash:schema:mpd:2011" profiles="urn:mpeg:dash:profile:isoff-live:2011" type="static" mediapresentationduration="PT1M36.4S" minbuffertime="PT8.3S">
  
      <programinformation>
  
      </programinformation>
  
      <period start="PT0.0S">
  
          <adaptationset contenttype="video" segmentalignment="true" bitstreamswitching="true" framerate="30/1">
  
          <representation mimetype="video/mp4" codecs="avc1.640028" width="1920" height="1080" framerate="30/1">
  
              <segmenttemplate timescale="15360" initialization="init-stream$RepresentationID$.m4s" media="chunk-stream$RepresentationID$-$Number%05d$.m4s" startnumber="4">
  
                  <segmenttimeline>
  
                      <s t="384000" d="128000"></s>
  
                      <s d="71680"></s>
  
                      <s d="128000" r="4"></s>
  
                      <s d="56832"></s>
  
                      <s d="128000"></s>
  
                      <s d="72704"></s>
  
                  </segmenttimeline>
  
              </segmenttemplate>
  
          </representation>
  
      </adaptationset>
  
      <adaptationset contenttype="audio" segmentalignment="true" bitstreamswitching="true">
  
          <representation mimetype="audio/mp4" codecs="mp4a.40.2" bandwidth="128000" audiosamplingrate="44100">
  
              <audiochannelconfiguration schemeiduri="urn:mpeg:dash:23003:3:audio_channel_configuration:2011" value="2"></audiochannelconfiguration>
  
              <segmenttemplate timescale="44100" initialization="init-stream$RepresentationID$.m4s" media="chunk-stream$RepresentationID$-$Number%05d$.m4s" startnumber="4">
  
                  <segmenttimeline>
  
                      <s t="1099755" d="367616"></s>
  
                      <s d="205824"></s>
  
                      <s d="367616" r="4"></s>
  
                      <s d="162816"></s>
  
                      <s d="367616"></s>
  
                      <s d="207872"></s>
  
                  </segmenttimeline>
  
              </segmenttemplate>
  
          </representation>
  
      </adaptationset>
  
  </period>
  
  </mpd>

  When I try to play it on dash.js player, a error occured :

  [112] Parsing complete: ( xml2json: 3.50ms, objectiron: 1.76ms, total: 0.00526s) Debug.js:127 
  
  [116] SegmentTimeline detected using calculated Live Edge Time Debug.js:127 
  
  [118] MediaSource attached to element.  Waiting on open... Debug.js:127 
  
  [119] Manifest has been refreshed at Tue Jan 02 2018 01:57:35 GMT+0800 [1514829455.1] Debug.js:127 
  
  [155] MediaSource is open! Debug.js:127 
  
  [156] Duration successfully set to: 96.4 Debug.js:127 
  
  [157] Added 0 inline events Debug.js:127 
  
  [158] video codec: video/mp4;codecs="avc1.640028" Stream.js:225 
  
  Uncaught TypeError: Cannot read property 'type' of null
  
      at z (Stream.js:225)
  
      at C (Stream.js:285)
  
      at D (Stream.js:373)
  
      at E (Stream.js:398)
  
      at Object.d [as activate] (Stream.js:107)
  
      at y (StreamController.js:363)
  
      at MediaSource.c (StreamController.js:342)

  then it fails to playback...

  Is it because I didn’t set the parameters right on ffmpeg or this is a bug in dash.js ?

  I really stuck here !

• running ffmpeg.exe command on golang windows

  27 février 2018, par Mehak Ayub Awan

  c:\goWorkSpace\src\github.com\tus\tusd\cmd\tusd\bin\ffmpeg.exe -y -i c:\goWorkSpace\src\github.com\tus\tusd\cmd\tusd\data\ac629d87f876835d3720059eb3e5d8a7.bin  -vcodec h264 "E:\MP4Files/27.02.2018/PM.mp4" 

  My command is working in cmd but not on exec.command using this :

  exec.Command("cmd", "-c",c:\goWorkSpace\src\github.com\tus\tusd\cmd\tusd\bin\ffmpeg.exe -y -i c:\goWorkSpace\src\github.com\tus\tusd\cmd\tusd\data\ac629d87f876835d3720059eb3e5d8a7.bin  -vcodec h264 "E:\MP4Files/27.02.2018/PM.mp4")