Recherche avancée

Sur d’autres sites (6276)

• fate/cbs : Add an SEI test

  8 mai 2018, par Mark Thompson

  fate/cbs : Add an SEI test
  The artificial sample file sei-1.h264 contains five frames (IDR P B I B)
  
  and the following SEI message types :
  
  * Buffering period
  
  * Picture timing
  
  * Pan-scan rectangle (display as 4:3)
  
  * User data registered, containing A/53 closed captions (captions match
  
    frame content, including reordering)
  
  * Recovery point (at the I frame)
  
  * Display orientation (identity transformation)
  
  * Mastering display (with arbitrary contents)
  
  * Undefined SEI type 1234 (containing ascending bytes)
  

  • [DH] tests/fate/cbs.mak
  • [DH] tests/ref/fate/cbs-h264-sei-1

• HTML5 Progressive Streaming — no follow-up range requests

  20 septembre 2023, par user2333829

  I'm working on an embedded device that is recording video on the fly. I'd like to stream that to an HTML5 video element, using our own custom server. I have this almost working and would like some help.

  



  So far as I can tell, I've got libav / ffmpeg doing their job right. I encoded an mp4 in RAM with the moov atom at the start of the file. I've written this file to disk and it plays everywhere it should.

  



  The problem, I think, lies with how I'm responding to HTTP range requests. When I try to do a live stream, I get an initial range request from the browser / player (currently tried Chrome, Firefox, and VLC) for bytes:0-. I responded with some initial bytes. The browser / player actually plays this fine, but never asks again. So the live stream doesn't work, just the first 3 seconds or whatever.

  



  I've looked at the RFC spec of partial content, and my understanding is I'm doing what I should be... Clearly I'm not though. Here is an example of a request / response with Chrome as the requester :

  



  ---

  



  
get /live.mp4 HTTP/1.1
host: localhost:1235
connection: keep-alive
accept-encoding: identity;q=1, *;q=0
user-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.167 Safari/537.36
accept: */*
dnt: 1
accept-language: en-GB,en-US;q=0.9,en;q=0.8
range: bytes=0-


  



  
HTTP/1.1 206 Partial Content
Accept-Ranges: bytes
Content-Type: video/mp4
Content-Length: 182400
Content-Range: bytes 0-182399/*


  



  ---

  



  Again, with that request / response pair, Chrome plays the first 182400 bytes but never makes a second request. I thought having the '*' in Content-Range would make this happen...

  


• It’s January 28th : Let’s celebrate Data Privacy !

  29 janvier 2018, par Matomo Core Team

  It is a special Sunday here for us at Matomo, as today is international Data Privacy Day. The day was created in 2007 to raise awareness of the importance of data privacy for people and businesses worldwide.

  

  What is data privacy about ?

  Personal data refers to any data which is collected and can be linked to an individual human being such as phone records, credit card transactions, GPS position, IP addresses, browsing history… So basically, personal data refers to your identity online. That is why you should be highly concerned about sending your personal data (or your customers’ personal data) away. It is important to be aware of who is collecting the information and how it is being used.

  What big changes are happening in 2018 ?

  New privacy regulations GDPR comes into play next May 2018 : GDPR will bring about some changes (in the right direction) by making people and businesses aware of what data privacy means, and what they should be doing to protect their customers’ privacy. With these new regulations, data privacy awareness is reaching a critical milestone this year.

  How can I protect my privacy ?

  Here are a few tips to protect your privacy :

  • Educate yourself on the importance of privacy : the more informed you are the better.
  • Use open source solutions where you can keep full control of your own data (such as NextCloud instead of Dropbox and of course Matomo instead of Google Analytics),
  • Experiment with different online services to protect your data privacy, for example using an alternative search engine (such as DuckDuckGo instead of Google) or an alternative email provider (such as ProtonMail).

  What’s coming next for Matomo and Privacy ?

  Here at Matomo, we are building the leading decentralised open web analytics platform. We’re currently working on new sets of privacy features to make compliance with GDPR a breeze. Stay tuned here to be notified when we launch the new privacy compliance tools !

  And in case you’ve missed this important info, you may be interested in :

  • Configure Privacy Settings in Matomo
  • 11 ways Matomo Analytics helps you to protect your visitors privacy

   

  The post It’s January 28th : Let’s celebrate Data Privacy ! appeared first on Analytics Platform - Matomo.