[xavier pilsudksi] “The capture process keeps aborting due to “Timecode breaks”
However, after a close look at the footage, there are NO TC breaks. “
if it is not a camera original tape- the VItc and Ltc may not match causing this alarm.
IF it is a camera tape- the start /stop/ record/ pause / preview functions can trigger time code breaks if the camera has not been setup properly.
“However I’ve noticed that FCP detects some long frames that seem to always be the first frame of the clip. Could that be the issue? And if yes, how do you fix Long Frame issues?”
FCP has had a nasty habit of leaving a “long” or ‘Dupe” frame traditionally the 2nd & 3rd frames of at the head of each SDI / HDSDI capture for a very long time- I first saw it in FCPv2.02 – you cannot fix these easily – and why would if you are adding proper handles to your captures to avoid these ( and have plenty of head room for efx and transitions)
My guess is there is something else in your system that is causing it to “burp”
is the REF set to Video in?
is the HDcam footage 25p or 50i?
“I moved the deck to another system with the same settings and the capture goes well.
I’ve deleted the preferences, repaired the disk permissions, used the internal HD as the scratch disk, but nothing changed. “
then there is something on the setup in your machine. OS / QT/ Other apps that are causing the error.
gary adcock
Studio37
HD & Film Consultation
Post and Production Workflows
Inside look at the IoHD