On Fri, Jan 23, 2015 at 06:44:56AM -0800, jon wrote: > Hi Michael, > > That is great! > > I see what you are referring to in mov_read_timecode_track(). However the > text of that comment seems contradictory to me based on what I have read in > the QuickTime reference I sited about the tmcd counter flag. > > It seemed like prior to the patch I submitted mov_parse_stsd_data() was > collecting the st->codec->time_base as if the counter flag was unset. > > That comment text comes from commit: > > 35da85562d2f731855b28d4ab3b9b0679730ebf7 > > Perhaps Clément Bœsch has a better understanding of the difference between > timecode values when the counter flag is set and when it is not. My work was > based on deciphering the samples I had at my disposal in conjunction with my > interpretation of the reference pdf. >
From what I remember, all the samples I had were in "frame number format" even though the flag was not set. I haven't look at this stuff for a very long time though. [...] -- Clément B.
pgpG6B0E2elRv.pgp
Description: PGP signature
_______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
