[BRussell] “darn it — FCP handles this easily, you just tell it to ignore breaks. Yes, there can be sync issues, but who cares when the breaks are at the end of clips. I wish there was some way to force the Adrenaline to keep the material. Oh well, there goes all my logging. Stewing…”
Well in all fairness, this isn’t totally accurate either. Most NLEs (maybe all) don’t actually record the TC signal. They grab the first frame and make comparisons from which they generate interpolated code. If the in and out TC matches, then the interpolation is accurate. If you choose to let FCP ignore TC, the warning indicates that batch captures will be wrong. For example, if you have 5 TC breaks in a clip and you tell FCP to ignore the TC breaks, all portions of that clip after the first break will have the wrong TC. If you are working offline/online this is disasterous, because you cannot consolidate and batch capture accurately.
On the plus side, Avid does a far better job of pre-rolling across TC breaks (FCP won’t) and automatically breaking clips into new segments at TC breaks. Have you tried the latter approach? I don’t remember if this works with batch capture/digitize, but maybe it does now.
Unfortunately you are encountering a known issue with Sony camcorder recordings.
Sincerely,
Oliver
Oliver Peters
Post-Production & Interactive Media
Orlando, FL
http://www.oliverpeters.com