Burnt In Timecode Issue

[lordpurton]

When setting up to output from REDCINE to a Quicktime I have found it useful to put as much information as possible on the screen using 'Burn-in' as security for the online conform.

However I've noticed that although the REDCINE display of the source t/c runs at 25fps the burnt in source t/c runs at 24fps. As you move along the clip in REDCINE the the BITC loses 1 frame each second so after 25 seconds the BITC is now 1 second out. Not that good as a reference!

Has anyone else found this. Is there a setting to set the source BITC to 25fps or is this a bug? I assume it only happens when working at 25fps PAL.

 

[Rob Lohman]

Are you sure you have selected source timecode for the burn in? Also make sure your project framerate is set up right. Are you using the latests REDCINE?

 

[lordpurton]

2 screen prints to illustrate

2 screen prints to illustrate

Frame rate is 25fps and source t/c is selected so hopefully ok.

I've attached 2 screen grabs to show the t/c drift(24-25fps). hopefully you can see on the bottom row of info runs at 25fps but the burnt in t/c above (and larger) is 24fps.


http://www.reduser.net/forum/attach...ment.php?attachmentid=2858&stc=1&d=1201601681

 

[Mark L. Pederson]

I hit this bug too - you need to chnage the frame rate of each shot - one at a time (oh JOY!) in the Library.

For some reason, even if the project is set up at the 25fps - it brings the clips (25fps) into the project as 24 fps. I reported this to Kevin and he re-created the bug and hopefully REDCINE team is on it -

 

[Brenton]

(Based on build 74)This grubby little bug only applies itself on the 'Load All' option, loading single clips keeps the correct fps. It's a toss up if changing the clips individually or loading them singly is a bigger pain in the a$$.

But then again, that's what assistants/interns are for

 

[Mark L. Pederson]

then again, that's what assistants/interns are for

it's a bug that needs to be squished. So many more exciting things for the interns to do -

 

[Brenton]

it's a bug that needs to be squished. So many more exciting things for the interns to do -

I concur, and sadly build 82 removes the loading single and is indeed loading 25fps as 24fps. Just tested