Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy 9 hrs of bad TC from DSR300. Any ideas?

  • 9 hrs of bad TC from DSR300. Any ideas?

    Posted by Phillip Powell on February 12, 2006 at 12:19 am

    Posted this as well on the SonyDV board.

    9 hrs shot with a fairly new, low hrs DSR300. Go to digg, & FCP stops with warning saying ‘time code break’. And refuses
    to work in ‘capture now’ mode as well. Image is fine, nothing visable wrong. Spot checked all thru the 9 hrs of the shoot,
    same thing. Camera was in NDF mode, shooting brand new Sony Brand tapes. Camera was one of 3 in a 3-Camera shoot
    gen locked and recording common TC. I know the set up’s not a problem, as we swapped out another camera & all is fine.

    I’ve tried to capture from 4 different DVCam decks/cameras. Same thing. TC on camera LCD, and read by FCP shows
    continuous, incrementally rising TC, just the way it should. No apparent abnormalities.

    While checking this, the only strange thing I’ve noticed is there are colons between hrs & minutes, and between minutes
    & seconds, (as it should be for NDF) but semi colon between seconds & frames.

    Any body come across this before? is my question.

    Meantime, gonna see if dubbing/cloning can preserve TC which is most important and get things going.

    Thanks for any help.

    p2

    Jerry Alto replied 20 years, 3 months ago 3 Members · 2 Replies
  • 2 Replies
  • Ben Insler

    February 12, 2006 at 12:48 am

    If you’re going to be synching the clips together in FCP for a multicam edit, I’m not sure if this will work for you, but go to your User Preferences in FCP and make sure that under the “On Timecode break:” settings is set to “Warn After Capture.” This will force FCP to capture clips that it finds to contain TC breaks, even in capture now, and will instead warn you at the end of your capture session which cilps had TC breaks – but at least they will get captured. I’m still using 4.5 HD so I haven’t had the fun of synching multicam shoots into a multiclip and don’t know if this will cause you problems there, but I run into this caputre problem with the DVX-100A all the time and once captured the footage edits fine. If you’re capturing a lot of brief clips, however, FCP will still detect TC breaks as it seeks for your media In preroll and out postroll points, and will get hung up on clips that have their pre/post-roll in and out points set within a break region (look carefully, there may be a TC break of three frames that we’d never see as the TC files by, but that FCP doesn’t like – I don’t know why this would EVER happen, but it seems to a lot). So, you might have to change your capture preset, or make a few different ones and run a few captures to grab the clips that failed.

    I feel your pain though… Good luck.

    Ben Insler
    Editor
    Telemark Films

  • Jerry Alto

    February 12, 2006 at 5:15 am

    P2- This issue harkens back to my betacam days when the camera was not set to record TC in auto (both VITC AND LTC). Kind of a long shot but it might have been the problem. If the code was jam synched I would think that one of the codes is correct and there may be a switch on the playback deck to set to the code that is correct. Betacam had a switch that could can be positioned in VITC, LTC or Auto. Or you may have to insert edit the correct code if its worth the time and effort.
    Jerry

    G5 Dual 3GB Ram
    FCP5 Studio
    External 1 TB SATA Raid 0
    Kona LH, Second system w AJA ioLA
    Sony Z-1

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