Yes, that is what I thought but when the source is drop-frame and the destination is drop-frame, it appears that ffmpeg is calculating some offset into it that is throwing it off. It should remain the same in this scenario.
- Sean -----Original Message----- From: ffmpeg-user [mailto:ffmpeg-user-boun...@ffmpeg.org] On Behalf Of Wayne Poll Sent: Sunday, May 15, 2016 7:25 PM To: FFmpeg user questions Subject: Re: [FFmpeg-user] 60 FPS timecode problem -----Original Message----- >But there is an oddity with the time code where it adds 1.8 seconds at the >start of the newly transcoded file for every hour on the initial time code. Sounds like a Drop Frame - Non-Drop Frame issue to me. I'm pretty sure the difference between DF and NDF is about 2 seconds per hour. _______________________________________________ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe". _______________________________________________ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe". _______________________________________________ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
