Harry Miller

My feedback

  1. 28 votes
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    22 comments  ·  Premiere Pro » Editing  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Harry Miller commented  · 

    Here is the work around: switch the Mercury Playback Engine to Software Only. In Premiere you go to File\Project Settings\General. In Media Encoder you go to Preferences\General\Video Rendering. That is only for exporting media. This give accurate sequence and clip timecode burn ins.

    An error occurred while saving the comment
    Harry Miller commented  · 

    Premiere Pro 13.1.2 (build 9), and Media Encoder 13.1 (Build 173). I'm hoping my frame grabs will upload to show that outputting a sequence (1920x1080, 24 fps, ProRes 422 HQ media) to Media Encoder (by selecting Queue), adding a Timecode display effect, the timecode displayed is WRONG.
    1) The sequence starts at 00:59:40.00. This frame shows the burnin at 00:59:36.10. 2) Adding a frame offset of 86 frames to start the sequence at 00:59:40.00, the last frame of picture the timecode is way off (54 frames). 3) Changing the timeline frame rate to 25 (and no 86 frame adjustment), the start timecodes match. 4) The last frame of picture the timecode is 1 frame off from the burnin (the burnin is wrong).

    Timecode doesn't work correctly as an adjustment layer, displaying incorrect timecode for the sequence AND the clip, and Media Encoder doesn't at all display the correct timecode.

    Very serious items to fix.

  2. 8 votes
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Premiere Pro » General  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Harry Miller commented  · 

    I have the same problem. I add an adjustment layer over the entire timeline, and set the timecode to display the source clip. But it is inaccurate, so not usable.

    Harry Miller supported this idea  · 

Feedback and Knowledge Base