[Matías Ónega]

Well, if it works, tell me! I’ll be trying today what I’ve been suggested to do here and see how it goes!

[Matías Ónega]

Wow, thanks. I will try your ideas and check the data you’ve asked for ASAP.

By running in the background I mean the same thing as when you are running Safari and, without clicking on a Word document you happen to have opened at the same time next to your Safari tab, you scroll down the document. You’re not switching application (meaning that, next to the Apple logo you still see SAFARI instead of WORD, that is the application you’re scrolling down in that very moment). In my case, Final cut can do lots of things that would usually require and loading times and Preparing Video For Dispalys if it is running inn the background (that being, while you dont’see FINAL CUT next to the apple logo).

[Matías Ónega]

Hi David! Here is the data of my computer.

MacPro2,1 (Quad-Core Intel Xeon)
Processor speed: 3 GHz
Number of processors: 2
Number of cores: 8
Caché level 2 (per processor): 8 MB
Memory: 8 GB
Bus speed: 1.33 GHz
Boot ROM: MP21.007F.B08
SMC: 1.15f3

I think RAM is not the problem. Specially given that this happens whit any tipe of media, being it small or large, low or high quality, and no matter what format you are using. It’s just always like that.
The thing with Final Cut having to load every time I switch back from Finder or other application (but working spectacularly well when in backgrpund) has been happening since day 1, working in local and with server, and the same using Final Cut in a iMacs 5.1 we’ve tested it with. It’s like it needs to verify all the media you’re working with in case you have made some changes before letting you work with it again (and indeed, when you do some changes in a connected clip, it willbe changed right before letting you go on).

Is there a way to just make the program run as it was on the background –while it’s not? The frustrating thing is that when it works in the background, it proves it can really work fast and without beachball times. So why does that happen anyway?
I can only compare this with Adobe Premiere, which does have not this issue.

Thanks!