Ed Silvester
New Member
Hi, My name is Ed Silvester and I am video architect at StatsPerform; we work in Sports Data. I am working with a number of encoder vendors to propose a standard way to write "origin" time and date to live video. I have started a LinkedIn Group on this subject here.
The idea is that once we have data and time in the stream, we can start to synchronise sports data and use it to drive synchronised graphics - but it is much bigger than that; there's so much that could be done in post or in archive not to mention synchronising any live service that also references UTC. If you want to discuss ideas or find out more about the technical requirements please do drop in and say hi.
KLV is the building blocks of MXF and conforms to a SMPTE standard and is free to implement. I hope OBS add it!
SMPTE 336-2007 “Data Encoding Using Key-Length-Value”
STANAG 4609 “NATO Digital Motion Imagery Standard”
MISB ST-0601.17 “UAS Datalink Local Set”
The idea is that once we have data and time in the stream, we can start to synchronise sports data and use it to drive synchronised graphics - but it is much bigger than that; there's so much that could be done in post or in archive not to mention synchronising any live service that also references UTC. If you want to discuss ideas or find out more about the technical requirements please do drop in and say hi.
KLV is the building blocks of MXF and conforms to a SMPTE standard and is free to implement. I hope OBS add it!
SMPTE 336-2007 “Data Encoding Using Key-Length-Value”
STANAG 4609 “NATO Digital Motion Imagery Standard”
MISB ST-0601.17 “UAS Datalink Local Set”