With Great Sadness……

[Jeremy Garchow]

[David Lawrence] “I think calling this beta software is overly generous. The data corruption described by Jim and others is simply unforgivable in professional commercial software. Imagine if Oracle launched a new version that randomly nuked the client’s DB. No question it would be recalled immediately. These are alpha level bugs at best. It really seems like 10.0.3 is unfit for release.”

I do agree that this is unforgivable, but I have worked with worse “betas”.

This is the first time I’ve heard of corruption at this level.

[Jim Giberti]

[Jeremy Garchow] “Just curious, Jim. Did you ever get this solved?:

https://forums.creativecow.net/readpost/344/8643

Bad ram can cause things to go down in a hurry. Did you try reloading the system at any point?

10.0.3 has certainly brought some bad performance and there’s no excuse to release something that hasn’t been vetted, but if files in the Finder are corrupt, it could point to other more systemic issues.”

Hey Jeremy,

RAM is fine, all systems are fine and optimized and were at the times of the corruptions.
I had a chance to play a little catch up today and started with a long talk with Apple

There’s no question that FCPX can be “sensitive” with content.
In essence this is what I’m sure of:

The simple graphic (in this instance was correctly formatted and a simple, flattened jpg out of PS) didn’t corrupt the FCPX project, FCPX corrupted the file, which then apparently corrupted the project as well.

2nd time in two weeks both times using simple graphic files.

Here’s what I think overall after spending several hours exploring all potential options/solution – FCPX is very high maintenance if you’re doing work beyond simple edits and small projects. At least higher than other similar programs.

It’s very sensitive to project size and I wouldn’t be surprised if it’s inane practice of bloating itself until it chokes is the fundamental cause of many of the problems people are having.

Here’s an example of what I found. There was one project, a scratch pad that was used to try out some ideas and filters etc. I didn’t even think of it till I decided to go through the program piece by piece.

it was 2 minutes long and had a few transitions. It was 54 GBs. When I deleted the unused render files it reduced the project to 2 GB.

My guess is there’s a point at which any project becomes more susceptible to hanging, crashing and possibly corruption – based on it’s relative project bloat.

Until Apple provides for the simple, logical, automatic deletion of any previous render files, they should make continuous file deletion a primary instruction for users in order to protect projects and media.

Why a project would accumulate every overwritten action in a project defies all logic, but if they fix this and provide a “Clear RAM” command, FCPX would have a functional memory approach.

Apple created a project that both gobbles RAM by the minute with no way to release it and simultaneously grows every project every moment it renders.

I’m not sure how they assess their priorities with updates, but I’m thinking these are first tier considerations.

[Jeremy Garchow]

[Jim Giberti] “It’s very sensitive to project size and I wouldn’t be surprised if it’s inane practice of bloating itself until it chokes is the fundamental cause of many of the problems people are having.”

Absolutely, and a way to turn off the autosave. I’ve said this before, but using your project as an example and the FCPX manual:

FCPX saves everytime a “change is detected” or every 15 minutes, which ever comes first. So, having a 56 GB file and having FCPX “detect a change” is going to cause major performance slow downs. I mean imagine trying to save a legacy project after every click, edit, move, whatever, and that should point to what X is trying to do.

https://help.apple.com/finalcutpro/mac/10.0.3/#verb6acb2fb

They need to break off the detected changes from the saving of the database, or something, I’m not a programmer, just a lowly user.

It’s not the size of the project that is the scary part, it’s how that size is dealt with. Right now, everything seems to be centered around saving those huge files, constantly. You can watch it happen when FCPX makes an auto backup file. There’s no wonder it moves slow when it’s trying to perform an operation while waiting for 56GBs to backup.

Kinda nutty.

Thanks for your response, and I’m sorry that this happened. Like you said, anything but corruption…

[Jim Giberti]

[Jeremy Garchow] “FCPX saves everytime a “change is detected” or every 15 minutes, which ever comes first. So, having a 56 GB file and having FCPX “detect a change” is going to cause major performance slow downs. I mean imagine trying to save a legacy project after every click, edit, move, whatever, and that should point to what X is trying to do. “

That’s another great point Jeremy.
It’s actually the third crazy way that they don’t manage memory, and they all create different levels of disfunction.

[Chris Harlan]

[Jim Giberti] “[Jeremy Garchow] “FCPX saves everytime a “change is detected” or every 15 minutes, which ever comes first. So, having a 56 GB file and having FCPX “detect a change” is going to cause major performance slow downs. I mean imagine trying to save a legacy project after every click, edit, move, whatever, and that should point to what X is trying to do. ”

That’s another great point Jeremy.
It’s actually the third crazy way that they don’t manage memory, and they all create different levels of disfunction.
“

Jim, I’m sorry you are going through this. This bloat issue is one of the things that kept me from trying out a few promos with this new version. I know I’ve been critical of the program, but I would really like it to work. It depresses me that this is where things are.

[Steve Connor]

[Chris Harlan] “Jim, I’m sorry you are going through this. This bloat issue is one of the things that kept me from trying out a few promos with this new version. I know I’ve been critical of the program, but I would really like it to work. It depresses me that this is where things are.
“

Can I just mention once again that not everyone is having these issues? I’ve done over 30 projects with it over the last few months and I’ve just finished the first cut of a feature on it with no major problems. 10.03 is certainly not as responsive as 10.02, but for me it’s not so bad that it’s unusable.

Steve Connor
“FCPX Agitator”
Adrenalin Television

[Steve Connor]

Would it have been better if Apple had just decided to quit the Edit Software business completely? I think there probably would have been much less outcry if they had done that.

I’m not surprised people who don’t like FCPX are moving on, they should! I’m just worried about Aindreas

[Aindreas Gallagher] “these are livelihood dependant markets. Continuously, and financially, livelihood dependent markets. Christ: editing is a touch to touch craft wage check. You can’t just nuke the toolset for giggles.

to simply turn around a decade later, whip off the cloth and say : “TA-DAAA!!! damn slavish market adherence , have THIS!!” –

And to have it be quite crazy, and, on this reading, pretty spine chillingly buggy –

It’s. just. not. good. enough.

It’s not on. None of this is on.
“

Still upset with Apple then Aindreas?

Seriously, how are things going?

Steve Connor
“FCPX Agitator”
Adrenalin Television

[Aindreas Gallagher]

thanks for asking, all good – are you ok yourself steve?

http://www.ogallchoir.net
promo producer/editor.grading/motion graphics

[Steve Connor]

[Aindreas Gallagher] “thanks for asking, all good – are you ok yourself steve?
“

Good at the moment thanks, in the middle of cutting a whole bunch of Corporate films and just finished the first cut of a mid budget feature. However I’m now extremely spooked by Jim’s experience.

Making sure I have backups of backups!

Are your clients moving on from FCP yet?

Steve Connor
“FCPX Agitator”
Adrenalin Television

[Oliver Peters]

[Steve Connor] “Are your clients moving on from FCP yet?”

One of the things I find truly scary in this whole transition is that many clients are enamored by the idea of X, but they aren’t the ones actually doing the testing and editing. I am. When I tell them of my concerns and real-world issues they just look at me like I’m taking an anti-Apple attitude. Yet, I’m the one actually pushing real projects through it and not just slapping a few clips together to be impressed about how fast it is.

Of course, if they put it in and disregard prudence and then have Jim’s experience, they have a complete lack-of-understanding as to how or why this could happen. The smarter clients at this point actually seem to be staying with FCP7/FCS until things continue to shake themselves out. My 2 cents, so far.

– Oliver

Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com