Performance/Beach Balling question

[Jim Giberti]

[Steve Connor] “The scale of yours appears to be, I haven’t seen another example of that scale of corruption to drive level
“

That was one time – one time too many.

I’ve read lot’s of stories of corruption and in my hour long talk with Apple it’s a term that they used regularly.

I’ve never had a corrupt file in the thousands we’ve produced in every version FCP before X.

Apple now considers it a problem with their new program.

I think if I help people know that, it might save them the nightmares we had on two big projects.

FWIW, previous to the last disaster, I was going to start a thread about how we produced a national film, TV campaign and even the associated radio campaign all with X.

I did pull that off, but it would hardy be the encouraging story to X users that I intended it to be.

I’m still working in FCP, but much more warily and with much greater supervision of it’s flaws.

[Steve Connor]

[Jim Giberti] “I’m still working in FCP, but much more warily and with much greater supervision of it’s flaws.

“

As we all should.

Steve Connor
“FCPX Professional”
Adrenalin Television

[Simon Ubsdell]

[Jim Giberti] “That was one time – one time too many.”

Your experience (with which I can only sympathize, not being able to imagine the trauma of living through it) has completely changed my view of the future of FCPX.

From being something I was eager to try out in a professional situation, only now ironically made possible for me by the very recent advent of x2pro, it has become something I will be giving the widest of berths until such time as this kind of issue has been demonstrably eradicated.

From everything we have seen, that time is waaaaaaaay in the future – if it ever arrives at all.

Thanks for sharing your experience – it is of enormous value.

Simon Ubsdell
http://www.tokyo-uk.com

[Carsten Orlt]

Tom was only trying to point out that we have been here before.

Jim I don’t know with what version of Final Cut legacy you started using it, but I started with version 1 and I remember corrupted sequences or project and lots of problems.

We as a community are eternally grateful that you post your experiences because it tells the rest of us where the pitfalls are and how to possible avoid a similar disaster you went through. It is also understandable that you are still p***** of and say things like horrible code etc. Fair enough.

I guess your experience underlines the fact why some people stay away from early software adoptions and wait until things settle down. Your trust into Apple improving FCPx is a personal choice. Some think they will, some take your experience as proof that they won’t.

FCPx is new and right now is going through the same early problem stages as every complex new software. Apple should have called FCPx something different than FCP legacy to avoid the perception that they build on the old code base and therefor stable performance of FCP7.

I hope you keep posting problems as they arise because for the rest of us your trouble was worth it. We are all smarter because of it. Somebody has to get burned first. Sorry it was you this time!!

Cheers
Carsten

[Tony West]

Jim, these post were very useful.

Thanks man

I cleared a bunch of space on my HDs

[Jim Giberti]

[tony west] “Jim, these post were very useful.

Thanks man

I cleared a bunch of space on my HDs”

Glad it helped Tony.
FWIW I still think that Apple did something fundamental in 1.0.3 that bogged down the system.
Previous to the update I would say that FCPX was snappy in it’s response and a pleasure to work in.
Since then, even with constant memory maintenance, it’s just sluggish and tentative by comparison.

I really wouldn’t be surprised to find it was the new auto backup taking place every 15 minutes combined with the ever growing project size. Like the way you don’t want Time Machine to kick in if you’re doing any serious work.

I also wouldn’t be surprised to find out that all the crashing since 1.0.3 (which never happened once in the months of use before) occurred during those backups.

I honestly think Apple has to get a 1.0,4 patch out asap to fix the performance issues which are likely causing the other issues that some of us have had.

In the meantime keep it small and clean and stay vigilant my friend.

[Jim Giberti]

[Carsten Orlt] “Tom was only trying to point out that we have been here before.

Jim I don’t know with what version of Final Cut legacy you started using it, but I started with version 1 and I remember corrupted sequences or project and lots of problems.

We as a community are eternally grateful that you post your experiences because it tells the rest of us where the pitfalls are and how to possible avoid a similar disaster you went through. It is also understandable that you are still p***** of and say things like horrible code etc. Fair enough.”

Tom is great and I certainly didn’t mean to suggest otherwise.

We started at the beginning with FCP1.0 and moved from our Media 100 systems pretty much immediately.

I never remember losing a project to corruption like this.
That said, I do think I’m understanding the underlying problems with the model and how to work within them while waiting for Apple to address them (and hopefully expanding it’s editing capabilities with a simple track grid and audio mixing).

This could be a great program, but the fact that it operates worse in it’s newest release shows that they’ve got some real work to do.

[Tony West]

[Jim Giberti] “In the meantime keep it small and clean and stay vigilant my friend.”

Will do my brother

Shot some stuff the other day with the subject in front of a window to show the city.

Didn’t have the heads about it so I didn’t have my 56k

It was overcast but the windows still a battle.

I decided to drop it into X to color grade and mask him to drop the window.

Looked great on the first clip so I pasted the effect down the line on the other clips.

Length maybe 30 min

Render took way too long in my opinion.

I’m on 1.0.3 with snow L

and an 8 core mac pro

Had not had a render that slow before, which caused me to search and find this post.

I think you are totally on point with everything you said. Heck, it’s what happened to you.

It’s given me pause.

Apple better get the fix out. I will work past some little things here and there and I can deal with style
but that story you told………

Better fix it.

[Simon Ubsdell]

[tony west] “Render took way too long in my opinion.”

Why are you rendering at all? I think it has been well established that there is only a disadvantage to rendering in addition to its being phenomenally slow. Conversely exporting an unrendered project is very quick for a number of reasons. Only ever render if you can’t actually work in the timeline otherwise, but most things should be real time. And that of course means that your render files folder doesn’t fill up. A win-win.

Simon Ubsdell
http://www.tokyo-uk.com

[Tony West]

[Simon Ubsdell] “Why are you rendering at all? I think it has been well established that there is only a disadvantage to rendering in addition to its being phenomenally slow. Conversely exporting an unrendered project is very quick for a number of reasons. Only ever render if you can’t actually work in the timeline otherwise, but most things should be real time. And that of course means that your render files folder doesn’t fill up. A win-win.”

Simon, very good question. You are right, I guess I was just doing it out of habit.

Thanks for the feedback.

You just saved me tons of time in the future.