Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Timecode pass through

  • Timecode pass through

    Posted by Matt Schulze on February 21, 2007 at 6:27 pm

    I am trying to clone a tape and preserve the existing timecode.
    Since I only have one Sony DSR-25 deck,(two would make this simple) I have to import the original into Final Cut and then output back to tape. My problem is, that the deck will always start timecode at 0:00:00:00 and not read the timecode on the original.
    The deck is connected through firewire.
    I’ve been up and down both the Sony manuals and the Final Cut manuals, tried different settings on the deck, but can’t make it work.
    In the computer the timecode of the original tape is preserved and I can set the sequence to start at those mumbers, but upon output they’re lost.
    Any ideas? Does it have to do with firewire? Do I need RS 422 protocol?
    Thanks

    Matt Schulze replied 19 years, 2 months ago 4 Members · 7 Replies
  • 7 Replies
  • Colin Mcquillan

    February 21, 2007 at 6:41 pm

    You need to stripe your 2nd tape with enough timecode for pre-roll.. then edit to tape the sequence..

    I use DSR-40’s, DSR-80’s, and DSR 1500a’s. on each you can set the crash record timecode to what ever you want. perhaps you cant on your DSR 25!?

    If you can.. go into the menu on the deck, set your timecode to start at the TC you want, then do a crash record. (hit record and play on the deck) let it lay down a good 30 seconds of timecode. then go into final cut and edit-to-tape your sequence setting the in point to match that of your original timecode..

    If your deck wont allow you to stripe your tape with user set timecode, then throw your second tape into your camera and do it there… just about every camera will let you set the starting timecode.

    uhm… well….

  • Colin Mcquillan

    February 21, 2007 at 6:48 pm

    ** be sure when draging your sequence into the edit-to-tape window you drop it on the “assemble” option

    uhm… well….

  • Jim

    February 21, 2007 at 6:58 pm

    I’ve done this deck to deck, but I believe you could do the same thing from camera to deck.

    There is a function on the 25 called Duplication Plus (button under the audio dials). If you hook up a FW between you camera & the deck and press the stop button on both machines, then press the duplication plus button it should rewind the tapes and create a clone of your source tape.

    As I mentioned, I’ve only done this deck to deck, but my guess is it should also work with a camera.

    Let me know how it works out.

    Good Luck

  • Paul Dickin

    February 21, 2007 at 7:10 pm

    Hi
    The DSR-25 has the External Timecode setting in its menus. Set it to extenal, and it will read FCP’s Edit To Tape timecode.
    For a fuller explanation, Shane Ross has written a full explanation for a DSR-11, which is functionally very similat to the DSR-25.
    https://proapptips.com/tips/article.php?story=2005092107133358

  • Matt Schulze

    February 21, 2007 at 10:46 pm

    Thanks for all the input.
    Setting the deck to external didn’t work, that was one of the things I’ve tried,
    but then I’ve used “print to video”. So I’ll try it with “edit to tape” and will report back.
    Using the “dup” button didn’t work either, since the computer does not behave like a deck. If “edit to tape” won’t work I’ll try the camera route.

  • Paul Dickin

    February 21, 2007 at 11:01 pm

    Hi
    Sorry my previous post was confusing 🙁
    Shane’s procedures are correct.
    FCP won’t send out timecode (well FCP 3 did, but not since then), but you can lay down some start timecode on the tape (with deck switched to External Timecode) using SimpleVideoOut.
    Then reset the deck to Internal Timecode, and Edit To Tape your movie, using Assemble Edit mode.
    Cheers

  • Matt Schulze

    February 22, 2007 at 2:28 am

    Cool,
    I will try that

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy