<div class="gmail_quote">2011/8/11 Sebastian Dröge <span dir="ltr"><<a href="mailto:sebastian.droege@collabora.co.uk">sebastian.droege@collabora.co.uk</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> <div class="im">On Wed, 2011-08-10 at 17:30 -0600, Cory Albright wrote:<br> > I am needing to export rendered frames from my application to an MXF<br> > video file. The application is rendering based on a GPS time-clock and<br> > I need to have the GPS time embedded into the frame headers of the MXF<br> > video. Does the MXF plugin for gstreamer support this?<br> <br> </div>Hi,<br> currently the MXF plugin does not support this but it should be possible<br> to add support for this. Based on which specification do you want to add<br> the GPS time into the frame headers?<br></blockquote><div><br>I would be interested in this as well, as I'll likely have a need to support this in the future. Do you want to save the GPS (UTC) date and time along with every frame (perhaps interpolated), just at the start (using relative offsets for each frame), or at the sampling rate of the GPS (typ. 1-10Hz)?<br> <br>Taking a quick look at the SMPTE metadata dictionary shows a lot of time-related keys, but I haven't worked with this before so I'm not sure which ones are appropriate. The SMPTE item for temporal keys is 07.02.00.00.00.00.00.00. My complete guess without reading any of the standards or RPs would be that you'd want to use: 07.02.01.02.01.01.00.00: Material Start True Date-Time, UTC, ("Absolute time at start of creating the segment, shot, clip, item etc."). Again, a complete guess, I'm not sure what's recommended or actually supported by software implementations.<br> <br>-Josh<br></div></div>