At that time there was not much interest in precisely synchronizing media in the same tab or across devices.īut today features like Apple's SharePlay or BBC's Together are well known and heavily used. The work on the spec started over 7 years ago.
The Timing Object specification is a W3C draft proposed by the Multi-Device Timing Community Group.
There may even be a few FFmpeg demos to help jumpstart the revolution.ĭid you know that there is a standard to synchronize time sensitive media across devices? It's a draft. In my Demuxed talk I will dive into the history of video framerates, explain how technical design choices made by people in lab coats 70 years ago still haunt us even in the digital age - and then explain why we, the greatest streaming nerds who ever attended a Demuxed conference, have a golden opportunity to lead the entire video industry into the 21st century by embracing integer framerates and saying goodbye to unnecessarily dividing perfectly nice whole numbers with 1.001. So why do we go through all this trouble? Where did these strange framerates come from in the first place? Why did they prevail against saner framerates like 24, 30 and 60? Million lines of code have been written by video engineers over the past decades to handle these framerates and the challenges that inevitably arise when trying to count whole frames as fractional values.
Nearly all of us working in video tech have encountered these oddly specific numbers more than once in our careers and can instantly recognize them as the digital video framerates most commonly used in North America (and a few other parts of the world). If this cannot be done theoretically, can you provide me with some reliable links which can succeed installing gstreamer with omxh265dec or nvdec support on Windows 10? Thank you for your help and looking forward to your early reply.It's Time We Said Goodbye To Fractional FrameratesĢ3.976, 29.97, 59.94. So the question comes: If I set the timestamp in appsrc with gstreamer, how can I get the timestamp with ffmpeg(it seems ffmpeg has no GstBuffer struct)? Because of the failness, I have to handle the H265 data with ffmpeg at client. Of course,if I get success,I can use appsink to abtain the timestamp which was set in appsrc. However, I tried my best to install gstreamer with nvdec or omxh265dec support on Windows 10,but all failed. But the situation is a bit of diffrent.Īt server,I indeed use the appsrc to push outer YUV data into pipeline,and I can set the timestamp using GST_BUFFER_PTS.īut at the client, we need to choose Windows 10 as client and we need to use Hardware Acceleration to decode(we can use omxh265dec or nvdec). Thanks for your reply,and the method you provided is just what I’m looking for.
0 kommentar(er)
