Restarting Timecode at New Scene

Hello All,

Wondering if there is a way to make nested/visible timecode restart at each new scene strictly for export? Would prefer if it didn't involve nesting and putting each new scene in a duplicate sequence and exporting individually. Also prefer if it didn't involve changing the timecode for the entire sequence (as this would really mess us up).

Is there a plug-in for this? Perhaps that involves markers?

We have a client preferring a quicktime of the entire episode but with individually numbered scenes that have their own timecodes (please don't ask why - it's just one of "those".

Thanks for any and all suggestions!
-Travis-

> Wondering if there is a way to make nested/visible timecode restart at each new scene strictly
> for export? Would prefer if it didn't involve nesting and putting each new scene in a duplicate
> sequence and exporting individually. Also prefer if it didn't involve changing the timecode for the
> entire sequence (as this would really mess us up).

You could use Timecode Generator instead of Timecode Reader. Use the "blank text object" approach and you can modify that object's timecode to your heart's content while leaving your sequence and clip timecodes alone. Just check random spots throughout the timeline and make sure the burned timecode matches your timeline.


www.derekmok.com

Derek's method is actually better than nesting because timecode will drop out over any voids in the nest.

Could plain old slug be used as well?

- Loren
Today's FCP keytip:

Copy a clip, Paste Overwrite with Command-V, but
Paste Insert with Shift- V !

Final Cut Studio 2 KeyGuide? Power Pack.
Now available at KeyGuide Central.
www.neotrondesign.com

I think why Derek mentioned using a blank text object is because it comes with an embedded alpha channel. With a slug, you still need to crop the slug.

I would actually advise sending out different QT movies and getting QTsync to generate a timecode instead, as that is much much faster than rendering timecode in FCP. But that is also provided you are not editing off HDV or XDCAM.



www.strypesinpost.com

> I would actually advise sending out different QT movies and getting QTsync to generate a
> timecode instead

In this case, if they're using different timeline timecode (one which picks up from where the previous scene left off) they might have issues finding out what part of an edit the client's talking about?


www.derekmok.com

Yea... But it's gonna be pretty confusing anyway- John at the diner, timecode 01:25, and you have 3 diner scenes and all of them start from 0:00..

Getting them into different sequences will be much faster on the rendering time (as long as you know which sequence the client is refering to), having a burnt in timecode layer (either slug or blank text object), can also do.



www.strypesinpost.com

True, but that's another reason to do a proper burn-in. You can label the scenes on top of the multiple zero timecodes.

Would've been even better if the client could've been convinced to stick with, uh, real timecode burns.


www.derekmok.com