[Andy Mees]

see if CHV’s Clone and Paint collection can help
https://www.chv-plugins.com/cms/Fx-Script/CloneAndPaint-collection/CloneAndPaint-collection.php

[Andy Mees]

drool worthy stuff

[Andy Mees]

Mike,
As a workaround until the cause is nailed down, try changing your sequence codec to ProRes 422 (obviously the source remains the same native XDCAM HD 422) … now, does FCP still crash when scrubbing in the ProRes timeline, and when exporting a self-contained Quicktime Movie (w/Current Settings) from that ProRes 422 sequence, do you still get crashes?

As an aside, if you create the project in Edit 2-9 eg not transfer it from Edit 1 but create it from scratch in Edit 2, do you get the same problem. Basically, can you confirm that the issue is wholly edit suite / fcp installation independent?

Andy

[Andy Mees]

Mike
Can I reasonably assume that you are working with footage transfered from an F700 ? And that the “capture” is via XDCAM Transfer rewrapping the camera native MXF clips to MOV files for use in FCP? And the Export is also using XDCAM Transfer back to disc as MXF wrapped MPEG HD 422 or exporting as Quicktime Movie with or without transcode to other formats? Can you also confirm that your workflows work flawlessly with projects and content acquired and handled in any other suite other than your Edit 1? Just looking for some more details to try to figure out what’s up.

Cheers
Andy

[Andy Mees]

Mike

XDCAM HD 422 is an MPEG format and its native codec, as supplied by Apple, is part of the AppleHDVCodec.component bundle.

Andy

[Andy Mees]

[Loretta Wilson] “As for the Sequence Item Properties:

Compressor – H.264

Thats the problem Loretta, H.264 is not an FCP native sequence format. Your earlier posts suggest that you intended to be working in a DV PAL sequence format but clearly this sequence is H.264.
Go to your Easy Setup menu and reselect DV PAL, then create a New Sequence … open that new sequence and try editing your source footage into that … does it work any better?

Worth noting also is that some of your source clips are using the Animation codec and some using H264, so those clips will certainly need to be rendered in your DV PAL timeline, but overall, you should see things return to normality.

Its likely that when you began editing this project, the first clip you dropped in the timeline was encoded as H264 … and so FCP offered to change the timeline format to suit the source clip, to which you agreed. You should be careful that you always understand any warning message that FCP gives you. If you just ignore them you can end up in an unexpected pickle that can be tricky to resolve.

[Andy Mees]

1) open FCP
2) right click the Flicker filter in the Effects bin and choose Open in Editor
3) select all the text that appears in the subsequent FxBuilder window and press delete
4) now copy and paste the text of that effect in its place
5) go to the FxBuilder menu and choose Create New Plugin (or words to that effect)
6) save the plugin on the desktop
7) then copy it into /Library/Application Support/Final Cut Pro System Support/Plugins
8) relaunch FCP

… failing that just bung me a email (address is in my profile) and I’ll email the filter to you and then you can install it in the Plugins folder as above and relaunch FCP ( steps 8 and 9 )

[Andy Mees]

Lawrence

Are you absolutely certain that you have what you think you have? What I mean is, however unlikely, its possible the footage was actually shot at 50i instead of 25p … stranger things have happened, and its sure to throw anyone for a loop if they’re assuming their footage is of one format when its really of another.

Easy enough to find out though. Just select one of the raw master clips in the browser and press Cmd-9 to view the clip’s Format properties. Note them down and post back with the info … in fact, it would be useful if you did the same thing with one of your sequences.

Cheers
Andy

[Andy Mees]

scriptid “Random Blink” //DO NOT LOCALIZE
filter “Random Blink”
group “Video”;
producesAlpha;

input op, “Opacity”, slider, 0, 0, 100 detent 0;
input blinkAmount, “Amount”, slider, 0.5, 0, 1;

InvalEntireItem
RenderEachFrameWhenStill
fullframe;
code
exposedbackground = 1;

float doBlend;
doBlend = Random (0, 1);

if (doBlend < blinkAmount) dest = src1; else channelfill(dest, 0, 0, 0, 0); blend(dest, src1, dest, op/ 100); end if;

[Andy Mees]

Hi Thompson

In the SETUP MENU under the METADATA options try toggling off the various options: UMID, ESSENCE, HD VANC, DATA ITEM etc … seems to be the only settings that might cause stripping of any preexisting data.

Also, are the captioned files produced by MacCaption MOV files or MXF? Can MacCaption work with the original MXF files. Will it work with raw MXF if you use a third party component such as CalibratedQ MXF Import? (You can grab the demo to check out). If raw MXF is a possibility you could avoid FCP as the conduit for transfer altogether and so eliminate any possible corruption there.

Andy