Welcome to our community

Be a part of something great, join today!

Log in
  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

Premiere Pro CS5 and timecode

K

kupchenpo

Banned
Joined
Sep 15, 2008
Messages
29
Reaction score
0
Points
0
Age
44
Hi,
If I open a .R3D clip in the source monitor, its timecode entry is two frames late. For example, if the absolute timecode of the clip is 19:43:15:16, the source monitor will display 19:43:15:18 (i haven't experimented with edgecode). It's messing up my EDLs

Anyone know why?
Thanks.
 
kupchenpo said:
Hi,
If I open a .R3D clip in the source monitor, its timecode entry is two frames late. For example, if the absolute timecode of the clip is 19:43:15:16, the source monitor will display 19:43:15:18 (i haven't experimented with edgecode). It's messing up my EDLs

Anyone know why?
Thanks.
Click to expand...

We don't have any bug open on this... I would love a sample file.

Cheers

Dave
 
  • Thread starter
  • Banned
  • #3
Hi Dave,
Thanks for your reply. I can send an .R3D if that's what you mean? I'm getting this weirdness consistently, with different files, different projects, different sequences. I posted this photo over at creativecow:
1.png
 
kupchenpo said:
Hi Dave,
Thanks for your reply. I can send an .R3D if that's what you mean? I'm getting this weirdness consistently, with different files, different projects, different sequences. I posted this photo over at creativecow:
1.png
Click to expand...

I see what you mean now... Will get back to you

Cheers

Dave
 
Wow... never noticed
 
Hi Kupchenpo,

Your issue here seems to be the drop-nondrop setting, and not specific to red format, and it is not a bug.

Drop-frame timecode is conventionally indicated by separating the time units with semicolons, whereas non drop is indicated by colons. Notice the properties shows : (colons), and the timeline shows ; (semicolons). This is the source of your issue. You should be able to look at the Premiere help to disable drop frame display. After Effects has a pretty good help file about this.

http://help.adobe.com/en_US/afteref...ml#WSca6f2c662eed6cbf340769891233f0aa1fd-8000

http://help.adobe.com/en_US/premierepro/cs/using/WS1c9bc5c2e465a58a91cf0b1038518aef7-7f81a.html

Here is some good info about timecode, and the reasons behind drop/non-drop if you're interested.
http://en.wikipedia.org/wiki/SMPTE_time_code#Drop_frame_timecode

Hope this helps.

Amir
Adobe After Effects Engineering
 
Last edited:
  • Thread starter
  • Banned
  • #7
Hi Amir,
Thanks for trying to help.

For Everyone, here's NDF:

2.png



Am I missing something obvious?
 
Hi Kupchenpo,

To answer your question, no, this stuff is not obvious.

I agree something looks amiss here. But I wouldn't necessary rule it out as a bug. I know from being confused by this myself on multiple occasions that there is a lot of subtlety about how the TC gets interpreted, especially when reinterpreting the footage. Dave's group is looking at it currently. I assume you can reproduce this in After Effects as well? If so we'd like to take a look.

Amir
 
  • Thread starter
  • Banned
  • #9
Hi Amir,
Here's the best I could do out of After Effects. Everything seems ok?

3.png
 
If you select the file in the project window, go to window, Metadata, then open up Files->Dynamic Media what does it say under Start Timecode, Alternate Timecode for both Time Value and Time Format?
 
Developments

Developments

Ok, it turns out that Premiere Pro isn't consistently misreading the R3D absolute start timecode by two frames. Sometimes PPRo is off by one or three frames...and sometimes its not off at all- it displays the correct timecode.:confused5:
This means things are much worse than I originally thought. It's not possible to correct an exported EDL by scripting, since the variance isn't constant or predictable.

Dave: any news about a fix?
 
Last edited:
Here's a sample from some R3D files:

chart3.png
 
Last edited:
kupchenpo said:
Ok, it turns out that Premiere Pro isn't consistently misreading the R3D absolute start timecode by two frames. Sometimes PPRo is off by one or three frames...and sometimes its not off at all- it displays the correct timecode.:confused5:
This means things are much worse than I originally thought. It's not possible to correct an exported EDL by scripting, since the variance isn't constant or predictable.

Dave: any news about a fix?
Click to expand...

All you guys having problems.. Can you narrow down the files with problems and without problems to a specific red camera firmware?

Cheers

Dave
 
All of my recent R3Ds are 4.5k 29.97 on 30.5.0#03 cameras (3 different MX Red Ones)

I tried ONE ancient 4k 29.97 from a 3.2.5#16, and the timecode was correct... Should I try some more files?
 
kupchenpo said:
Hi,
If I open a .R3D clip in the source monitor, its timecode entry is two frames late. For example, if the absolute timecode of the clip is 19:43:15:16, the source monitor will display 19:43:15:18 (i haven't experimented with edgecode). It's messing up my EDLs

Anyone know why?
Thanks.
Click to expand...

I know why! Thanks for the bug report. You should find that you will see this bug with r3d files that have audio and won't see the bug when you don't have audio. The problem is we were putting the timecode in the audio framerate... yucky on our side, sorry about that. We have a fix in house, not sure when it will reach you guys.

Cheers

Dave
 
David McGavran said:
I know why! Thanks for the bug report. You should find that you will see this bug with r3d files that have audio and won't see the bug when you don't have audio. The problem is we were putting the timecode in the audio framerate... yucky on our side, sorry about that. We have a fix in house, not sure when it will reach you guys.

Cheers

Dave
Click to expand...

Has this been fixed yet? It's a showstopper for us adopting CS5, which I really want to do.

Our FCP editor is loving CS5, we'd save hundreds of hours not transcoding an entire feature's worth of rushes, but this timecode this is HUUUUGE.

I'm on 5.02 and still having this problem.

thanks,


JT
 
John Tissavary said:
Has this been fixed yet? It's a showstopper for us adopting CS5, which I really want to do.

Our FCP editor is loving CS5, we'd save hundreds of hours not transcoding an entire feature's worth of rushes, but this timecode this is HUUUUGE.

I'm on 5.02 and still having this problem.

thanks,


JT
Click to expand...

We can't easily role out this fix do to entanglement with other code. The problem is only there when there is audio in the R3D. It will be fixed in our next bigger style release. Sorry about this...

Cheers

Dave
 
I had a similar problem. I right clicked on the r3d file and clicked interpret footage, and changed the frame rate to 24... It fixed my main issues. Not sure?

EDIT: I just started a new sequence in premiere with the frame rate of 24fps, it seemed to fix the issue.
 
Last edited:
You must log in or register to reply here.
Back
Top