10.0.3 DISASTEROUS

I'll give that a shot, although I did vac it out a bit when I put the RAM in the first time (it's been in and out a number of times since then for various tests).

I'm also looking into the 10.7.3 "Combo" updater as there's quite a bit of discussion on the web about the mess that the original 10.7.3 was/is. Many feel that this latest "update" fixes a bunch of issues...I'm not holding my breath!

Bleak House - It goes without saying that I feel your pain...but I still had to say it. I am very much looking forward to that "Aha!" moment when the culprit is discovered in all of this!!! Until then; I find that walking the dogs (along with copious amounts of red wine) does help some. 😉

Hey Andy, I just leave the default speed to min, let the computer, or the heat sensor do the job. It works fine when rendering or doing hard CPU task the fans start to kick in like they normally should. So leaving it as the minimum default setting it should be fine.

Switch900 is it the "Favorite" that you set to "Minimum"?

Are you able to post a screen shot?

OK, but what does this actually do then to minimze my fan from running?

Just to let you know, yesterday I had a lengthy conversation with apple who advised Me against creating optimised media. Isnt that somehow contradictory? I Was also told that even if you turn off background rendering it is still doing all sorts of other background tasks and will not make the blindest bit of difference. I was also told that this software Is ahead of it's time and that we should in other words be appreciative of this fact. Yeah right! If they'd been fully tested before going to Market. If I gave a client a film/video that was not fit for purpose I'd either have a very unhappy client or a law suit on myhands... How are they allowed to get away with this rickety piece of cack. All I want is a solid editing platform that cuts through 1080p like a hot knife through butter. And to think everyone is creaming themselves over 4k. What a laugh!

I'm running a 3.4 i7 iMac 8gb ram, not that bad a machine, everything flys on it but as soon as I open fcpx (on it's own as it is a ram sponge) it turns into a useless piece of glass that I want to put my head through. That to me says there is a fault with the software. Now I'm no expert but hey that's why I bought Macs, Init!

a lengthy conversation with apple

Who is this person?

It was one of the Apple pro software agents. UK based. I was told that I was out of my free advice period dah dee dah, but nevertheless still talked to me about it. He wasn't arrogant but it still got under my skin. I didn't get a name, didn't see the point. I rather concerned that my less than 6 month old i7 is happy with everything other than this piece of Apple software. I'm sure with my case number I could pull him up again but I can't imagine its even worth the cost of the call. I'm hoping that rather soon we will be the ones having the last laugh when the cogs finally click and off we go. Then watch all the rats climb back on board the currently sinking ship... Sorry did I just fall asleep?

It is software for the future, so wait a year until the hardware can deal with all the options FCPX has, this has been a cunundrum since the tapestry loom was invented. I can't imagine that there is an apple computer yet that can really edit a 2hr timeline in 4K Pro Res 422 and be responsive as a 2hr 1080P Timeline in Pro Res Proxy. From my expereince I don't see any benefits to turning off background rendering while editing your project timeline.

I agree editing in 1080P should be like a hot knife through butter, and it is if you are careful with your settings and setup, I suggest just one event and project loaded at a time and using trancoded playback proxy. FCP7 gets very slow when you have two feature film projects loaded.

As for why this thread is here, perhaps the FCP X team has a fix coming soon for this title update oversight. 10.0.2 I think came soon after .0.1 if I remeber to fix some bugs.

Thanks for the laugh "useless peice of glass that you want to put your head through".

From your description the Apple pro sofware agent sounds like an idiot.

Just to lower the tone slightly... I think Apple came a bit too soon with FCPX. Cheers for the advice about having just the one project and event. Will try that ASAP and get back to you. After some MUCH needed shut eye ;)

Should I post into a mile-long (7pgs!) long thread? Anyhow ... :

Unfortunately, due to sheer bulk of text in some posts, I miss details to hardware-in-use.

The OP told us MBP - which stands for MacBookPro, right?

Over there, in my original habitat, at iMovie discussions, we notice for many months a serious bug - yes, a real repeatable, diagnosed, documented and fixable bug, no flaw: using TimeMachine on a laptop Mac/10.7 while editing and exporting in iMovie, creates a bunch of errors, most famous the -49 one, Heap Zone, or a generic 'not enough memory':

10.7 + TM creates a hidden 'mirror folder' when mobile-device is out of reach of TM .... and THAT plus the sheer amount of data in video processing, causes an error.

Reading the error descriptions (... as far as I can as a non-native speaker) I would narrow error-analysis by:
if you use 10.7., and a mobile Mac, and your TM-drive is not connected ... switch OFF TimeMachine.

... and if you can't imagine, it could help - just do it, to exclude it..

yes, it's all about iMovie, not FCPX - but iM-b appeared 4 years before FCPX ... the smaller but older sister of 'pro'.

try and report .........

montster wrote:

... And because your project seems to work for you, it must be A-OK for everyone elses.

and because you have trouble, it must be 'desastrous' for everyone else? 😉

FCPX .3, on my tiny & old MacMini, 2.26/8GB doing fine ......... 😁