An error occurred while saving the commentTeagan L commented
This is a serious issue affecting my workflow on multiple projects now, only began happening after updating to CC 2019. Up to at Least version 12 this was not occuring in CC 2018 for me.
If I have a 24fps Timeline and apply 24fps "Generate" Timecode to a 24fps Transparent Video Track. I get completely wrong timecode read out:
1. It sometimes starts at about 00:59:56:09
2. It drifts significantly over the course of just 20 minutes of video.
By the end of a 20 minute rush you are looking at 1 second+ of drift, and the amount of drift increases, it is not a static offset. This seems to be some kind of mathematical error, and it may be in the coding for the Mercury OpenCL acceleration engine for this effect. Using Mercury, the timecode effect is incorrect. Using Software-Only, the timecode effect renders correctly based on its settings.
Only solutions at the moment are:
1. Stay on OpenCL and change the Time Display to "25fps" in the effect, which for some reason makes the timecode run at 24fps correctly and match...
2. Switch to Software only for rendering out, which makes the correct settings generate properly, which still doesn't solve the problem of then conforming things while actually editing.
Please fix this as it is a huge problem!
Premiere Pro CC 2019 (v. 13.1.2 Build 9)
iMac 5k Late 2014
4 GHz Intel Core i7
AMD Radeon R9 M295X 4GB