Recherche avancée

Sur d’autres sites (10250)

• Play MPEG-2 TS using MseStreamSource

  27 novembre 2022, par Nicolas Séveno

  I need to display a live video stream in a UWP application.

  



  The video stream comes from a GoPro. It is transported by UDP messages. It is a MPEG-2 TS stream. I can play it successfully using FFPlay with the following command line :

  



  ffplay -fflags nobuffer -f:v mpegts udp://:8554


  



  I would like to play it with MediaPlayerElement without using a third party library.

  



  According to the following page :
https://learn.microsoft.com/en-us/windows/uwp/audio-video-camera/supported-codecs
UWP should be able to play it. (I installed the "Microsoft DVD" application in the Windows Store).

  



  I receive the MPEG-2 TS stream with a UdpClient. It works well.
I receive in each UdpReceiveResult a 12 bytes header, followed by 4, 5, 6, or 7 MPEGTS packets (each packet is 188 bytes, beginning with 0x47).

  



  I created a MseStreamSource :

  



  _mseStreamSource = new MseStreamSource();
_mseStreamSource.Opened += (_, __) =>
{
    _mseSourceBuffer = _mseStreamSource.AddSourceBuffer("video/mp2t");
    _mseSourceBuffer.Mode = MseAppendMode.Sequence;
};
_mediaPlayerElement.MediaSource = MediaSource.CreateFromMseStreamSource(_mseStreamSource);


  



  This is how I send the messages to the MseStreamSource :

  



      UdpReceiveResult receiveResult = await _udpClient.ReceiveAsync();
    byte[] bytes = receiveResult.Buffer;
    mseSourceBuffer.AppendBuffer(bytes.AsBuffer());


  



  The MediaPlayerElement displays the message "video not supported or incorrect file name". (not sure of the message, my Windows is in French).

  



  Is it a good idea to use the MseAppendMode.Sequence mode ?
What should I pass to the AppendBuffer method ? The raw udp message including the 12 bytes header or each MPEGTS 188 bytes packet ?

  


• ASPSMS : a successful integration with Piwik

  3 octobre 2017, par Piwik Core Team — Development

  Have you ever wondered how an integration between a third party company and Piwik is possible ? What are the key factors for a good partnership ? This article describes our recent collaboration with a company for a mobile messaging integration.

  At Piwik, we are always looking for new functionalities to build and improve the work of our community members. ASPSMS, an innovative SMS Gateway & Messaging solutions provider got in contact with us in order to do just this.

  Why did we decide to partner with ASPSMS ?

  • Fast
  • Easy
  • Just works

  Those three words define the collaboration we had with ASPSMS and in the end everyone benefits.

  Stefan, one of our developers who did the integration into Piwik, says “Thanks to an easy to understand API the SMS integration was done in a couple of hours. We got SMS credits upfront for testing which helped a lot.”

  Using the ASPSMS integration, you can receive a daily or weekly SMS message listing the Key Performance Indicators of your website(s).

  ASPSMS is now part of Piwik through the Mobile messaging settings :

  

  As a company, how can I contribute to Piwik ?

  If, like ASPSMS, you are providing great services which can help Piwik final users take better decisions, do not hesitate to contact the Piwik core team.

  You can also start to develop your own, specific plugins, that you can freely publish on the Piwik marketplace.

  About ASPSMS

  VADIAN.NET AG is today one of the leading global providers of SMS solutions with more than 200,000 satisfied business clients. The product ASPSMS was launched in 2001. ASPSMS is a product of VADIAN.NET AG, a Swiss based Internet and Mobile Solutions provider.

  

  Learn more about ASPSMS.

• Introducing Improvements to the Opt-Out Form Feature

  18 septembre 2022, par Ben — About

  Matomo includes a built-in opt-out form that you can add to your website so you can provide your visitors with the choice to opt-out of Matomo tracking. Up until Matomo 4.12.0 the built-in opt-out form relied on iFrame technology which has become increasingly problematic due to browser changes and restrictions on setting third-party cookies.

  With our privacy-first approach, we’ve known for some time that we would eventually need a new way to provide this important opt-out functionality that would work most reliably in the myriad of contexts our users rely on it for.

  Embedding the opt-out form

  Matomo 4.12.0 introduces an improved opt-out. This provides two new options for embedding the opt-out on your website, either using the Matomo tracker code or as self-contained code.

  

  As with the iFrame method, the built-in opt-out code can be styled in Matomo to match your website, and provides a snippet which you can add to your website to show the opt-out feature to your users.

  Find out how to customise the opt-out form.

  Customising the opt-out form

  

  What does this mean for existing opt-out forms ?

  Although it is no longer possible to generate new iFrame embed code using the Matomo UI, the underlying opt-out feature is still fully supported and any existing iFrame opt-out form code embedded in websites will still work as before. It is recommended to migrate to one of the new opt-out form options as browser support for the iFrame opt-out will continue to decrease.

  To read more in depth information about the new opt-out functionality please refer to our new developer documentation for tracking opt-out.