Skip to main content
This topic has been closed for replies.

28 replies

Show previous replies
R
renecaron
Participant
January 24, 2023
Problem still there in 13.1.2. Definitely related to GPU acceleration. Using GPU acceleration (OpenCL or Metal) breaks the timecode. Software only is a the only workaround at a huge rendering speed expense. Guys fix this ASAP please! Unworkable in my situation cannot use this release as it is right now.
F
FeedbackCommunityMemberAuthor
Inspiring
January 24, 2023
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!

System Details:
Premiere Pro CC 2019 (v. 13.1.2 Build 9)
iMac 5k Late 2014
4 GHz Intel Core i7
AMD Radeon R9 M295X 4GB
F
FeedbackCommunityMemberAuthor
Inspiring
January 24, 2023
Timecode overlay display error in 24P when NVIDIA GPU mode.
If change to software mode, Timecode overlay will be correct.
A
adabis168
Participant
January 24, 2023
come on adobe. you need to take this major flaw in your software seriously. people can't turnover their films with this bug. where are you?
    F
    FeedbackCommunityMemberAuthor
    Inspiring
    January 24, 2023
    If possible please verify if this is the same issue that you may be facing.

    https://forums.adobe.com/thread/2611600
    F
    FeedbackCommunityMemberAuthor
    Inspiring
    January 24, 2023
    I can back this up, the bug is still present in v13.1. I have a sequence in 24 fps. All material is also 24 fps. In the export window, if I select the output also as 24 fps, and use the 'timecode overlay' option, I get the following results.

    Choosing 'generate timecode' and '24fps' yields completely wild results. The starting time is not the same as displayed on the seqeunce itself. If i correct it with offset, it will not stay in time, in fact it does double frames, so the timecode does not change between two frames at various points.

    If i select 'generate timecode' and 25 fps, the starting time is completely off, but I can again correct this with offset. This time, it stays correct from beginning to end.

    So 24 fps is completely useless, and for some reason, for 24 fps sequence / material, you have to choose to generate 25 fps timecode and offset it if you want results.
    R
    renecaron
    Participant
    January 24, 2023
    This bug has once again reappeared in Premiere v13. It makes this release totaly useless for us. Ex.: a 24fps timecode effect generator @ 10:00:00:00 in a 24fps timeline will display 09:59:22:00 and double or skip frames from time to time. So frustrating and unacceptable!
    F
    FeedbackCommunityMemberAuthor
    Inspiring
    January 24, 2023
    Agreed, seems to be an ongoing issue through the years.

    This is not an issue of interpreting the TC of imported footage; I can add an Adjustment layer/Transparent video to an empty timeline, add the TC generator to it, and the burn-in will not correspond with the TC displayed in the timeline panel. In my case it's exclusive to a 30fps sequence/30fps TC generator.

    Current workaround is to swap everything to 29.97-- and presto the TC generator will correspond properly to the sequence TC.
    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices