Hi Kieran, To answer your question, this change basically takes the first valid TC as a string and sticks it in the video’s avstream metadata dictionary where other muxers and encoders look. It does not make an independent timecode track/stream with samples per frame. That is why I called the patch “limited”. However there doesn’t seem to be many if any parts of ffmpeg that use dedicated timecode streams with individual samples. That is why it still seemed worth submitting my work back as we move on to other solutions.
I hope that still helps you in your case. I will stay the course to address Marton’s feedback and get this in there. Thanks, Jon > On May 25, 2018, at 8:59 AM, Kieran O Leary <kieran.o.le...@gmail.com> wrote: > > I'd love to see some documentation and to know how timecode is stored in > the output file. This looks like a really welcome development! > _______________________________________________ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org > http://ffmpeg.org/mailman/listinfo/ffmpeg-devel _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
