• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
0

TRT in export is ~4 seconds longer than in the Timeline

Community Beginner ,
Jun 14, 2024 Jun 14, 2024

Copy link to clipboard

Copied

Hi all,

 

I'm running into a weird export issue that has me stumped. I'm working with 29.97 progressive scan footage, my timeline has a timebase of 29.97 and a display format of 29.97 non-drop frame TC. The issue is that when I export I get a QT file that is roughly 4 seconds longer than the timeline. Sequence settings are below:

 

Screenshot 2024-06-14 at 5.07.20 PM.png

 

Export settings are:

 

Screenshot 2024-06-14 at 5.10.13 PM.png

 

 Everything looks kosher to me, but when I export I get a QT file that looks like this at the final frame: 

 

Screenshot 2024-06-14 at 5.12.35 PM.png

 

 Here's the inspector info:

 

Screenshot 2024-06-14 at 5.12.47 PM.png

Any ideas for what is causing this drift? I feel like it's gotta be a frame rate issue, but I'm just not seeing what the problem is.

 

-Mark

TOPICS
Editing , Export

Views

149

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Jun 14, 2024 Jun 14, 2024

Copy link to clipboard

Copied

It appears that Quicktime is interpreting the timecode format as Drop-Frame instead of Non-Drop-Frame, and this is causing it to count the frames incorrectly. I ran a test on VLC, and it is doing the same thing.

However, when I imported the file back into Premiere, the timecode was correct. You can verify this in the file metadata. In the Metadata panel, under the File heading, go to Start Timecode > Time Format, and you should see that it is Non-Drop-Frame.

So, it might be an issue with Quicktime Player and VLC, or perhaps the file is missing some metadata that tells these apps to distinguish between Drop and Non-Drop formats.

Cheers,
Paul

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Jun 15, 2024 Jun 15, 2024

Copy link to clipboard

Copied

Huh, yeah that would explain it. Thanks for the response, Paul.

 

I guess the only problem is that even if I now know what the issue is, it's still an issue. If I have to deliver to network and they just see that the file is 5 seconds longer than it should be, I doubt the missing metadata/misreading frame rate explanation will fly.

 

Premiere Adobe guys, please please look into this!  

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Contributor ,
Jun 15, 2024 Jun 15, 2024

Copy link to clipboard

Copied

Drop-Frame is real time, Non-Drop is a way of counting frames that makes the arithmetic easier without using a calculator.  Networks by and large use real time (as do Quicktime Player and VLC by default), and that is how they will ingest and interpret it.  Your file probably is, sorry to say, 5 seconds too long.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Jun 15, 2024 Jun 15, 2024

Copy link to clipboard

Copied

if you check you source footage in Media Info,

is there any possibility of VFR? (Variable Frame Rate)

If yes, use Handbrake to change your source footage to CBR (Constant Frame Rate),

then import back the CBR footage to Premiere Pro.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Jun 16, 2024 Jun 16, 2024

Copy link to clipboard

Copied

@Carlos Ziadethanks for the suggestion. I have over 4.5 TB of 1080 footage, so there's a lot. But everything that we shot is CBR. No one was using an iPhone or anything like that.

 

That said, there is a healthy amount of archival from all kinds of sources that also lives in the timeline. That stuff is not uniform. But, that describes almost all the projects I work on.  I've never run into this.

 

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Jun 16, 2024 Jun 16, 2024

Copy link to clipboard

Copied

LATEST

Also, all that archival has been transcoded to Pro Res 422 Proxy.  I also proxied all the footage we shot as well. Maybe something weird is happening because of the proxies. 

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines