Recherche avancée

Sur d’autres sites (6375)

• j2k/jpeg2000 : split data pointer in int & float.

  30 mai 2013, par Michael Niedermayer

  j2k/jpeg2000 : split data pointer in int & float.
  This fixes a TODO item and unifies both decoders structures
  
  It also fixes undefined behavior due to aliasing violations
  I choose 2 fields instead of a union because mistakely using the
  
  wrong type with a union will lead to hard to debug "wrong output"
  
  while with 2 fields mistakely using the wrong type will crash
  
  with a null pointer derefernce which is much easier to debug
  Signed-off-by : Michael Niedermayer <michaelni@gmx.at>
  

  • [DH] libavcodec/j2k.c
  • [DH] libavcodec/j2k.h
  • [DH] libavcodec/j2kdec.c
  • [DH] libavcodec/j2kenc.c
  • [DH] libavcodec/jpeg2000.c
  • [DH] libavcodec/jpeg2000.h
  • [DH] libavcodec/jpeg2000dec.c

• 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.

• Proxying an RTSP url using an RTSP Proxy Server

  21 juin 2018, par Sleeba Paul

  I have a use case where I need to restream an RTSP URL.

  For all the below cases, Live555 is built locally by cloning the source.

  For all the below cases, required ports are opened for RTSP in respective servers.

  First I set up a file to be streamed using Live555MediaServer. This is in an AWS instance (AWS1).

  ./Live555MediaServer ashi.webm gives

  rtsp://public_IP_of_instance:8554/ashi.web

  I check whether an incoming stream is working or not, by trying to play it in VLC player. This incoming stream is working fine and playing well on VLC.

  Now, to restream, I tried Live555ProxyServer. Now incoming stream from AWS1 is restreamed to another URL by running Live555ProxyServer on my Mac.

  ./Live555ProxyServer rtsp://public_IP_of_instance_one:8554/ashi.web gives,

  rtsp://localhost:8554/ProxyStream

  This URL is also playable in VLC.

  Now I setup another AWS instance (AWS2) and run ProxyServer on it, listening to AWS1.

  That is,

  ./Live555ProxyServer rtsp://public_IP_of_instance_one:8554/ashi.web gives,

  rtsp://public_IP_of_instance_two:8554/ProxyStream

  This URL is not playable.

  I tried using -t flag for TCP instead of UDP. I tried checking the incoming RTSP stream with ffprobe and the stream is showing all the required details.

  What could be the possible reason ? What is the missing piece in this pipeline ? Do we’ve great industry-grade open source RTSP servers ?

  EDIT :

  I don’t know what is exactly happened, but using VLC as the client to check the stream was the problem. I moved to ffmpeg and tried to write it to a file using

  ffmpeg -i rtsp://public_IP_of_instance_two:8554/proxyStream -acodec copy -vcodec copy abc.webm

  So the stream from ProxyServer is fine.

  The lead to the change of client was the repeated warning from live555ProxyServer about outdated firmware explained here.

  I’m currently using VLC Version 3.0.3 Vetinari (Intel 64bit) in Mac which is the latest version. Maybe VLC is using an old version of Live555 internally.