It may not happen, then begin after FCP is re-launched. The problem is somewhat inconsistent and more likely to happen with 4k clips of at least 60 sec duration. The problem apparently began in 10.5.3 and exists in 10.6.1 on both x86 and Apple Silicon. The XML probably reflects internal problems in the project-level SQL database tables containing clip attributes. You can't match starting timecode and length and do an Edit/Replace to restore the damaged timeline clip range.Ī before/after diff comparison of the project XML indicates FCP has lost track of the retimed clip duration and starting timecode. "Reveal in Browser" SHIFT+F on the black timeline clip will not find the source clip, and all timecode in the black clip has been wiped out. The source clip remains in the Event Browser but all connections to the retimed timeline clip (or clips) are severed. Copying the clips to another timeline or copying the project to another library or export/import of the project XML will not correct it. However if FCP is re-launched or the machine rebooted, the timeline damage is locked in and unrecoverable. If the user immediately recognizes the problem and does CMD+Z it can be recovered. This can happen to a single retimed clip or multiple clips at once. If the retime command and Remove Effects are repeated on the black clip, FCP may delete the clip from the timeline. Red "render bars" may appear which apparently are an undocumented corruption indicator. There is a serious FCP bug whereby if Edit>Remove Effects or Edit>Remove Attributes is used on a retimed clip and adjacent non-retimed clips, it may cause the retimed clip to go black.
0 kommentar(er)
