Not sure if this is the case in YOUR case John, but something similar happened to me with a SPANNED file-based clip.
Somehow on the other side of the span, Avid lost the timecode values similar to what you're describing. Took FOREVER to figure that one out.
Since we're all seeing more and more file-based stuff, I thought I'd point it out as a possibility.
Actually, now that I think about it, instead of a spanned FILEBASED clip, it might have been an instance where AVID actually "spanned" a long clip because the capture from tape went over the 4gig limit. When it went to the new "span" of the clip, the clip timecode appeared OK, but multi-cam collapse lost any timecodes after the first "span" of the captured clip. If the clip you're talking about was really long, see if there are multiple MXFs or OMFs associated with the same clip.
Steve Hullfish
contributor: www.provideocoalition.com
author: "The Art and Technique of Digital Color Correction"
On Jun 9, 2011, at 1:29 AM, John Moore wrote:
> I've been using commit multi cam for years without issue. Today for some reason commit multicam actually changed a shot and it's timecode. Very weird a shot went into a clip of the same shot with a motion effect, not a time warp. The outgoing shot was supposed to continue just with the motion effect. Using commit multi cam changed the clips timecode. I went back to the original sequence and cut in just the motion effected clip without using commit multicam and the time code was correct but it wouldn't relink no matter what I did.
[Non-text portions of this message have been removed]
If you want to donate to Red Cross quake relief, you can do so through your cell phone. Text redcross to 90999 to make a $10 donation. It will be on your next cell bill.
No comments:
Post a Comment