-
Locating timecode break error – timecode is fine
When digitizing, FCP experiences a “locating time code break” error every 3-5 seconds. This causes it to stop digitizing and begin to search the tape for the break. It’s impossible to digitize video of any considerable length. This has been going on for a while intermittently, and my workaround has been to digitize on another machine and transfer to my main editing system via external drive.
The fact that FCE captures the footage with no problem leads me to believe that there’s not an issue with the time code or the playback device (in fact, the problem still occurs with a camera used for playback). I’ve searched the forums, deleted preferences, tried different firewire ports and different capture settings, all to no avail. Choosing “non controllable device” to bypass timecode results in unsyched a/v. FYI – The external drive I’ve been using to transfer files is firewire and I have had no issues with connectivity when using it.
MacPro 3.0GHz 8 Core – 12GB RAM
ATI Radeon HD 4870; FCS3; AE; CS4 -
6 Replies
-
I take it this is Firewire based machine control?
You haven’t specified what VTR models, formats, and settings you have tried.
If its Firewire, do you have other Firewire devices attached? Which ones?
-
Sorry for not giving all the info, but I’ve been doing this for so long I know what the problem is not, and it’s not the deck, it’s not the settings. But here goes:
Format: SD 16:9
Deck = JVC HR-DVS2. Old school miniDV/SVHS.
Alternative capture devices: Sony HC-9; Sony V1U.
Capture settings: Firewire NTSC basic/DV NTSC 48kHz (anamorphic). Have tried NTSC and NDF to no avail.
No other firewire devices attached to system (unless transferring from said external drive).
OSX: 10.6.7
FCP: 7.0.3It’s especially frustrating when you’ve been using the same set up for years and for whatever
MacPro 3.0GHz 8 Core – 12GB RAM
ATI Radeon HD 4870; FCS3; AE; CS4 -
I’ve had the “Timecode Break” error come up in situations where there was an issue with the Capture Scratch RAID. The drive was losing speed constantly during the transfer until the drive’s throughput was lower than the captured video’s. What really should have come up as a dropped frame error was seen as a timecode break by FCP, which started up the infinite VTR crawl. That could be a thing to cross off the possible causes list. Running some kind of diskwhack test like AJA’s would quickly tell you if that’s your case. After I fixed the HDD issue, I never saw the error again.
IHTH,
JC Boulay
Technical Director
Audio Z
Montreal, Canada
http://www.audioz.com -
The hard drive speed thing sounds very plausible. I will check into it.
MacPro 3.0GHz 8 Core – 12GB RAM
ATI Radeon HD 4870; FCS3; AE; CS4 -
Thanks again to the COW the problem is solved. It was indeed a hard drive speed issue. Now to figure out what’s up with the drive – or better yet get a new one on the way.
Thank you Jean, for pointing me in the right direction and hopefully helping anyone else with the same issue.MacPro 3.0GHz 8 Core – 12GB RAM
ATI Radeon HD 4870; FCS3; AE; CS4 -
Problem WAS the hard drive – used xbench to determine the issue. Switched capture to another drive and captured with no errors.
Ordered a new drive from OWC, installed and all is back to normal.
Thanks for all your help!MacPro 3.0GHz 8 Core – 12GB RAM
ATI Radeon HD 4870; FCS3; AE; CS4
Reply to this Discussion! Login or Sign Up