Recherche avancée

Sur d’autres sites (15639)

• FFMPEG : Recurring onMetaData for RTMP ? [on hold]

  30 novembre 2017, par stevendesu

  For whatever reason this was put on hold as "too broad", although I felt I was quite specific. So I’ll try rephrasing here :

  My former understanding :

  The RTMP Protocol involves sending several parallel streams of data as a series of packets, with an ID correlating to which stream they are a part of. For instance :

  [VIDEO] <data>
  
  [AUDIO] <data>
  
  [VIDEO] <data>
  
  [VIDEO] <data>
  
  [SERVER] <metadata about="about" bandwidth="bandwidth">
  
  [VIDEO] <data>
  
  [AUDIO] <data>
  
  ...
  
  </data></data></metadata></data></data></data></data>

  Then on the player side these packets are split up into separate buffers based on type (all video data is concatenated, all audio data is concatenated, etc)

  One of the packet types is called onMetaData (ID : 0x12)

  An onMetaData packet includes a timestamp for when to trigger the metadata (this way it can be synchronized with the video) as well as the contents of the metadata (a text string)

  My setup :

  I’m using Red5Pro as my ingest server to take in an RTMP stream and then watch this stream via WebRTC. When an onMetaData packet is received by Red5, it sends out a JSON object to all subscribers of the stream over WebSockets with the contents of the stream.

  What I want :

  I want to take advantage of this onMetaData channel to embed the server’s system clock into a stream. This way anyone viewing the stream can determine when (according to the server) a stream was encoded and, if they synchronize their clock with the server, they can then compute the end-to-end latency of the stream. Due to Red5’s use of WebSockets to send metadata this isn’t a perfect solution (you may receive the metadata before or after you actually receive the video information), however I have some plans to work around this.

  In other words, I want my stream to look like this :

  [VIDEO] <data>
  
  [AUDIO] <data>
  
  [ONMETADATA] time: 2:05:77.382
  
  [VIDEO] <data>
  
  [VIDEO] <data>
  
  [SERVER] <metadata about="about" bandwidth="bandwidth">
  
  [VIDEO] <data>
  
  [ONMETADATA] time: 2:05:77.423
  
  [AUDIO] <data>
  
  ...
  
  </data></data></metadata></data></data></data></data>

  What I would like is to generate this stream (with the server’s current time periodically embedded into the onMetaData channel) using FFMPEG

  Simpler problem :

  FFMPEG offers a -metadata command-line parameter.

  In my experiments, using this parameter caused a single onMetaData event to be fired including things like "title", "author", etc. I could not inject additional onMetaData packets periodically as the stream progressed.

  Even if the metadata packets do not contain the system clock, if I could send any metadata packets periodically using FFMPEG then I could include something static like "the server’s clock at the time the broadcast started". I can then compare this to the current timestamp of the video and calculate the latency.

  My confusion :

  Continuing to look into this after creating my post, there are a couple things that I don’t fully understand or which don’t quite make sense to me. For one, if FFMPEG is only injecting a single onMetaData packet into the stream, then I would expect anyone joining the stream late to miss it. However when I join the stream 8 hours later I see Red5 send me the metadata packet complete with title, author, etc. So it’s almost like the metadata packet doesn’t have a timestamp associated with it but instead is just generic metadata about the video

  Furthermore, there’s something called "AMF" which I’m not familiar with, but it may be important ?

  Original Post

  I spent today playing around with methods to embed the system clock at time of encode into a stream, so that I could compare this value to the same system clock at time of decode to get a rough estimate of RTMP latency. Unfortunately the majority of techniques I used ended up failing.

  One thing I wanted to try next was taking advantage of RTMP’s onMetaData to send the current system clock periodically (maybe every 5 seconds) as part of the stream for any clients to listen for.

  Unfortunately FFMPEG’s -metadata option seems to only be for one-time metadata when the stream first loads. I can’t figure out how to add continuous (and generated) values to a stream.

  Is there a way to do this ?

• Catalyst Open Source Academy

  16 janvier 2015, par Matthieu Aubry — Community

  The Open Source Academy is an initiative designed to provide training and work experience for young New Zealand technologists. Catalyst organises the Academy to show young technologists how to participate in open source communities and to fully explore their passion for IT through freely available open source tools.

  It has been running annually since 2011. We are proud that Piwik project could participate in the Academy again this year !

  What students got done

  It’s amazing what a few young students can get done in four days of participating in an open source project like Piwik ! They were able to quickly get started with Piwik, and continued to make useful contributions to the Piwik analytics platform.

  New Darkness theme

  Liam has created a new dark theme for Piwik called Darkness.

  

  To create the theme, Liam had to improve Piwik core stylesheets and created this pull request : Reuse the LESS variable for white color across all stylesheets.

  Accessibility improvements

  We were lucky to spend time with Julius, a Catalyst employee who is blind. He showed us in great detail how difficult and time consuming it can be for a blind user to use Piwik. For example we noticed how complicated it was for Julius to navigate the menus, to get to the main content, and to use the calendar and the Website selector. During this presentation we also noticed that Piwik was not yet usable with the keyboard.

  As a result of this session with Julius we got to work with the students to improve accessibility in Piwik.

  

  (photo source)

  List of accessibility improvements

  All these pull requests were created by the students and have been successfully merged into Piwik :

  • see the focus of menu items when tabbing through the page
  • Tweaks to improve accessibility (section around graph, better tooltip, set language in html)
  • Added h3 tags to widget headers
  • when main Menu is focused, display submenu
  • Add “Skip to content” feature when user presses tab key
  • Improved accessibility by putting offscreen text in the widget title

  To learn more about accessibility in Piwik check out this issue on our tracker.

  Summary

  Working with young students was fun and interesting. We were excited to see how much they got done in such a short time !

  At Piwik and Piwik PRO we are committed to building the best open analytics platform, and we will continue to support students who want to take part in the Piwik adventure.

  Be well,

• Catalyst Open Source Academy

  16 janvier 2015, par Matthieu Aubry — Community

  The Open Source Academy is an initiative designed to provide training and work experience for young New Zealand technologists. Catalyst organises the Academy to show young technologists how to participate in open source communities and to fully explore their passion for IT through freely available open source tools.

  It has been running annually since 2011. We are proud that Piwik project could participate in the Academy again this year !

  What students got done

  It’s amazing what a few young students can get done in four days of participating in an open source project like Piwik ! They were able to quickly get started with Piwik, and continued to make useful contributions to the Piwik analytics platform.

  New Darkness theme

  Liam has created a new dark theme for Piwik called Darkness.

  

  To create the theme, Liam had to improve Piwik core stylesheets and created this pull request : Reuse the LESS variable for white color across all stylesheets.

  Accessibility improvements

  We were lucky to spend time with Julius, a Catalyst employee who is blind. He showed us in great detail how difficult and time consuming it can be for a blind user to use Piwik. For example we noticed how complicated it was for Julius to navigate the menus, to get to the main content, and to use the calendar and the Website selector. During this presentation we also noticed that Piwik was not yet usable with the keyboard.

  As a result of this session with Julius we got to work with the students to improve accessibility in Piwik.

  

  (photo source)

  List of accessibility improvements

  All these pull requests were created by the students and have been successfully merged into Piwik :

  • see the focus of menu items when tabbing through the page
  • Tweaks to improve accessibility (section around graph, better tooltip, set language in html)
  • Added h3 tags to widget headers
  • when main Menu is focused, display submenu
  • Add “Skip to content” feature when user presses tab key
  • Improved accessibility by putting offscreen text in the widget title

  To learn more about accessibility in Piwik check out this issue on our tracker.

  Summary

  Working with young students was fun and interesting. We were excited to see how much they got done in such a short time !

  At Piwik and Piwik PRO we are committed to building the best open analytics platform, and we will continue to support students who want to take part in the Piwik adventure.

  Be well,