[Brynn Sankey]

Hi John,
Thanks for your feedback – much appreciated! I’ve spent quite a bit of time on google looking for info, but am mainly finding industrial specs which, of course, are a whole different ball game and deals with reducing the noise of heavy machinery rather than damping out every last rumble of passing trucks 🙂
Cheers
Brynn

[Brynn Sankey]

I noticed a similar problem today. Unfortunately I don’t have a solution, just a +1 to your problem!

[Brynn Sankey]

I agree with you David that editing is storytelling over hardware proficiency. My comments were meant more in addition to the contributions of others, I certainly wouldn’t suggest that software/hardware proficiency is all that is required to call yourself a pro – far from it.

But I do agree with what Grinner said – “When you know it and can edit anything and respond to any demand, you are ready.” And that takes proficiency as well as an ability to tell a visual story. If you’re full of grand ideas but don’t have the proficiency to match them, then in my opinion you’re not ready to handle “any and every demand.”

[Brynn Sankey]

May seem like a very elementary question, but have you checked your Capture Scratch folder? If a clip was captured in its entirety before FCP crashed, it should be there, despite its absence from the FCP browser.

[Brynn Sankey]

This is in fact very easy.

BEFORE importing your stills, open up the User Preferences dialog (Final Cut Pro>User Preferences…) and click on the “Editing” tab. At the very top left you will see “Still/Freeze Duration.” Change the value to “00:00:00;01” and then import your images. Their default length upon import will be 1 frame, so then you can just “select all” and drop them on the timeline.

If you already imported your stills before making the above change in the Prefs, simply delete them from the browser, make the change and then re-import them.

[Brynn Sankey]

In my opinion, to call yourself a video editor requires proficiency with more than just one platform (FCP, for example). If you tell people you’re a pro based on your experience with FCP and then get hired for a job that requires you to work with Avid, you’re going to look very stupid indeed.

[Brynn Sankey]

What are the specs of your mac? (I ask this to be sure your system is powerful enough to handle playback of multiple streams) and is your scratch disk an external hard drive (or any other hard drive that might not have a read-speed or interface that can handle the necessary bandwidth of playing back multiple streams)?
I don’t know this for a fact, but I cant imagine that using capture now has anything to do with the problem, as the TC is embedded into the clip the same way no matter how you capture.

Quote “Would an alternate workflow be to export fully self contained reference movies?” Just to clarify, there is no such thing as a self-contained reference movie. A clip is either self-contained or it is a reference movie, it can’t be both. The term “reference” refers to the fact that the media is not contained within the file itself, but simply references to the original source material in a separate movie file(s).

One possible solution would be to export all of your individual clips (before you multi-clip them) as self-contained clips (making sure they all start on exactly the same frame and all start on the same timecode), then import all of the self-contained clips into another project and create your multi-clip sequences again. However by doing this you would no longer have the ability to batch capture down the track. You could, however, print each clip to tape with it’s new timecode so you would resolve that problem. It’s just a matter of whether you want to go to the trouble of doing that.

Hopefully that makes sense.

Cheers
Brynn

[Brynn Sankey]

I have never tried importing reference movies, I have always worked with self contained movies if I am re-importing. But just a thought – isn’t it likely that FCP is getting confused between the timecode of the referenced source media, and the timecode embedded into the reference clip itself?
Is your problem remedied if you use self contained clips? I know you are trying to avoid this approach because of the multiclip issue, but i’m wondering if your problem may stem from FCP getting a little confused as to where it is supposed to get its timecode from.