FCP re-reads movie data each time

[Tom Wolsky]

First, they’re called editors.

Second, preparing video for display is not “reading the video.” It’s better not to make up terminology. This is usually a project memory issue. One way around this is to make sure you have closed all sequences before you quit the application. Or launch the application holding the Option key.

This can also be caused by defective RAM. It can also be caused by an incorrectly installed operating system and application.

All the best,

Tom

Class on Demand DVDs “Complete Training for FCP7,” “Basic Training for FCS” and “Final Cut Express Made Easy”
Author: “Final Cut Pro 5 Editing Essentials” and “Final Cut Express 4 Editing Workshop”

[Jerry Levin]

Hi Tom. Thanks for quick response and clarifications.

To elaborate:
The original machine that the project was created on works perfectly fine.

I cloned the folder tree to two other machines that are actually far more capable (more recent CPU, 4 gig instead of 2; just newer boxes). It’d be strange (though not impossible) for them to both have memory related issues.

Both exhibit the exact same issue of “Searching for movie data in file foo.mov”, and do this for all 75 .MOV files.

This happens even if I’ve just booted the machines, have just launched FCP for the first time since booting up the box.

Here’s a sequence I went through on both machines, sorry to be verbose but perhaps there’s a hint you may recognize:
1. I created a new, empty project file, closed FCP, and re-opened FCP. no problems.
2. With the new project, I imported all the movie clips, saved, closed and reopened the project. Again no problem.
3. I opened the project file that works perfectly on the original machine, by copying it to the problematic machine. After the project finished loading with the issue described, I cut and pasted the sequence into the newly created project. Saved the newly created project file, quit FCP, rebooted the machine. Launched FCP and opened the new project. Same problem.
4. With FCP running, I ensured that it would *not* open last project in user prefs. Quit and rebooted machine. Launched FCP. It *still* displays the same problem, even when opening a new project. When it’s finished loading, this appears to be an empty file; i.e. no media, no bins, just a “virgin” project. Why would it reference media that a new project isn’t “connected” to?

How would one verify that the app is properly installed, or hasn’t been corrupted? I do know that the other editor has done a force quit as there’s no clean way to abort out of the problem…

I have also launched FCP with the Option key, but w/o change in the behaviors described.

Again – thanks.

PS – with regard to making up terminology: fair enough – I’m here to learn and appreciate the chance to learn best practices and vernacular. For the term “reading”, this stems explicitly from the dialog box title, “Reading project”, along with the displayed message “searching … in file foo.mov”. Thanks…

Jerry

[Tom Wolsky]

I’m confused here, is it happening on both machines or on one?

Have you trashed your preferences?

Details of the machines, OS, and QT would help. Are they all using the same versions of the OS, QT, and FCP? What is it?

“Searching for movie data in file foo.mov”

This is actually what the error message says? Even after trashing prefs and opening a blank project?

All the best,

Tom

Class on Demand DVDs “Complete Training for FCP7,” “Basic Training for FCS” and “Final Cut Express Made Easy”
Author: “Final Cut Pro 5 Editing Essentials” and “Final Cut Express 4 Editing Workshop”

[Jerry Levin]

There are 3 machines: one original which works perfectly, two that repro the identical problem.

OS:
Working machine: 10.6.3, 2.33 Ghz Intel Core 2 Duo (MacBookPro2.1), 2 Gig RAM

1st problem machine: 10.6.2, 2.8 Ghz Intel Core 2 Duo, MacBookPro5.2, 4 Gig RAM

QT Player:
All machines 10.0

FCP:
All machines: 7.0.2

The text actually reads:
“Searching for movie data in file foo.mov” where “foo.mov” changes for each of the 75 MOV file names that are the source files. Example: “Cam1_A.mov”, Cam1_B.mov” all the way through Cam3_X.mov.

And yes this happens even after trashed prefs, and a new (empty) project file that’s opened.

Rebooting both the machine and FCP, even with “open last project” unchecked still repros this.

Interesting, eh?

Thanks in advance for your thoughts…
Jerry

Jerry

[Jerry Levin]

One add’l comment – I only posted info about one of the two problematic machines. The other one which is a tower config isn’t here for me to check on OS and app versions.

Thanks,
Jerry

Jerry

[Tom Wolsky]

There is no way after trashing preferences and launching the application, not an existing project, that FCP will look for video.

Are you sure it’s FCP looking for the video and not the system?

How was the OS and apps installed on these machines? Are they new machines with the OS preinstalled, or where they upgraded? Was this done with a clean erase and install from discs, or otherwise?

All the best,

Tom

Class on Demand DVDs “Complete Training for FCP7,” “Basic Training for FCS” and “Final Cut Express Made Easy”
Author: “Final Cut Pro 5 Editing Essentials” and “Final Cut Express 4 Editing Workshop”

[Jerry Levin]

Hi Tom…

More information here (thanks for staying with this).

1. After trashing prefs, FCP boots cleanly.
2. If I open the real project file, FCP goes through the searching movie behavior.
3. I allow FCP to finish opening the project, and then quit. When I launch FCP again it still goes through the same search behavior, even though *this* time it opens to a new project (i.e. “open last project” is not checked).
4. FCP will continue to go through this until I trash the prefs again. Bizarre.

On a separate note,
1. Trashed user prefs, ensured FCP was launching clean
2. I plugged the original external disk from the working laptop into the new, problematic laptop (after disconnecting the disk with copied files).
3. Launched FCP with the desired project file – all worked fine. There’s obviously some file(s) needed to satisfy FCP, but have no idea what, but at least this is a tangible hint).

Insights?

Jerry